Dear Python, leave me alone

So yet once again Mr python decide to tease me when i do `apt-get dist-upgrade`:

Setting up python-lxml (2.0.5-1) ...
/var/lib/dpkg/info/python-lxml.postinst: /usr/bin/pycentral: /usr/bin/python: bad interpreter: No such file or directory
dpkg: error processing python-lxml (--configure):
 subprocess post-installation script returned error exit status 126
...
Errors were encountered while processing:
 epiphany-extensions
 bzr
 gnome-media-common
 libgnome-media0
 gnome-media
 pidgin
 python-lxml
E: Sub-process /usr/bin/dpkg returned an error code (1)

Comments

Anonymous said…
Hello! If apt-get -f install does not work you can try editing var/lib/dpkg/info/package-giving-error.postrm

and add after #!/bin/sh this code:
exit 0, run the command and then remove the exit 0.
May 30, 2008 at 3:58 PM
chrismurf said…
Looks to me like you're missing your /usr/bin/python symlink. You could try the following:

sudo ln -s /usr/bin/python2.5 /usr/bin/python
May 30, 2008 at 4:50 PM
Anonymous said…
I think its time you switched to a distro that works. Obviously debian is just too retarded with python... I'll have a look on monday if you're still having problems but seriously dude this is getting ridiculous.
May 31, 2008 at 1:42 AM
zeenix said…
dierre! Nice. i'll try. Thanks

chrimurf: Thats what we did last time I had a python problem so the link should have been there but now that i checked, it's all gone. So i guess I'll have to do this manually again. Thanks.

Karl: I refuse to change my distro just because some developers decided to re-write some nice and fast GNOME applications in a scripting language whose interpreter is not well-maintained in one of the most popular distros out there.

There are reasons I got in love with Vala you know. :)
May 31, 2008 at 2:08 AM
Unknown said…
You should probably stop using dist-upgrade for upgrading Debian Unstable. That *will* break.

Just use aptitude.
May 31, 2008 at 2:11 AM
zeenix said…
Ross: Why is that different than `apt-get dist-upgrade` ? I use debian testing btw so it shouldn't be as unstable as unstable. :)
May 31, 2008 at 2:14 AM
Pachi said…
You should be using $sudo aptitude safe-upgrade
and, iff you really know what you're doing, $sudo aptitude dist-upgrade after it.
With dist-upgrade you're allowing compatibility breaking changes to enter your system.
May 31, 2008 at 2:32 AM
Anonymouz said…
If this happened on Red Hat derived distribution, it would be called RPM 'dependancy' hell.

This is the packagers and packaging fault, not the program.
May 31, 2008 at 3:14 AM
Unknown said…
It sucks when this stuff doesn't work, but all of the details are hidden in the error messages.

The "bad interpreter" error means that a script was run which started with

#!/usr/bin/python

and something was bad about the interpreter: "/usr/bin/python". In this case, it doesn't exist (possibly the ultimate in bad :).

You can/should follow @chrismurf's suggestion of making the symlink, but also might want to investigate why there isn't a symlink made naturally with your python.

I don't know about @wademealing's comment. I don't think that there's a dependency problem -- just that your python install is broken. If your python install didn't exist at all, then I'd call it a dependency problem (as the package with the post-install script should require python as a dependency). But maybe I missed some details...
May 31, 2008 at 10:31 AM
Juhaz said…
This comment has been removed by the author.
June 2, 2008 at 3:58 AM
Juhaz said…
There are reasons I got in love with Vala you know. :)

And those reasons would suddenly vanish if Debian packager of Vala did a bad job, like Debian packagers of Python do? That does not sound particularly logical.

Note that the python packages are not unmaintained or undermaintained - they're overmaintained. Debian people have this weird urge to add their own insane "python-support" and "pycentral kludges that just break things without any real gain, if they were just packaging upstream software you'd never see this kind of issues.
June 2, 2008 at 4:00 AM
zeenix said…
There are reasons I got in love with Vala you know. :)

And those reasons would suddenly vanish if Debian packager of Vala did a bad job, like Debian packagers of Python do? That does not sound particularly logical.

There can't possibly be those problems with Vala since Vala does not introduce any runtime dependencies. Please think/study a bit before getting pissed at what i say. :)
June 2, 2008 at 4:11 AM
Juhaz said…
I get pissed because you act like Debian can do no wrong, even though it's obvious that they are to blame, and then start looking for a scapegoat in Python.

In the end, it doesn't matter a while lot where the dep comes from. If lots of stuff uses something, you should be very careful to not break it. Would you still absolve Debian of all responsibility if they chose to break libc or glib or gtk instead?
June 2, 2008 at 4:50 AM
zeenix said…
I get pissed because you act like Debian can do no wrong, even though it's obvious that they are to blame, and then start looking for a scapegoat in Python.

I didn't say that at all, please re-read what i wrote a few times with a cool mind. Also note that I was happy redhat (and then Fedora) user until I was forced to move to debian/ubuntu because Fedora packages were always optimized for high-end machines and not my (not so) low-end machines.

Would you still absolve Debian of all responsibility if they chose to break libc or glib or gtk instead?

The fact is that Debian/Ubuntu has quite a big amount of users/developers (compared to that of Fedora) and many of them are GNOME users so I think a GNOME developer should check weather or not the dependency he is introducing to his software has some problem in the the most widely used distros or not.

And now for a direct question to your answer, no! I will immediately switch to another distro if Debian's support for such basic libs will be as poor as that of python. So far, it never happend.
June 2, 2008 at 5:10 AM
Anonymous said…
Juhaz, you can’t say that python-central/python-support is useless. They don’t bring anything visible, but under the scene this is what allows Python packages to install smoothly, doing correctly many things that distutils (and, much worse, setuptools) do wrong or don’t do at all.

The real problem here (just like in your previous post) is that python-central is full of bugs and not correctly maintained.
June 3, 2008 at 3:50 AM
Post a Comment

Popular posts from this blog

Welcome to the virtual world!

Image
About two months ago I informed  the followers of this blog that I will now be working on SPICE project  for Red Hat . Judging from the questions I was asked after that, I realized that not many people know about SPICE so I thought I write at least one blog entry dedicated to explaining what SPICE is all about. Before I get to SPICE itself, let me first introduce you to the world SPICE lives in. Virtualization and Virtual Machines (VMs) For some reason, I feel that I should leave the definitions to wikipedia  and only quote it so that is what I am going to do: " Virtualization, in computing, is the creation of a virtual (rather than actual) version of something, such as a hardware platform, operating system, a storage device or network resources. " " A virtual machine (VM) is a "completely isolated operating system installation within your normal operating system".Today, this is implemented by either software emulation or hardware virtualization ". V...
Read more

clutter-gst

After I was informed about the existence of ClutterGstVideoSink, I quickly modified my super-video application to make it use that. But as soon as i did that, i stopped getting even the static image. After careful analysis for days, I figured that I was supposed to call gst_bus_add_signal_watch() on the pipeline bus since ClutterGstVideoSink uses messages on the bus combined with signal handlers to render the frames in the application thread. This is obviously a 'dirty' hack; a hack because gst elements are supposed to do all the media processing in the pipeline thread, dirty because gst bus is not meant for media transport. After this realization, I had been working on it from time to time. First I tried to make the actual rendering happen in the gst pipeline thread by using the clutter's thread safety primitives and that worked quite nicely in the end except for one minor problem: The call to clutters rendering thread blocks if it happens after the clutter main loop has b...
Read more

Shame Ubuntu shame

I am no more a fan of Ubuntu. The reason is their recent demonstration of lack of community spirit. Here is the release announcement of Ubuntu hardy alpha6. If you scroll-down you can see the gnome-system-monitor's new cool "Resources" view featured with a nice screenshot. Since Karl-Lattimer worked really hard to make this happen, he asked to be given personal credit on that page. Don't know about others but I see this as a very reasonable thing to ask. The result of this request can be seen in the announcement of hardy beta. They just removed the feature from the announcement. Shame Ubuntu shame. UPDATE: It's interesting how most of the comments that are from people who got pissed without actually caring to understand the main point of this blog entry (which me and Karl-Lattimer tried to emphasize in the comments) are posting as Anonymous. :) Acknowledging the possibility that they might not think comments are worth reading before commenting, let me make it c...
Read more