Ubuntu
postgresql-8.4 package

'postgresql-plperl-8.4' is marked for removal but it is in the removal blacklist

Bug #905454 reported by DavidL
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
postgresql-8.4 (Ubuntu)
Fix Released
High
Martin Pitt

Bug Description

TEST CASE:
1. Install Oneiric and apply updates
2. Install the following packages:
  postgresql-8.4
  postgresql-plperl-8.4
3. Upgrade to Precise

ACTUAL RESULT
Upgrade fails with
The package 'postgresql-plperl-8.4' is marked for removal but it is in the removal blacklist.

ORIGINAL DESCRIPTION
I am running Ubuntu 11.04 when trying to 11.10 I got the following error. I have an run a pre-release version of Ubuntu, I'm not trying to upgrade to a pre-release version of Ubuntu. It's possible that I'm using non Ubuntu packages but nothing involving Postgresql or Perl.

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade:
The package 'postgresql-plperl-8.4' is marked for removal but it is in the removal blacklist.

 This can be caused by:
 * Upgrading to a pre-release version of Ubuntu
 * Running the current pre-release version of Ubuntu
 * Unofficial software packages not provided by Ubuntu

If none of this applies, then please report this bug using the command 'ubuntu-bug update-manager' in a terminal.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.150.5.1
ProcVersionSignature: Ubuntu 2.6.38-13.52-generic-pae 2.6.38.8
Uname: Linux 2.6.38-13-generic-pae i686
Architecture: i386
Date: Fri Dec 16 14:01:53 2011
GConfNonDefault:
 /apps/update-manager/check_new_release_ignore=
 /apps/update-manager/first_run=false
 /apps/update-manager/show_details=true
 /apps/update-manager/window_size=(1278,904)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager
UpgradeStatus: Upgraded to natty on 2011-12-16 (0 days ago)
VarLogDistupgradeApttermlog:

VarLogDistupgradeHistorylog:

VarLogDistupgradeTermlog:

See original description
Revision history for this message
DavidL (w-launchpad-larochelle-name) wrote :
Revision history for this message
DavidL (w-launchpad-larochelle-name) wrote :

FWIW, after explicitly removing the package by running 'apt-get remove postgresql-plperl-8.4' in the terminal, I was able to get the upgrade to complete.

Revision history for this message
RedSingularity (redsingularity) wrote :

Thanks for confirming. Closing report.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in update-manager (Ubuntu):
status: New → Invalid
Revision history for this message
Ken Tanzer (ktanzer) wrote :

I'm not sure why this was closed or marked invalid. I am encountering this same problem, also trying to upgrade from 11.04 to 11.10. In bug 961719, the same issue is reported attempting 11.10->12.04.

Any idea why this package (postgresql-plperl-8.4) is on the "removal blacklist?" Whatever exactly that means. It's something you'd expect with spam, not Free Software! ;)

I too was able to remove it manually, and the upgrade is currently proceeding. But I'd imagine some people will end up getting stuck or frustrated by this, and unable to upgrade...

Jean-Baptiste Lallement (jibel)
Changed in update-manager (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

reproduced on oneiric

Changed in update-manager (Ubuntu):
assignee: nobody → Canonical Foundations Team (canonical-foundations)
importance: Undecided → High
description: updated
tags: added: rls-mgr-p-tracking
tags: added: dist-upgrade oneiric2precise
Revision history for this message
Martin Pitt (pitti) wrote :

Quick summary of the problem: postgresql-8.4 and -9.1 are designed to be co-installable, as we cannot just remove -8.4 after the upgrade to precise. It needs to stay around so that people can migrate their 8.4 DBs to 9.1. There is a debconf note and documentation to explain how this works.

Now, this works fine for the most part, but the problem with this upgrade is that plperl -8.4 and -9.1 are not co-installable because lucid to natty's 8.4 versions are built against libperl5.12, which is not co-installable with libperl5.14.

As we don't really want to trash people's data, the easiest option would be to reintroduce postgresql-8.4 into universe and build it against Perl 5.14. This should fix the upgrade and keep a migration path. WDYT?

Revision history for this message
Steve Langasek (vorlon) wrote :

Martin, if you think it's necessary to pull this back into universe, I can do the NEW review for it. Assigning this bug to you for the upload.

Alternatively I would think admins should just be advised to dump their databases before upgrade and deal with reimporting them afterwards.

In both cases, it makes sense to leave the blacklist in place so that the package is not removed unintentionally as part of the upgrade.

Changed in update-manager (Ubuntu):
assignee: Canonical Foundations Team (canonical-foundations) → Martin Pitt (pitti)
status: Confirmed → Triaged
Revision history for this message
Martin Pitt (pitti) wrote :

I synced postgresql-8.4 back into precise universe. It'll still be marked obsolete by p-common.

Changed in update-manager (Ubuntu):
status: Triaged → Fix Released
affects: update-manager (Ubuntu) → postgresql-8.4 (Ubuntu)
Revision history for this message
Mekk (marcin-kasperski) wrote : Re: [Bug 905454] Re: 'postgresql-plperl-8.4' is marked for removal but it is in the removal blacklist

Sidenote: presence of old postgresql versions has more benefits than
easier upgrade - for example gives chance to more gracefully upgrade
slony or other replications. I'd be glad if Ubuntu could keep at least
previous version available unless there are important reasons not to…

Revision history for this message
Ken Tanzer (ktanzer) wrote :

Hi. Just wondering whether this has also been fixed for a Natty-->Oneiric upgrade as well? If so, it's not readily apparent from reading the bug comments, which seem to address Oneiric-->Precise. Thanks.

Revision history for this message
Martin Pitt (pitti) wrote :

Ken Tanzer [2012-04-18 19:03 -0000]:
> Hi. Just wondering whether this has also been fixed for a
> Natty-->Oneiric upgrade as well?

Indeed Natty->Oneiric had a perl 5.10 → 5.12 migration, so if you use
PL/Perl this likely affects you as well.

> If so, it's not readily apparent from reading the bug comments,
> which seem to address Oneiric-->Precise.

And Lucid -> Precise.

Revision history for this message
Ken Tanzer (ktanzer) wrote :

> Indeed Natty->Oneiric had a perl 5.10 → 5.12 migration, so if you use
> PL/Perl this likely affects you as well.

It's more than just likely. Natty-->Oneiric is what DavidL originally reported to open this bug, and what I encountered four days ago and posted in comment #4. I guess I was wondering whether y'all were going to fix (or have fixed) this, which still isn't quite clear to me. Thanks.

Revision history for this message
Ken Tanzer (ktanzer) wrote :

Any chance of getting an answer?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.