On Sat, Sep 11, 2010 at 21:49:33 +0200, Didier 'OdyX' Raboud wrote:
> So from here I see some options (with my opinion in parentheses)
> i) Removing PySide from Squeeze
> (I think it would be sad).
> ii) Keeping the current PySide in Squeeze and request the maintainer (me) to
> provide pa
There still around 50 packages depending, recommending or suggesting python2.5,
without explicitly build-depending on python2.5 or python2.5-dev. A large chunk
of these seem to be release critical, especially those which depend on python
python2.6 (libpython2.6) and python2.5. Another chunk of
On Sun, Sep 26, 2010 at 21:49:28 +0200, Matthias Klose wrote:
> The easier solution would be to remove python2.5 from the list of
> supported python versions and rebuild.
>
NAK. The solution to an incomplete python transition is not to
introduce yet another one.
Cheers,
Julien
signature.asc
D
* Matthias Klose , 2010-09-26, 21:49:
A large chunk of these seem to be release critical, especially those
which depend on python python2.6 (libpython2.6) and python2.5.
On the contrary, these are safe to ignore in most cases. Such
dependencies are typically autogenerated because Python module
On 09/26/2010 09:49 PM, Matthias Klose wrote:
> There still around 50 packages depending, recommending or suggesting
> python2.5, without explicitly build-depending on python2.5 or
> python2.5-dev.
Yes, and? We will have Python2.5 in Lenny thanks to your own fault of starting
the transition more t
Hello Matthias,
* 2010-09-26 22:52, Matthias Klose wrote:
> At least one of the binary packages built by these source packages ends
> up with a dependency, recommendation or suggestion on python2.5 without
> having an explicit build dependency on python2.5 or python2.5-dev.
These packages provide
6 matches
Mail list logo
