On Sun, May 18, 2003 at 10:01:31PM -0500, Taral <[EMAIL PROTECTED]> was heard
to say:
> Looks like the python2.2 stuff migrated into testing without noticing
> that it breaks python-apt. Anyone using python-apt (e.g. aptitude users)
> are advised not to upgrade.
aptitude has nothing to do with
On Sun, May 18, 2003 at 11:29:14PM -0500, Adam Majer wrote:
> On Sun, May 18, 2003 at 10:01:31PM -0500, Taral wrote:
> > Looks like the python2.2 stuff migrated into testing without noticing
> > that it breaks python-apt. Anyone using python-apt (e.g. aptitude users)
> > are advised not to upgrade.
On Sun, May 18, 2003 at 10:01:31PM -0500, Taral wrote:
> Looks like the python2.2 stuff migrated into testing without noticing
> that it breaks python-apt. Anyone using python-apt (e.g. aptitude users)
> are advised not to upgrade.
>
> Anyone know how exactly the testing scripts managed to miss th
On Sun, May 18, 2003 at 10:01:31PM -0500, Taral wrote:
> Looks like the python2.2 stuff migrated into testing without noticing
> that it breaks python-apt. Anyone using python-apt (e.g. aptitude users)
> are advised not to upgrade.
Huh? What's aptitude got to do with python-apt?
Package: aptitude
Looks like the python2.2 stuff migrated into testing without noticing
that it breaks python-apt. Anyone using python-apt (e.g. aptitude users)
are advised not to upgrade.
Anyone know how exactly the testing scripts managed to miss this
breakage?
--
Taral <[EMAIL PROTECTED]>
This message is digit
5 matches
Mail list logo