Hmm. I just tried and it's still reporting the same problem. The package would also have this information in it wouldn't it. So I tried force installing the package. Then editing the available list but sure enough next time I touch apt-get it uninstalls the package again.

Is there an easy way to modify dependencies of a dpkg file? Could I do it that way? Make a new package based on python2.2?

Jeff

Cade Cairns wrote:

I'm not certain if it will work but you could manually alter the available
file (found in /var/lib/dpkg). Just change the Depends: line for that
package to python2.2. Hope that works for you.

Regards,
Cade Cairns

On Sun, 15 Dec 2002, Jeff Clement wrote:


Well. Looks like I ran into my first big problem with Debian. Sniff...

The system originally came with Python 2.1 installed and a whole schwack of
stuff has dependencies on it. I would rather not remove it.

I am wanting to use Python 2.2. So I install Python2.2 with apt:
apt-get install python2.2

Yeah. So now I have Python2.1 and Python2.2 on my system. And I can install
a lot of python packages for Python2.2 with things like
apt-get install pygame-python2.2

However with one of my packages for Python 2.2 it has Python as a dependency
instead of Python2.2. Python is a "meta package" that is currently pointing
at 2.1. This means whenever I try and install this package it fails because
the Python package is the wrong version even though I do have Python2.2 on
the system.

So my question is how do I get by this? Is there a way to change which
version of Python the meta Python package is pointing at?

I tried force installing the package but next time I installed something it
decided to remove it again.

Does anyone have any ideas?

Jeff





Reply via email to