Bug#683053: unblock: python2.7/2.7.3-2
On Saturday, July 28, 2012 02:14:04 PM Philipp Kern wrote:
> On Sat, Jul 28, 2012 at 03:39:51AM -0400, Scott Kitterman wrote:
> > My recommendation is that you unblock python2.7, but increase the age
> > requirement to 30 days (it's at 14 righ now) and that you also unblock
> > linkchecker (#682603) and I'll NMU pegasus-wm, createrepo, and gwibber,
> > file fore unblocks, etc. In each case the diff is very compact (similar
> > to #682603 in scope). With python2.7 having two weeks to go, this was
> > all the fixed packages can migrate with or before python2.7 so it can be
> > a smooth switch (the fixed packages work fine with either the python2.7
> > in wheezy or unstable there's no need to tightly coordinate things.
>
> Couldn't python2.7 get Breaks on the broken packages or something? I shortly
> talked with doko about that when I thought that only one package is
> affected and hence that was discarded. It is a private undocumented API
> but given that it really does affect other packages, it makes sense to me
> at least.
It could, I suppose. I don't think that, once this is sorted out in
Wheezy/Unstable there is an upgrade issue for Squeeze. If one of the relevant
applications is running during the upgrade it will keep using the old version
of the module. In my estimation, for Squeeze upgrades it's not worth making
the package upgrade sequencing more complicated for the apt resolver.
Scott K
Reply to: