[Pkg-lyx-devel] Bug#286555: Lyx is removed from unstable sytems since python 2.4 is now "standard" for python
Aron T
Aron T <aront54@gmail.com>, 286555@bugs.debian.org
Mon, 20 Dec 2004 18:49:11 -0500
Exactly. But when you update certain packages in unstable they "pull"
in Python 2.4, and the python package now points to python2.4. Then
lyx-qt gets removed because lyx-common gets removed because the
dependencies of lyx-common are apparently set up wrong. i.e. even
though I still have python 2.3 installed in addtion to python2.4,
(i.e. 2.4 does not remove 2.3) the fact that the python package now
points to 2.4 confuses the issue, and lyx-common thinks it no longer
has the proper python available.
I'm not familiar enough with how the dependency system works, but the
correct solution should be that lyx should check for the presence of
python2.1 or python2.2 or python2.3 and not look at what the python
package is.
Hope that helps you understand the problem better. Thanks.
On Mon, 20 Dec 2004 17:27:34 -0500, Erinn Clark <erinn@double-helix.org> wrote:
> package lyx-common
> tags 286555 unreproducible moreinfo
> thanks
>
> * Aron T <aront54@gmail.com> [2004:12:20 15:33 -0500]:
> > Because unstable now uses Python 2.4, and because of how lyx-common
> > dependencies are set up (i.e. an explicit requirement for python 2.3
> > or less), lyx-common (and hence lyx-qt and lyx-forms) are no longer
> > available in unstable. Since Python 2.3 is not removed by the
> > installation of 2.4 it seems this should be relatively easy to fix,
> > and lyx should be available on systems that also have 2.4
>
> Thanks for the bug report.
>
> First of all, all of the lyx components are still in unstable.
> (packages.debian.org shows all of them still present.)
>
> Second of all, python still provides python2.3, so 2.4 is not
> "standard".
>
> How are you seeing this behavior?
>
> --
> off the chain like a rebellious guanine nucleotide
>