On Thu, Sep 24, 2009 at 11:53:12PM +0200, Ralf Treinen wrote: > Hello, > > > But dpkg-dev is built-essential, and so already installed > > in the chroot, and so the edos-builddebcheck part should always > > consider built-essential as installable, atleast for the usage > > in wanna-build. > > What should happen when a package has a *versionend* build-dependency > on a package that is build-essential? Depending on the answer I > see two different ways to implement this is in the edos-builddebcheck wrapper. > > If only a non-versionend build-dependency on a build-essential package > should be considered always satisfied: in this case the wrapper should > also generate a new package that provides all the build-essential > packages. > > If any build-dependency on a build-essential package should be considered > satisfied, no matter whether versionend or not: in this case the wrapper > should just drop all the dependencies of build-essential packages. > (This leaves the question open what to do with conflicts of build-essential > packages, which is somewhat delicate when one really wants to treat > correctly all the possible corner cases. This is probably not very > relevant in practice).
So you're asking what to do with: Build-Depends: dpkg-dev (>= 1.16) (With the current version being 1.15.4) I guess the question in that case is what will sbuild do. As far as I know, sbuild never by itself upgrade things, it will only try to install new packages, and if those depend on a newer version of something that's already installed, it will be upgraded. So as far as I understand, just build-depending on a version for a build-essential package (or anything already in the chroot) will not get that version installed in the chroot, and it will fail anyway. So with the current sbuild behaviour it doesn't really matter, it will most likely fail anyway. But if it would stay in bd-uninstallable state until the version it build-depends on was uploaded, it would probably be better. You'd know the version is available and just need to upgrade the chroot. So I think I would prefer the option that would make packages that will fail to build anyway in bd-uninstallable state. PS: Please note that it's all the essential + build-essential packages and their depedencies that are installed in the chroot and that Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
