Re: Understanding python2.3 migration problems

[Colin Watson <cjwatson@debian.org>]

On Wed, Oct 01, 2003 at 02:40:03PM +0200, Bj?rn Stenberg wrote:
> Colin Watson wrote:
> > On Tue, Sep 30, 2003 at 08:29:42PM -0700, Ross Boylan wrote:
> > > The report from
> > > http://bjorn.haxx.se/debian/testing.pl?package=python2.3 looks much
> > > different, and I guess I was expecting Colin's note to be similar.
> > 
> > It's a common mistake to assume that update_excuses.html (which Bj?rn's
> > script uses, I believe) is the only relevant information. In fact
> > update_excuses.html only lists obvious and cheap-to-calculate problems.
> > More expensive checks - counting uninstallable packages after attempting
> > to install each package in turn - are logged in update_output.txt.
> 
> Actually, my script already reads both these files.

Oh, OK, sorry.

> But there is currently no "trying: python2.3" line at all in
> update_output.txt, and hence no result to report. Could this be due to
> the following output at the bottom:
> 
> Hint from ajt: python2.3/2.3.1-1
>  Version mismatch, python2.3 2.3.1-1 != 2.3.1-2
> Not using hint
> 
> Or is there some other reason for this, that perhaps my script could
> detect and report?

python2.3 isn't ready for testing today because it just had a new
version uploaded.

python2.3 (2.2.106-2beta2 to 2.3.1-3)
    Maintainer: Matthias Klose
    Too young, only 0 of 2 days old
    idle-python2.3/ia64 unsatisfiable Depends: python2.3-tk (>= 2.3.1-3)
    python2.3-examples/ia64 unsatisfiable Depends: python2.3 (>= 2.3.1-3)
    Not considered

When you see "Not considered", that means that the package does not go
through the (expensive) stage of processing that produces
update_output.txt.

-- 
Colin Watson                                  [cjwatson@flatline.org.uk]