Making sure all dependencies are met when using Pungi

Sun, 01 Jul 2007 21:34:59 -0700

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. 

--
Bill in Denver

--
Fedora-buildsys-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list






















					Reply via email to