Bug 1363 - mageia-release-common fails to install. Blocked by madriva-doc packages.
Summary: mageia-release-common fails to install. Blocked by madriva-doc packages.
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: release_blocker normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-20 21:57 CEST by Dave Hodgins
Modified: 2011-05-21 01:10 CEST (History)
0 users

See Also:
Source RPM: mageia-release-1-0.10.mga1.src.rpm
CVE:
Status comment:

Attachments
urpmi --auto-update --debug output (9.95 KB, text/plain)
2011-05-20 21:59 CEST, Dave Hodgins 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Dave Hodgins 2011-05-20 21:57:45 CEST 
From urpmi --auto-select ...
trans: scheduling update of mageia-release-common-1-0.10.mga1.i586 (id=14100, file=/var/cache/urpmi/rpms/mageia-release-common-1-0.10.mga1.i586.rpm)
Installation failed:
        mandriva-doc-common >= 2010.1-1.0mdv2010.1 is needed by (installed) mandriva-doc-Drakxtools-Guide-en-2010.1-1.0mdv2010.1.noarch
        mandriva-doc-common >= 2010.1-1.0mdv2010.1 is needed by (installed) mandriva-doc-Mastering-Manual-en-2010.1-1.0mdv2010.1.noarch
        mandriva-doc-common >= 2010.1-1.0mdv2010.1 is needed by (installed) mandriva-doc-Introducing-en-2010.1-1.0mdv2010.1.noarch

I'll attach --debug output.
Comment 1 Dave Hodgins 2011-05-20 21:59:08 CEST 
Created attachment 434 [details]
urpmi --auto-update --debug output
Comment 2 Ahmad Samir 2011-05-21 00:11:03 CEST 
Is this the same installation used in the speech_tools bug?

Ideally this bug shouldn't exist, latest mageia-release obsoletes mandriva-doc-common, and the upgrade should be smooth, I've just tested in a 2010.1 VM.

Priority: Normal => release_blocker

Comment 3 Dave Hodgins 2011-05-21 01:10:30 CEST 
Yes.  I'll close this as invalid then, and manually remove those packages.  Thanks.

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