Bug 719

Summary: upgrade to mageia stops claiming 'some files are missing'
Product: Mageia Reporter: robert marshall <robert>
Component: InstallerAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: balcaen.john, sfietkonstantin
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: libkdecorations4-4.6.2-0 CVE:
Status comment:

Description robert marshall 2011-04-08 14:55:31 CEST 
Description of problem:

Upgrading from mdv 2010.1 to the beta release. I followed instructions in 
http://mageia.org/wiki/doku.php?id=qa_upgrade using the ftp.nluug.nl mirror and after about 500 of the 1947 packages the upgrade stopped with the message

.... libktexteditor4-4.6.2-0.mga1.i586.rpm
...retrieving done
Installation failed, some files are missing:
    ftp://ftp.nluug.nl/pub/os/Linux/distr/mageia/distrib/cauldron/i586/media/core/release/libkdecorations4-4.6.2-0.mga1.i586.rpm
You may need to update your urpmi database.
unlocking urpmi database
unlocking rpm database

Version-Release number of selected component (if applicable):


How reproducible:
upgrade stopped there; I tried the process again (the urpmi command) but it exited without doing any further installation

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 John Balcaen 2011-04-08 15:20:09 CEST 
it's a network/mirror problem here :/

CC: (none) => balcaen.john

Comment 2 robert marshall 2011-04-08 15:27:01 CEST 
Though I can see 4.6.2-1 of libkdecorations on the mirror, guess there's a faulty dependency somewhere?
Comment 3 John Balcaen 2011-04-08 15:41:16 CEST 
Here it means that the hdlist on the mirror are not synchronized with the files available on the mirror.
So you need to update your hdlist (as suggested by urpmi).
In summary while you were updating your box, kdebase-workspace-4.6.2-1 has been uploaded & kdebase-workspace-4.6.2-0 removed from your mirror, but since your hdlist was out of date, urpmi is trying to recover a non existent package.
Comment 4 robert marshall 2011-04-08 16:00:19 CEST 
Ah ok - thanks. Doing it now!
Should I close/resolve this?
Comment 5 Lucien XU 2011-04-08 17:44:44 CEST 
Closed : INVALID !

Status: NEW => RESOLVED
CC: (none) => sfietkonstantin
Resolution: (none) => INVALID