On 05/26/2015 02:58 PM, Thorsten Glaser wrote: > cowbuilder continues to work for me (and it’s pretty much pbuilder). > I would ask you, Adrian, to refrain from shooting out “I think the > only real solution is” so quickly.
Yet you do the same two paragraphs later ;). But again, there are more issues with pbuilder. I have had many packages where I had to install certain debhelper packages on the host system outside the chroot before I was able to build the package. This doesn't look like a very clean solution to me. Furthermore, using sbuild is just way more flexible and with btrfs snapshots, it's unbeatenly fast, really :). > The change in dpkg-buildpackage is annoying, but has been forewarned > since etch or thereabouts already, and I’ve already got a bloody nose > with one package requiring stuff from its B-D to create the source > package (due to debian/rules clean). But this likely only affects > pdebuild, not pbuilder itself. > > The fix is easy of course: don’t use pdebuild, dpkg-buildpackage -S -d > then run the .dsc that results in with pbuilder. Yeah, but what's the point about using pbuilder then. I don't see anything where it beats sbuild and your only argument seems to be again "Don't fix it, because it's old and I have used it for years" (TM) ;). I'd be happy to be enlightened about this though. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
