As per discussion on dev ML. We currently carry 4 postgresql versions which is excessive and unreasonable for QA to test when updated. With 2 live releases and 4 versions in 2 arches it leads to 16 separate tests for one update, assuming there are no issues. Reproducible: Steps to Reproduce:
Priority: Normal => release_blockerBlocks: (none) => 14069
Assigning to Oden as he said he would work on this.
Assignee: bugsquad => oe
Hi Oden, What's the status on this bug? Do you just need more time to make the necessary packaging changes, or do you need some more input?
CC: (none) => remi
Simple solution is to drop the older versions.
Just FYI, I found this in /etc/urpmi/prefer.vendor.list: # postgresql libpq9.3_5 lib64pq9.3_5 It should probably also be updated if the one postgresql that we keep is version 9.4.
After speaking with Oden he will not be able to release it before Mageia 5. So unless somebody can work on it we will have to move it for Mageia 6
CC: (none) => ennael1
Can we drop older versions then please as an interim measure.
So, in order to drop postgresql{9.1,9.2,9.3}, we need to make sure that all current packages are using postgresql9.4 (the latest version). With a quick check on BuildRequires, it seems only "glom" requires postgresql9.3, the rest are unversioned so hopefully are built against 9.4: http://paste.fedoraproject.org/195741/08534142/ I'll try building glom against postgresql9.4 to get started.
Hm, since it won't be that straight-forward since I can't install postgresql9.4-server out of the box (even though I never installed postgresql9.3-server): http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/media/core/release/postgresql9.4-server-9.4.1-1.mga5.x86_64.rpm installing postgresql9.4-server-9.4.1-1.mga5.x86_64.rpm from /var/cache/urpmi/rpms Preparing... ########################################################################################################################################################## You currently have database tree for Postgresql 9.3 You must use postgresql9.3-server To update you Postgresql server, dump your databases delete /var/lib/pgsql/data/ content, upgrade the server, then restore your databases from your backup error: %prein(postgresql9.4-server-9.4.1-1.mga5.x86_64) scriptlet failed, exit status 1 ERROR: 'script' failed for postgresql9.4-server-9.4.1-1.mga5 error: postgresql9.4-server-9.4.1-1.mga5.x86_64: install failed
Perhaps keeping two, the one from mga4 and the new one introduced in mga5. Unless there is a compelling reason to keep so many? mga4 currently has 9.0, 9.1, 9.2, 9.3
Re comment 8, it seems I had some stuff in /var/lib/pgsql/data even though I can't remember having dabbled in postgresql9.3-server stuff before... Cleaning this stuff made it possible to upgrade. I just tried on a clean install of Mageia 5 RC, postgresql9.4-server installs without any issue.
As discussed right now on #mageia-dev, we'll keep 9.3 and 9.4 for Mageia 5. postgresql9.3 is only used by "glom" and the latter could probably be built against postgresql9.4, but since 9.3 was the latest version in mga4, it's better to keep it to preserve smooth upgrades. I'll obsolete postgresql{9.1,9.2} with postgresql9.4.
The new postgresql9.4-9.4.1-2.mga5 should have obsoleted postgresql{9.1,9.2}. What's left to do for this issue is to add a mention in the release notes about that, so that users of postgresql{9.0,9.1,9.2} are aware that they need to dump their database before they upgrade. <tmb> the problem with obsoleting old postgresql is that it will screw the users too... (if you dont dump the database before the upgrade, you cant dump it after with the new server ...
Done: https://wiki.mageia.org/en/Mageia_5_Release_Notes#Obsoletes_packages
Status: NEW => RESOLVEDResolution: (none) => FIXED