[wpkg-users] [Bug 144] Removed packages not progressing in priority order if server change applied .

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=144





--- Comment #2 from Keith Jones <k.e.jones at brighton.ac.uk>  2009-02-14 20:33:46 ---
Hiya,

 Thanks for the rundown of dependencies. I think you misunderstood slightly or
I probably mislead you with "looks complex..." :-}

 I usually have everything done on dependancy on our production system. I'm up
to about 4 tiers of abstract dependencies on the profiles alone 8-)

 What I use priority for is, to analyse what happens when you install,
reinstall or modify software with many different options. In this case I was
playing with SQL Express 2005 instances. I "queue" up applying the software in
different ways, set it going and go off to do something else. When I come back
it's easy to pick out the exit codes complaining about not being able to
install over xyz component etc. I bet you'd never guess I'd use it for that but
it does save the odd hour or two of sitting at a keyboard! 

 You can't do that with dependencies without having WPKG roll back changes all
the time because of an error. WPKG is too smart for it's own good and undoes
all my attempts to force crashes :-)

 I think I hit *just* the right combination to trigger a blind spot. There's
definately more to the scenario I had and my debug runs still point at that
fixup code (lines 4328 to 4354) interacting incorrectly somehow.

 When I ran into it I thought it best to bug it while it was fresh in my mind.
I entered this as a "minor" bug because it has so many If's and But's ;-)


 Basically what I had was a pair of packages that couldn't get updated to the
server code because they kept queuing in the wrong order.

 I'm going to try and isolate it more with some dummy files. I have a thought
about what's going on but it's a bit of a complex interaction.

Back shortly!





-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.