Re: Policy problem
Evan Simpson writes:
> I'm running into dependency clashes while trying to install wxPython,
> and looking for help.
>
> Since I am a Zope developer, and different versions of Zope rely on
> different versions of Python, I need to have several versions of Python
> installed. In fact, I have installed the packages named "python1.5",
> "python2.1", "python2.2", and "python2.3" in addition to the standard
> "python".
>
> Although I am running stable, I am also using some packages from testing
> and unstable by pinning stable in /etc/apt/preferences and overriding
> the version for specific packages using aptitude. Now I'm trying to
> install "libwxgtk2.3-python" from unstable, and this is where I ran into
> trouble.
>
> "libwxgtk2.3-python" is packaged in accordance with section 2.2.1 of the
> DPP, so it wants "python" to be (>=2.2, <<2.3). My "python" is from
> stable, so it's version 2.1 and the dependency fails even though I have
> Python 2.2 installed. Upgrading to the unstable "python" breaks 17
> other packages.
no, it should not. in unstable, the transition to 2.2 is over. There
are new versions of your 17 packages that you can install.
> I'm new to Debian and slowly learning about packaging; is it possible
> for a package to depend on (python >=2.2, <<2.3 OR python2.2)?
yes, if the package maintainer packs python-foo, python2.1-foo and
python2.2-foo.
> Is there
> some way around this for me, or is the answer "the packager has decided
> to support only the default version -- live with it"?
yes. or maybe package _and_ maintain the version you need.
Reply to: