Making sure all dependencies are met when using Pungi

[Jesse Keating]

On Monday 02 July 2007 00:31:15 William F. Acker WB2FLW +1-303-722-7209 wrote:
> As packages are updated, they can grow dependencies.  An example is that
> libpurple now requires libhowl.so.o, found in avahi-compat-howl.  Yet,
> Pungi doesn't complain about the missing package.  In the logs, I find
> that when libpurple is examined, there's a  list of dependencies, but
> libhowl.so.0 is nowhere to be found.  Where does Pungi get its dependency
> info?  One would think that it comes from the metadata in the repo, which
> is local, in my case.

Gets it from the repo yes.  There is a yum bug, fixed by 3.2.1 I do believe, 
that would make yum sometimes not complain about missing deps.

Also look in your logs for WARNINGS regarding missing deps.  I fixed pungi's 
reporting of missing deps recently.

-- 
Jesse Keating
Release Engineer: Fedora
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-buildsys-list/attachments/20070702/57f6be42/attachment.sig>