Bug 8669 - update points to new packages that do not yet exist in Cauldron media (at given version)
Summary: update points to new packages that do not yet exist in Cauldron media (at giv...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-12 10:32 CET by Digigold
Modified: 2013-01-25 08:49 CET (History)
3 users (show)

See Also:
Source RPM: lib64harfbuzz0-0.9.10-2.mga3.x86_64.rpm, lib64hpip0-3.12.9-3.mga3.x86_64.rpm, lib64hunspell1.3_0-1.3.2-5.mga3.x86_64.rpm, lib64hdf5_7-1.8.9-3.mga3.x86_64.rpm, lib64hdf5_hl7-1.8.9-3.mga3.x86_64.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Digigold 2013-01-12 10:32:14 CET 
RPMs affected:
lib64harfbuzz0-0.9.10-2.mga3.x86_64.rpm, lib64hpip0-3.12.9-3.mga3.x86_64.rpm, lib64hunspell1.3_0-1.3.2-5.mga3.x86_64.rpm, lib64hdf5_7-1.8.9-3.mga3.x86_64.rpm, lib64hdf5_hl7-1.8.9-3.mga3.x86_64.rpm

Description of problem:
For lib64harfbuzz0-0.9.10-2.mga3.x86_64.rpm only lib64harfbuzz0-0.9.10-1.mga3.x86_64.rpm exists.  Problem is identical for all rpms listed above.  /core/release and the current urpmidb don't match and they need to. May stop urpmi from updating other files! (I worked around this manually.)

How reproducible:

Update any pkg mentioned above

Please fix the index file for /core/release urpmidb!
Digigold 2013-01-12 10:33:28 CET

CC: (none) => digigold808

Comment 1 Thomas Backlund 2013-01-12 11:38:03 CET 
This is due to the full cauldron rebuild currently happening, so it takes some time for mirrors to catch up.

I think this will get back to normal in the next couple of days...

CC: (none) => tmb

Comment 2 Manuel Hiebel 2013-01-12 11:42:59 CET 
tmb was faster
Comment 3 Manuel Hiebel 2013-01-25 08:49:11 CET 
should be fixed now

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.