[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Understanding python2.3 migration problems



On Wed, Oct 01, 2003 at 03:36:30PM +0200, Bj?rn Stenberg wrote:
> Colin Watson wrote:
> > 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
> 
> Aha, this means the file was not yet updated at 02:00 CET when my
> script downloaded it. When can the processing reasonably be expected
> to be finished, and the result files downloaded?

It's variable depending on how much work is being done. I'd guess at
maybe 01:30 to 02:00 UTC under "normal" circumstances.

Why not simply download the result files every hour or so with a
Last-Modified-Since: HTTP header, and rerun your script only when you're
told that they've changed? AJ sometimes runs britney by hand at other
times.

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



Reply to: