python-profiler for Python 2.6 fails to overwrite python2.5 lib

Asked by Jason R. Coombs

I have Ubuntu Lucid with the deadsnakes PPA added for Python 2.7, 3.2, and 2.5. I've since found that I need a profiler on my host, so I attempted to install it with "aptitude install python-profiler" but got this error:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following NEW packages will be installed:
  python-profiler
0 packages upgraded, 1 newly installed, 0 to remove and 9 not upgraded.
Need to get 0B/29.8kB of archives. After unpacking 188kB will be used.
Writing extended state information... Done
(Reading database ... 72747 files and directories currently installed.)
Unpacking python-profiler (from .../python-profiler_2.6.5-0ubuntu1_all.deb) ...
dpkg: error processing /var/cache/apt/archives/python-profiler_2.6.5-0ubuntu1_all.deb (--unpack):
 trying to overwrite '/usr/lib/python2.5/profile.py', which is also in package python2.5 0:2.5.6-0~ppa1~lucid1
Errors were encountered while processing:
 /var/cache/apt/archives/python-profiler_2.6.5-0ubuntu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done

Why is python-profiler_2.6.5-0ubuntu1_all.deb trying to write to /usr/lib/python2.5 ? Is this a bug? Is there a recommended workaround?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu python-profiler Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

sudo dpkg --force-all -i /var/cache/apt/archives/python-profiler_2.6.5-0ubuntu1_all.deb ; sudo apt-get -f install

There is a file in 2 packages, Ubuntu doesn't like that. I suggest you report this to the PPA maintainer so this conflict can be resolved.

Revision history for this message
Jason R. Coombs (jaraco) said :
#2

Maybe I should have been more explicit with my first question:

Why if Ubuntu Lucid ships with only Python 2.6 would any of its packages (including python-profiler) try to install a file into /usr/lib/python2.5 ?

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

Not sure, backward compatibility maybe?

Revision history for this message
Jason R. Coombs (jaraco) said :
#4

Does it make sense that python-profiler in the multiverse should be adding profiling modules for versions of Python which are not available in that repo? That is, it seems more appropriate for deadsnakes to include the file than for python-profiler to do so.

Revision history for this message
Launchpad Janitor (janitor) said :
#5

This question was expired because it remained in the 'Open' state without activity for the last 15 days.