On Fri, Jun 06, 2003 at 12:10:45PM -0400, David Z Maze wrote: > "Karl E. Jorgensen" <[EMAIL PROTECTED]> writes: > > > debhelper 4.1.45 (=sid/sarge) builds OK, then resulting .deb then > > depends on debconf-utils (>= 1.1.1) [source: debconf] > > > > debconf 1.2.35 (=sarge) build-depends on debhelper (>= 4.1.27) > > > Which makes me wonder: How did debconf/debhelper get into testing/sarge > > in the first place? Somebody must have performed some magic that I > > should be able to do too... > > The way the testing scripts run, the set of packages after the upgrade > need to be consistent, but each individual package upgrade doesn't need > to result in a consistent pool. That is, assuming "depends" rather > than "build-depends" aboove, both new-debhelper and new-debconf could > move into testing, but they'd have to have moved in together.
That makes sense - moving packages into testing in "groups". > I don't actually know whether the testing scripts check build-depends > or not; > http://www.debian.org/devel/testing/ has most of the rules, but (without the trailing '/' I presume) > doesn't actually clarify this. Where would I go to find out? I believe that they *should* check build-dependencies; otherwise building debian from scratch might become impossible... -- Karl E. Jørgensen [EMAIL PROTECTED] http://karl.jorgensen.com ==== Today's fortune: Somebody ought to cross ball point pens with coat hangers so that the pens will multiply instead of disappear.
pgp00000.pgp
Description: PGP signature
