summaryrefslogtreecommitdiffstats
path: root/urpm/md5sum.pm
diff options
context:
space:
mode:
authorChristophe Fergeau <cfergeau@mandriva.com>2010-04-28 10:10:27 +0000
committerChristophe Fergeau <cfergeau@mandriva.com>2010-04-28 10:10:27 +0000
commitae52aba4a92db1172d66b73e7f06a0203fc0fdcd (patch)
tree51624e0d29eace726fd21ca2d781ed48c5458f3b /urpm/md5sum.pm
parent73c8eb5336829b10f490dbcac1d5259a82d62e40 (diff)
downloadurpmi-ae52aba4a92db1172d66b73e7f06a0203fc0fdcd.tar
urpmi-ae52aba4a92db1172d66b73e7f06a0203fc0fdcd.tar.gz
urpmi-ae52aba4a92db1172d66b73e7f06a0203fc0fdcd.tar.bz2
urpmi-ae52aba4a92db1172d66b73e7f06a0203fc0fdcd.tar.xz
urpmi-ae52aba4a92db1172d66b73e7f06a0203fc0fdcd.zip
remember which media local packages came from
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).
Diffstat (limited to 'urpm/md5sum.pm')
0 files changed, 0 insertions, 0 deletions