Bug#846405: dpkg-shlibdeps: scales badly for many binaries

Package: dpkg Version: 1.18.15 Severity: minor Hi, when building the piglit package, the dpkg-shlibdeps invocations take upwards of 30 minutes (on an i7, building inside a tmpfs). Most of the time seems to be spent spawning several thousand instances of dpkg-query. Is there a way to speed this

Re: schroot default chroot path

Johannes Schauer writes: > it would. If anybody knows a good argument for a default location for > schroot containers then I can add such a default. I am not aware of such > a standard path for system-wide schroot directories or tarballs. pbuilder just uses /var/cache/pbuilder

Bug#846164: dpkg-dev: Have dpkg-genchanges support a source+buildinfo-only upload

Guillem Jover: > On Mon, 2016-11-28 at 22:00:32 +0100, Ximin Luo wrote: >> It would be good to be able [..] >> to do a binary build locally, but only upload the source package >> *and* the buildinfo file. > > This was the intention from the beginning. But when I mentioned this > on IRC the other

schroot default chroot path (was: Re: Intent to commit craziness - source package unpacking)

Hi, Quoting Ian Jackson (2016-11-30 12:11:22) > ~Johannes Schauer writes ("Re: Intent to commit craziness - source package > unpacking"): > > sbuild supports multiple backends. The default backend is schroot. How to > > get > > from "apt-get install sbuild" to actually building packages depends

Re: Intent to commit craziness - source package unpacking

~Johannes Schauer writes ("Re: Intent to commit craziness - source package unpacking"): > sbuild supports multiple backends. The default backend is schroot. How to get > from "apt-get install sbuild" to actually building packages depends on the > backend used. For the default schroot backend,

Re: Intent to commit craziness - source package unpacking

Hi, Quoting Ian Jackson (2016-10-04 18:55:14) > Russ Allbery writes ("Re: Intent to commit craziness - source package > unpacking"): > > If sbuild is now at the point where you can just apt-get install sbuild, > > run a single setup command, and be ready to build packages (which is where > >