Bug 10132 - /sbin/install-info from dpkg in mga2 blocks the upgrade to mga3 (conflict with info-install)
Summary: /sbin/install-info from dpkg in mga2 blocks the upgrade to mga3 (conflict wit...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Malo Deniélou
QA Contact: QA Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-17 18:48 CEST by Rémi Verschelde
Modified: 2013-05-17 23:00 CEST (History)
1 user (show)

See Also:
Source RPM: texinfo-4.13a-8.mga3.src.rpm
CVE:
Status comment:


Attachments
/root/drakx/report.bug.xz (38.85 KB, application/x-xz)
2013-05-17 18:50 CEST, Rémi Verschelde
Details

Description Rémi Verschelde 2013-05-17 18:48:53 CEST
Conflict while upgrading from Mageia 2 to Mageia 3 using the i586 DVD:
file /sbin/install-info from install of info-install-4.13a-8.mga3.i586 (from texinfo SRPM) conflicts with file from package dpkg-1.16.0.1-2.mga1.i586

The upgrade aborts because of that.

Possible fix (from Luigi on IRC):
<Luigi12_lappy> if /sbin/install-info was removed from the mga3 dpkg, install-info just needs a versioned Conflicts


Version-Release number of selected component (if applicable):
info-install-4.13a-8.mga3.i586

Reproducible: 

Steps to Reproduce:
Comment 1 Rémi Verschelde 2013-05-17 18:50:08 CEST
Created attachment 3987 [details]
/root/drakx/report.bug.xz
Rémi Verschelde 2013-05-17 18:51:00 CEST

Assignee: bugsquad => pierre-malo.denielou
QA Contact: (none) => qa-bugs

Comment 2 Malo Deniélou 2013-05-17 18:59:07 CEST
Fixed in svn and soon pushed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 3 Thierry Vignaud 2013-05-17 22:54:49 CEST
This is bogus, dpkg is no more installable

CC: (none) => thierry.vignaud

Comment 4 Malo Deniélou 2013-05-17 22:56:03 CEST
I put a <= instead of a <.
I'll fix.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 5 Malo Deniélou 2013-05-17 23:00:08 CEST
Thomas fixed it quicker.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.