Re: Test builds in gbp patch-queue branch [was: Re: Is there a way to preserve pbuilder chroot environment?]
+++ Ross Gammon [2014-03-01 23:37 +0100]:
> Now you have all helped me to realise that I can spam with 'debian/rules
> build' to test if it fixes a FTBFS, or 'fakeroot debian/rules binary' to
> go all the way to a 'deb' which I can try installing.
(And very usefully, just retry the packaging step without doing the
whole build again (can save a lot of time)).
> But if I don't want to install all the build dependencies on the machine
> I am using, how can I pass these commands to pbuilder? Or can I override
> gbp buildpackage (with pbuilder as an option) in some way so that it
> ignores the fact that there are altered files?
Just do the builds in a chroot. One of the coolest things about schroot
is that by default your home dir is mounted inside the chroot so you get
the exact same veiw inside and outside.
So you issue the dpkg-buldpackage, or fakeroot debian/rules binary or
whatever build commands inside the chroot. Thereby testing the build in
a stable (fairly) clean environment, and not filling your main machine
with build-deps.
Meanwhile you do do other stuff on the codebase from outside the chroot using all
your favourite tools too. Just avoid operations that are suite-specific.
> Hoping someone can solve a regular frustration of mine.
The above is how I do it.
> Regards,
>
> Ross
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] 53126122.1060903@the-gammons.net">https://lists.debian.org/[🔎] 53126122.1060903@the-gammons.net
>
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
Reply to: