Re: Backporting of debhelper: loops in dependencies !?
"Karl E. Jorgensen" <karl@jorgensen.com> 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. 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
doesn't actually clarify this.
--
David Maze dmaze@debian.org http://people.debian.org/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
Reply to: