On Sat, Nov 13, 2010 at 04:41:29PM +0100, Loïc Minier wrote: > On Fri, Nov 12, 2010, Roger Leigh wrote: > > The main question that needs answering is: > > Are all the packages listed in > > /usr/share/doc/build-essential/essential-packages-list and > > /usr/share/doc/build-essential/list > > available and installable? > > The error message is more confusing than the original one since the > mention of ESSENTIAL as a separate step was bit more explicit; I > suspect the change is not related to your patch though, but rather to > other sbuild updates.
We should probably do one or both of - making the error messages much more explicit about what went wrong - separating the essential and package build deps. The essential and package deps were merged since they can all be installed in a single apt-get/aptitude run, which is more efficient and lets the resolver make a more informed decision based on what the final outcome should be. > I'm not familiar with sbuild, but from reading sbuild-vpkg.patch it > seemed entirely appropriate, but since I can't confirm it fixes > anything, I don't know whether you want to include it or not. > > It seems this bug can be closed since it's a problem in Ubuntu's > build-essential, I'm leaving it open in case you'd like to merge > sbuild-vpkg.patch. I've now applied the patch. It does make sense to do this, but it doesn't make the diagnostics better when things go wrong. It's only activated when $resolve_virtual is enabled, so by default it won't attempt to find virtual packages. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
signature.asc
Description: Digital signature