Debugging rpm package installation order

Jeffrey Johnson n3npq at
Fri Aug 9 17:58:57 CEST 2013

On Aug 9, 2013, at 7:55 AM, Jacek Konieczny wrote:

>> The easiest way to identify if a "fix" is functional is to use this
>> macro to select exactly one edge to ignore in order to break the LOOP.a
> Exactly one edge of 30 problematic edges reported?

Yes. Eliminating any edge eliminates the loop. The remaining
29 edges are usually sufficient to provide adequate ordering info to tsort.

Also: Fix the 1st LOOP detected first. The errors cascade adding to complexity.

> Maybe the package dependencies are right, but the RPM dependency checking is
> broken for some reason? Any ideas?

Maybe. I can say that the existing rpm implementation has been used by many for
years without any change whatsoever.

FIx your LOOP before guessing at what is broken.

73 de Jeff

More information about the pld-devel-en mailing list