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

Re: update excuses: what does "but foo is screwed anyway"?



On Wed, Mar 21, 2001 at 02:42:20PM +0100, Josip Rodin wrote:
> On Wed, Mar 21, 2001 at 01:39:09PM +0100, Marcelo E. Magallon wrote:
> >  Another side issue: what does:
> > 
> >    * foo-package uploaded XX days ago, out of date by YY days!
> >    * valid candidate (will be installed unless it's dependent upon
> >      other buggy pkgs)
> > 
> >  mean?  In particular, if it's a valid candidate, why hasn't it been
> >  installed already?
> 
> Because it depends on a package that is buggy and won't enter testing.

Can't the script traverse the dependency graph for us? Saying for
example:

valid candidate (but depends on libfoo, which depends on libbar, which 
is not a valid candidate).

(No need to traverse the whole graph, I wouldn't think.  Just
first-failure would do as a pointer).

Jules



Reply to: