On Fri, Jul 04, 2003 at 03:09:25PM -0700, Ross Boylan wrote: > 3) However, the version in unstable would work, if it were in testing, > wouldn't it? So the question is why the package hasn't migrated down. > The reason appears to have nothing to do with the issues discussed in this > thread
That is incorrect; it is simply that there is an additional issue beyond those discussed in this thread. The primary issue is that apt has release-critical bugs which are not being fixed: http://qa.debian.org/developer.php?excuse=apt The new python-apt cannot enter testing until the new apt does. If you wish to complain about this situation, please contact [EMAIL PROTECTED], since I assume that is who broke python-apt in testing by forcing in a new python (if not, he would know who did). > Oops, I realized arm may just be the first reported failure and there > could be others. But it does look as if it built OK for i386. It built fine everywhere except arm. As far as I can tell from looking at that log, this is either a problem with python or with the buildd environment. I do not think there is anything wrong with python-apt. The fact that no porter has filed a bug regarding this failure makes it seem even less likely that python-apt is at fault. -- - mdz
