| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
regression introduced in commit r7280 on Feb 5 2013: "(install_logger)
unify with callback_uninst(), thus fixing counting for erasures"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(spot by Colin on installing a minimal system with urpmi)
callback_open got called one too much (it got called twice for first
package which is actually filesystem), thus we bump the index one too
much.
the call chain is:
rpmtsRun() -> runTransScripts() -> rpmteProcess() which says:
/* Dont bother opening for elements without pre/posttrans scripts */
But since we now have package ('filesystem') with %pretrans due to /usr
migration, it goes further and calls rpmteOpen()->rpmteFDHeader() which
notifys us about a package opening in order to get its file descriptor.
|
| |
|
|
|
|
| |
rationale: 'callback_uninst' now enables to get erasure progress
|
| |
|
| |
|
| |
|
|
|
|
| |
eg: for rpmdrake/gurpm/drakx
|
| |
|
|
|
|
|
|
|
|
|
|
| |
only initialize $total_pkg:
- when starting a new transaction
- or on first erasure in transaction
(_compute_pkg_total) kill it (no more needed)
adjust testsuite accordingly
|
| |
|
|
|
|
|
|
|
|
|
|
| |
erasures
(callback_uninst) restore quiet behavior when not in verbose mode
(install) temporary set $urpm->{trans}
adapt testsuite
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
inspirated from install_logger()
adjust testsuite accordingly
|
| |
|
|
|
|
|
| |
got broken in commit r6466 on 2012-11-16:
"(_apply_delta_rpm) split it out of _schedule_packages()"
|
| |
|
| |
|
| |
|
|
|
|
| |
broken for years (actually it _NEVER_ worked...)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
should have been done right after commit r251061 by pixel on Tue Jan
2009: "- drop urpmi.recover
(no more possible with rpm 4.6 which doesn't handle --repackage)"
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
else we keep the RPM DB open several times until rpm fails:
created transaction for installing on / (remove=0, install=0, upgrade=8)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Basenames index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Group index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Requirename index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Triggername index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
(...)
regression introduced in commit r2946 on 2012-02-14
(was: '(install) --test: do not display "More information on package"')
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
else we keep the RPM DB open several times until rpm fails:
created transaction for installing on / (remove=0, install=0, upgrade=8)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Basenames index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Group index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Requirename index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Triggername index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
(...)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
with Magiea.
This commit consitsts of the following subversion commits:
------------------------------------------------------------------------
r1928 | dmorgan | 2011-09-13 21:44:28 +0100 (Tue, 13 Sep 2011) | 1 line
Import urpmi
------------------------------------------------------------------------
|
| |
|
|
|
|
|
|
| |
rationale: all prints in transaction/installation code now go through
a callback that redirects the output at install time
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
r254652 ; revert both:
- r253559 (2009-03-04) "(install) close another fd leak (needed for
drakx)"
- and r253550 (2009-03-04: "(install) explicitely close the RPM DB on
comleting transaction (needed for drakx -- looks like refcount has
hard work)"
|
|
|
|
|
|
|
| |
many times in installer
(regression introduced in r253510 when adding new callbacks for the installer)
|
|
|
|
|
|
|
|
| |
detecting whether installing ackages succedded or not)
this doesn't impact anything since this is a freshly added callback used only
by drakx
|
| |
|
|
|
|
|
| |
(needed for drakx -- looks like refcount has hard work):
|
| |
|
| |
|
| |
|