Re: Debugging rpm package installation order

2013-08-11 Thread Jacek Konieczny
On Fri, 09 Aug 2013 16:49:28 -0400 Jeffrey Johnson wrote: > > But THERE IS NO LOOP. RPM shows loop due to some imaginary > > dependency. > > > > Before shouting (or comparing to rpm-4.5 behavior), It was a bit rude, indeed. But I am frustrated. And my mail with important details didn't get thro

Re: Debugging rpm package installation order

2013-08-09 Thread Jeffrey Johnson
On Aug 9, 2013, at 4:39 PM, Jacek Konieczny wrote: > On Fri, 09 Aug 2013 11:58:57 -0400 > Jeffrey Johnson wrote: >> 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. > >

Re: Debugging rpm package installation order

2013-08-09 Thread Jacek Konieczny
Re-sending this mail… it was not sent for some reason… On Fri, 9 Aug 2013 13:55:30 +0200 Jacek Konieczny wrote: > First two are clear: > > iproute2-3.4.0-1.aos2.i686 requires '/bin/sh', so it pulls pdksh… > then pdksh-5.2.14-56.aos2.i686 requires '/usr/share/man/man1' and…? > > axeos-pbx-api-0

Re: Debugging rpm package installation order

2013-08-09 Thread Jacek Konieczny
On Fri, 09 Aug 2013 11:58:57 -0400 Jeffrey Johnson wrote: > 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. But THERE IS NO LOOP. RPM shows loop due to some imaginary depen

Re: Debugging rpm package installation order

2013-08-09 Thread Jeffrey Johnson
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

Re: Debugging rpm package installation order

2013-08-09 Thread Jacek Konieczny
On Thu, 08 Aug 2013 13:52:02 -0400 Jeffrey Johnson wrote: > What follows is a dependency LOOP with exactly the same information > as before. Before the RPM upgrade when I got a 'LOOP:' message, it contain two or three clearly related packages: error: LOOP: error: removing lighttpd-1.4.28-6.aos1.

Re: Debugging rpm package installation order

2013-08-08 Thread Jeffrey Johnson
On Aug 8, 2013, at 3:56 AM, Jacek Konieczny wrote: > > Hi, > > I am building a system image for a PLD-based distribution using poldek. > It used to work well until I have upgraded my RPM from 4.5 to 5.4.12. > Now the packages are installed in wrong order, %post scripts fail and > the whole imag

Debugging rpm package installation order

2013-08-08 Thread Jacek Konieczny
Hi, I am building a system image for a PLD-based distribution using poldek. It used to work well until I have upgraded my RPM from 4.5 to 5.4.12. Now the packages are installed in wrong order, %post scripts fail and the whole image build fails. poldek --verify=order gives a reasonable order: No