Bug#593177: Clarify when dependencies of pre-dependencies are satisfied

2011-03-06 Thread Jonathan Nieder
(switching topics; sorry for the cognitive dissonance) Steve Langasek wrote: > Taken in sum, there is a cost to that documentation. Thanks for a nice summary. > On Sat, Mar 05, 2011 at 06:26:27PM -0600, Jonathan Nieder wrote: >> Bug#593177 brings the possibility of change. In the extreme cas

Bug#593177: Clarify when dependencies of pre-dependencies are satisfied

2010-08-15 Thread Jonathan Nieder
Jonathan Nieder wrote: > this > is about preinst only, which basically means (based on a quick search) > pseudo-essential packages and debconf. Hmm, and python-ure. Maybe we should treat all dependencies of a pre-dependency as pre-dep

Bug#593177: Clarify when dependencies of pre-dependencies are satisfied

2010-08-15 Thread Jonathan Nieder
Russ Allbery wrote: >>> On Sun, Aug 08, 2010 at 07:27:44PM -0500, Jonathan Nieder wrote: Except *new* dependencies of an upgraded pre-depedency may not be present. This is part of the philosophy behind pseudo-essential packages generally using pre-depends for one release when they

Bug#593177: Clarify when dependencies of pre-dependencies are satisfied

2010-08-15 Thread Russ Allbery
Jonathan Nieder writes: > Steve Langasek wrote: >> On Sun, Aug 08, 2010 at 07:27:44PM -0500, Jonathan Nieder wrote: >>> Except *new* dependencies of an upgraded pre-depedency may not be >>> present. This is part of the philosophy behind pseudo-essential >>> packages generally using pre-depends f

Bug#593177: Clarify when dependencies of pre-dependencies are satisfied

2010-08-15 Thread Jonathan Nieder
Package: debian-policy Severity: wishlist Steve Langasek wrote: > On Sun, Aug 08, 2010 at 07:27:44PM -0500, Jonathan Nieder wrote: >> Except *new* dependencies of an upgraded pre-depedency may not be >> present. This is part of the philosophy behind pseudo-essential >> packages generally using p