package python-storm 0.18-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/pyshared/storm-0.18.egg-info/top_level.txt.dpkg-new': No such file or directory

Bug #793695 reported by rajan chatterjee
34
This bug affects 4 people
Affects Status Importance Assigned to Milestone
storm (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

i try it with with root priviledges even then i could'nt resolve it....

ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: python-storm 0.18-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
Uname: Linux 2.6.39-3-generic i686
AptOrdering:
 python-storm: Install
 python-storm: Configure
Architecture: i386
Date: Tue Jun 7 00:46:03 2011
DpkgTerminalLog:
 Preparing to replace python-storm 0.18-0ubuntu1 (using .../python-storm_0.18-1_i386.deb) ...
 Unpacking replacement python-storm ...
 dpkg: error processing /var/cache/apt/archives/python-storm_0.18-1_i386.deb (--unpack):
  unable to open '/usr/share/pyshared/storm-0.18.egg-info/top_level.txt.dpkg-new': No such file or directory
ErrorMessage: unable to open '/usr/share/pyshared/storm-0.18.egg-info/top_level.txt.dpkg-new': No such file or directory
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: storm
Title: package python-storm 0.18-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/pyshared/storm-0.18.egg-info/top_level.txt.dpkg-new': No such file or directory
UpgradeStatus: Upgraded to oneiric on 2011-06-06 (0 days ago)

Revision history for this message
rajan chatterjee (rajanchatterjee) wrote :
Revision history for this message
Julian Taylor (jtaylor) wrote :

this is the same issue foolscap had.
It is caused by the new build-depend on python-setuptools which creates an egg folder instead of a egg file.
With multiple supported python versions dpkg will fail on certain file ordering in the data.tar.gz
see foolscap 0.6.1-4 for a workaround.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report. This is only a problem when upgrading from storm 0.18-0ubuntu1 to the latest 0.18 storm package, so will only affect users running Oneiric (0.15 is in natty)
I'm setting the status to triaged/low but I think this bug could be closed because this defect only affect the upgrade from Oneiric to Oneiric and it is expected on a development release.

Changed in storm (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Colin Watson (cjwatson) wrote :

Given that this only affected upgrades within a development release which is now long since EOL, and since the Python packaging infrastructure now looks quite different, I think it makes sense to just close this bug. Sorry that we didn't deal with it better at the time!

Changed in storm (Ubuntu):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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