Tracking down broken dependencies in devel

[Michael Schwendt]

On Tue, 2 Jan 2007 10:29:43 +0100, Gianluca Sforna wrote:

> On 12/31/06, Kevin Fenzi wrote:
> >
> > I understand that devel is often in a state of flux as dependencies get
> > upgraded and packages need to be rebuilt and tweaked, but I don't think
> > it's very good to have things that are broken for many months.
> > If you run into problems rebuilding your package, you should ask for
> > help on the list or upstream, IMHO.
> 
> My broken deps in -devel can be fixed by removing the offending packages:
>        kmod-sysprof-kdump - 1.0.7-1.2.6.18_1.2849.fc6.1.i686    (25 days)
>        kmod-sysprof-xen - 1.0.7-1.2.6.18_1.2849.fc6.1.i686    (25 days)
>        kmod-sysprof-xen - 1.0.7-1.2.6.18_1.2849.fc6.1.x86_64    (25 days)
> 
> BTW, I am not even sure why they are still there...

Because kmod- packages are excluded from automated pruning.

This is correct for final releases of the distribution, but apparently not
for Rawhide. 

Does Rawhide contain only a single kernel package release at a time? It
seems so. If that is true, we can simply drop "kmod-" from the whitelist,
and let repoprune kill the old package releases.