| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
(...)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
installation fails due to either conflicts (mdv#63072) or to
unselecting package (inspirated by mdv, mdv#63940)
|
| |
|
| |
|
|
|
|
| |
installing mga1 in a chroot from mga2+ (mga#4590)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
(conflicts, requires on older than installed packages, unstallable
packages)
|
|
|
|
| |
again
|
| |
|
| |
|
|
|
|
| |
packages exist in several repositories (eg: noarch packages) (mga#4322)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
twice on x86_64 (mga#4038)
|
|
|
|
|
|
|
|
| |
(/var/lib/rpm/installed-through-deps.list) when chrooted
(was trying to read out of chroot one when computing orphans)
(compute_future_unrequested_orphans,get_orphans) adapt to new calling
convention
|
|
|
|
|
|
|
| |
(cautgh by perl_checker, might help mga#1342)
introduced by cfergeau in r261869 on 2009-10-13
("add df function to urpm/sys.pm")
|
|
|
|
|
|
|
|
|
| |
urpmf & urpmq)
introduced in r232995 by pixel on 2008-01-15
("fix using xml info files with spaces in medium name")
(cautgh by perl_checker)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Barakin, mga#2518)
due to options->{metalink} test, we were selecting curl/aria2/... before
checking for rsync protocol
tested by setting 'choosen' in /var/cache/urpmi/mirrors.cache to any
mirror available on rsync, for examle:
rsync://ftp-stud.hs-esslingen.de/Mageia/distrib/cauldron/x86_64
|
|
|
|
| |
missing or bad packages
|
| |
|
| |
|
|
|
|
|
|
|
| |
--auto-select --update defaulting to all media when there're no update
media (#1024)
(syncing with currently shipped urpmi)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's sometimes possible that a package is available from both a
local medium (CDROM) and a distant one. This causes problems
when the package isn't signed with the same key (this is bad
but happens on MES5 install CDs) as urpmi tends to get confused
about where a package comes from and then check the package against
the wrong key.
Packages are assigned IDs by urpmi, and these IDs are
used to figure out the package media. This ID is also used as an
identifier to "recognize" identical packages coming from different
media, so we need to be careful when manipulating it. In particular,
we can't assign the right ID to every package right away because then
this would break package downloading (we'd download packages available
on local media).
When processing packages to download, if we encounter a local
package, we assign it the right ID. This assumes the list of media
in the blist are sorted by order of relevance (ie prioritary ones
first).
|