python-yaml: Depends: python (<2.6) but 2.6.1-0ubuntu1 is to be installed

[chris_c]

Binary package hint: python-yaml

is there no way to automagically check what packages a new package will break dependencies on?

This kind of thing is a common a needless happening not only with python but with various packages from time to time...

[Scott Kitterman (kitterman)]

The package needs rebuilt for the Python 2.6 transition. I'll take care of
it.

[chris_c (c-camacho)]

It would have been nice if this had been done *before* python 2.6 had hit the repo - I have several python apps I cant use until this is resolved...

[Scott Kitterman (kitterman)]

You really can't. Jaunty is a development release. If you need anything
sure to be working at any given moment you shouldn't be running it.

[chris_c (c-camacho)]

It just means rebooting and less testing...

Why can't you release them all at once?

> You really can't.
you dont need 2.6 in the *public* repo without yaml

you could make the package for 2.6 then for yaml and upload them at the same time surely ?
my own custom modules just needed sudo python setup.py install whats different about yaml ?

[Scott Kitterman (kitterman)]

The problem isn't pyyaml specific. It's the scale of the archive. It
makes more sense to get Python transitioned and then deal with modules
after.

[Launchpad Janitor (janitor)]

This bug was fixed in the package pyyaml - 3.08-1build1

---------------
pyyaml (3.08-1build1) jaunty; urgency=low

  * No change rebuild for Python 2.6 transition (LP: #335473)

 -- Scott Kitterman <email address hidden> Fri, 27 Feb 2009 13:59:41 -0500