Bug 12018 - libpq9.3_5 conflicts with libpq9.2_5, breaking upgrades
Summary: libpq9.3_5 conflicts with libpq9.2_5, breaking upgrades
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: release_blocker normal
Target Milestone: ---
Assignee: Funda Wang
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 11704 11979
  Show dependency tree / graph
 
Reported: 2013-12-16 20:10 CET by David Walser
Modified: 2014-01-25 01:04 CET (History)
2 users (show)

See Also:
Source RPM: postgresql9.3-9.3.2-1.mga4.src.rpm
CVE:
Status comment:

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

Description David Walser 2013-12-16 20:10:05 CET 
I'm testing mga3->mga4 upgrades, and when upgrading a VM which has moodle installed, which requires php-pgsql, which requires the libpq library, the libpq library and php-pgsql packages weren't able to be upgraded, and I got this:

Some requested packages cannot be installed:
libpq9.3_5-9.3.2-1.mga4.i586 (due to conflicts with libpq9.2_5-9.2.6-1.mga4.i586)
php-pgsql-5.5.6-1.mga4.i586 (due to unsatisfied postgresql-libs[>= 9.3.1])

Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-12-22 15:30:49 CET

Blocks: (none) => 11979

Comment 1 David Walser 2013-12-27 22:37:27 CET 
Oden posted some ideas to the mailing list that might help:
https://ml.mageia.org/l/arc/dev/2013-12/msg01070.html
David Walser 2014-01-23 20:08:54 CET

Blocks: (none) => 11704

David Walser 2014-01-23 21:43:30 CET

Priority: Normal => release_blocker

Comment 2 David Walser 2014-01-23 22:20:03 CET 
Oden, nobody's heard from Funda in a little while and Anne says he seems to be unreachable at the moment.  You seemed to have a workable solution devised for this.  Do you think you could commit it to SVN?

CC: (none) => oe

Comment 3 Anne Nicolas 2014-01-24 14:33:24 CET 
Packages submitted just now. Will be included in next isos

CC: (none) => ennael1

Comment 4 David Walser 2014-01-25 01:04:51 CET 
I performed a new upgrade test and the fix worked successfully.  Thanks Oden!

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