package python3.0 3.0~rc1+20081027-0ubuntu1 failed to install/upgrade: Versuche, ?/usr/lib/python3.0/lib-dynload/_pickle.so? zu ?berschreiben, welches auch in Paket python3.0-minimal ist

Bug #301597 reported by Robert D. Martin
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python3.0 (Ubuntu)
Fix Released
Low
Matthias Klose

Bug Description

Binary package hint: python3.0

lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

Info to ubuntu
Vielen Dank für Ihr Interesse an Ubuntu 8.10, dem Intrepid Ibex (»unerschrockener Steinbock«) — veröffentlicht im Oktober 2008.

(??? is it normal for Intrepid Ibex to be indicated here, though I upgraded to jaunty?)

apt-cache policy python
python:
  Installiert: 2.5.2-3ubuntu1
  Kandidat: 2.5.2-3ubuntu1
  Versions-Tabelle:
 *** 2.5.2-3ubuntu1 0
        500 ftp://ftp.fu-berlin.de jaunty/main Packages
        100 /var/lib/dpkg/status

When I started the update-manager this morning expecting to carry out my habitual daily upgrade of the OS, an error message appeared stating that the packages cache be damaged. I therefore ended the update-manager and opened a terminal from which per sudo to use apt-get to check, update and then upgrade everything.

the message pertaining to python3.0 3.0-rc1+20081027-0ubuntu1 then appeared ...:

"package python3.0 3.0~rc1+20081027-0ubuntu1 failed to install/upgrade: Versuche, ?/usr/lib/python3.0/lib-dynload/_pickle.so? zu ?berschreiben, welches auch in Paket python3.0-minimal ist"

My assumption: the cache got somehow damaged independently of any correlation to the specific package that as a result could not get updated/installed, in this case python(...). I am guessing that I need to use dpkg somehow to re-create the cache as a whole or something, but just in case I be in error I am sending this python related error message along.

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: Versuche, »/usr/lib/python3.0/lib-dynload/_pickle.so« zu überschreiben, welches auch in Paket python3.0-minimal ist
Package: python3.0 3.0~rc1+20081027-0ubuntu1
SourcePackage: python3.0
Title: package python3.0 3.0~rc1+20081027-0ubuntu1 failed to install/upgrade: Versuche, »/usr/lib/python3.0/lib-dynload/_pickle.so« zu überschreiben, welches auch in Paket python3.0-minimal ist
Uname: Linux 2.6.27-8-generic i686

Related branches

Revision history for this message
Robert D. Martin (ets3rodamar) wrote :
Revision history for this message
Robert D. Martin (ets3rodamar) wrote :

After trying...:

sudo dpkg --configure -a
sudo apt-get update

I then tried...:
sudo apt-get upgrade

...which resulted in the following messages...:

Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut
Lese Status-Informationen ein... Fertig
Probieren Sie »apt-get -f install«, um diese zu korrigieren.
Die folgenden Pakete haben nicht erfüllte Abhängigkeiten:
  python3.0: Hängt ab: python3.0-minimal (= 3.0~rc1+20081027-0ubuntu1) aber 3.0~rc3-0ubuntu3 ist installiert
E: Nicht erfüllte Abhängigkeiten. Versuchen Sie, -f zu benutzen.

Do I guess right that the intrepid version be being somehow considered the proper current version with the result that the jaunty version be considered uninstallable?

Revision history for this message
Robert D. Martin (ets3rodamar) wrote :

Please note that I am using the OpenOffice.org Version 3 under jaunty, which I download and install however from out of the intrepid repository...:

http://ppa.launchpad.net/openoffice-pkgs/ubuntu intrepid main

Does that somehow cause a mix-up resulting in the above problem?

Revision history for this message
Robert D. Martin (ets3rodamar) wrote :

OK... after the above measures were taken, I was able to use synaptic to install the python3 package...:

"python3.0 (Version 3.0~rc1+20081027-0ubuntu1) wird auf die Version 3.0~rc3-0ubuntu3 aktualisiert"

and in the aftermath to then install first one then the newest mono packages. Apparently, everything (?) is now okay, at least as far as synaptic be concerned.

Unless there be other matters involved here of which I am not aware, please therefore consider this case to have become solved.

Sorry to have troubled you.

Revision history for this message
Kjell Braden (afflux) wrote :

No, I can reproduce this issue when upgrading from intrepid to jaunty. Note that you can workaround this problem by removing python3.0 and python3.0-minimal and installing them again.

Changed in python3.0:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Kjell Braden (afflux) wrote :

Adding python3.0-minimal as a pre-depends for python3.0 should fix the issue.

Changed in python3.0:
status: Confirmed → Triaged
Revision history for this message
James Westby (james-w) wrote :

Hi Kjell,

Thanks for working on this.

While Pre-Depends may be the correct solution here there is a
reluctance to add them if other solutions are possible.

Could you post your assesment of the problem and the reasoning
for a Pre-Depends to the ubuntu-devel mailing list so that
other solutions can be proposed?

Thanks,

James

Revision history for this message
Colin Watson (cjwatson) wrote :

Surely the proper solution to files moving between packages is Replaces, not Pre-Depends.

Revision history for this message
Colin Watson (cjwatson) wrote :

That is, when files move from package A to package B, B should Replaces: A (<< first-version-where-files-are-no-longer-in-A).

Matthias Klose (doko)
Changed in python3.0:
assignee: nobody → doko
status: Triaged → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package python3.0 - 3.0~rc3-0ubuntu4

---------------
python3.0 (3.0~rc3-0ubuntu4) jaunty; urgency=low

  * Update to 20081127 from the py3k branch.
  * Ensure that all extensions from the -minimal package are statically
    linked into the interpreter. LP: #301597.
  * Include expat, _elementtree, datetime in -minimal to link
    these extensions statically.

 -- Matthias Klose <email address hidden> Thu, 27 Nov 2008 08:49:02 +0100

Changed in python3.0:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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