On Sat, 2003-09-20 at 17:27, Felix Miata wrote: > I installed fresh from my sunet cooker rsync about three days ago. Last > night (around 02:00 UTC) I freshened my rsync, then did the following: > > 1-urpmi.addmedia --update cooker-updates > file://mnt/nfs/ax5t3/cooker/Mandrake/RPMS with ../base/hdlist.cz > > 2-urpmi -a > > 3-urpmi -v --auto-select > > 4-urpmi kernel > > Step 3 installed about 39 packages and ended with a warning that two > packages were not available. Step 4 ended with "everything already > installed", even though my kernel was 2.4.22-9, but the package on the > mirror is 2.4.22-10. So, I went to the RPMS directory and successfully > ran 'rpm -i kernel-2.4.22-10mdk-1-1mdk.i586.rpm'. > > Is this oddball 10mdk-1-1mdk rpm the reason why urpmi wouldn't install > it? How do I find out what other existing packages didn't install? Why > were there packages missing?
Anyway, to answer the original question despite Ron's masterful diversion of it to be about his download script...this is probably just due to a synchronisation problem between the hdlist and the available packages. Packages tend to be propagated to mirrors before the hdlists, so if you happen to catch a mirror while it's busy updating, you may well find a situation where the hdlist it has no longer reflects the packages it has. Thus the missing packages (these would be ones that had been updated twice since your rsync; the hdlist would contain version X+1, which the actual file on the mirror would be X+2) and the non-updated kernel (which had presumably only been updated once; you have 9mdk, the hdlist lists 9mdk so urpmi thinks there is no update available, even though 10mdk was actually on the mirror by that point). -- adamw
