Re: pbulk dependency resolution failed

[Joerg Sonnenberger <joerg%britannica.bec.de@localhost>]

On Mon, Jun 15, 2009 at 10:33:41AM -0400, Jan Schaumann wrote:
> pbulk-resolve: No match found for dependency py26-numpy>=1.0 of package
> py26-fonttools-2.2
> pbulk-resolve: No match found for dependency py23-gtk2>=2.10.0 of
> package py23-goocanvas-0.14.1
> pbulk-resolve: No match found for dependency py23-gtk2>=2.8.4 of package
> py23-goocanvas-0.14.1
> pbulk-resolve: No match found for dependency py23-cairo>=1.8.4 of
> package py23-goocanvas-0.14.1
> pbulk-resolve: No match found for dependency py23-cairo>=1.0.2 of
> package py23-goocanvas-0.14.1
> pbulk-resolve: No match found for dependency py23-gtk2>=2.8.5nb1 of
> package py23-goocanvas-0.14.1
> pbulk-resolve: No match found for dependency py23-cairo>=1.0.2nb1 of
> package py23-goocanvas-0.14.1
> pbulk-resolve: No match found for dependency py26-OpenSSL>=0.6 of
> package py26-twisted-8.1.0
> 
> So what does that mean?  That these packages are broken?  Are there bugs
> open to get this fixed?

The packages have dependencies that can't be fulfilled. Normal solution
is to either check if the depending packages can deal with the newer
Python version (py-numpy, py-OpenSSL) or needs to be masked (py-gtk,
py-cairo).

> > > So... what am I going to do with these messages?  How would I proceed to
> > > resolve these so that pbulk can actually run?
> > 
> > You can always set ignore_missing_dependencies, which will cut the
> > transitive closure of unresolvable packages away.
> 
> Will these packages lateron still show as broken or will they be treated
> as non-existent?

Non-existent.

Joerg