Re: problem with python in Debian/unstable
On Wed, Nov 26, 2003 at 01:17:37PM -0500, Kevin Coyner wrote:
> I'm in the same boat as a couple other people regarding this subject:
Ah, unstable users who can't resolve a simple dependency loop.
> Just by way of background, could someone briefly explain why there is a
>
> python
> python2.1
> python2.2
> python2.3
Because there is a need to be able to install multiple versions without
them overriding each other. The package 'python' brings in whatever the
current default version is. The others, obviously, are earlier versions.
> and which one(s) of these I should stick with?
Python 2.3 is the current version in unstable. If you have software
installed that still depends on prior versions, then you will have one or
more of the prior installed.
> Seems that if I apt-get remove any one of them, I end up removing a lot
> of other dependent programs as well.
Good... then the dependency resolution system is working.
> But it also seems that python and python2.3 don't want to live together.
No, apt is installing the packages in the wrong order. A file moved from
the python2.3 deb to the python deb, so apt needs to remove the python2.3
deb before it can install the python deb. Except the python deb depends on
the python2.3 deb. Fun, huh?
Simply installing the packages yourself using the --auto-deconfigure flag
(which dpkg happily pointed out to you) solves the problem.
--
Marc Wilson | Marry in haste and everyone starts counting the
msw@cox.net | months.
Reply to: