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).

before restarting urpmi

(should we try to update libcares & libssl too???)

When the same packages is available from different medias (main/release
and main/update for example), urpmi can forget from which media it
downloaded the package,  and this causes issues with key checking. This
commit makes sure we are using the right package id for the package we
downloaded (the same package will have different IDs if it's available
from different medias).

(backporting r250481 from trunk (2008-12-15))

  o --auto: do not prompt for "retry" on aria2 download failure

(to be used in urpmi.update)

(for next commit)