On Mon, Dec 27, 2010 at 19:36, Guido Günther <[email protected]> wrote: > On Sun, Dec 26, 2010 at 04:53:18PM +0100, Guido Günther wrote: >> On Fri, Dec 24, 2010 at 02:16:03PM -0300, Felipe Sateler wrote: >> > Package: git-buildpackage >> > Version: 0.5.11 >> > Severity: normal >> > >> > When using gbp-clone, if the repository uses debian/gbp.conf and >> > Pristine-tar is set to true in said file, the pristine-tar branch is not >> > created. gbp-clone should parse any configuration files found in the >> > master branch of the target repository. >> That makes a lot of sense - we should first clone then read gbp.conf as >> usual (while preserving overrides from the command line) and create the >> necessary branches. Patches would be welcome. > You point remails valid but I just noticed that gbp-pull --all was > completely underdocumented: > > > http://git.debian.org/?p=users/agx/git-buildpackage.git;a=commitdiff;h=2a5df0a2f45100dcf7e7caa55fe7dbf51e5b26bf;hp=0e98d3a3fd3ee9814cf1a3f2441ee4647abb57ea > > also you can set pristine-tar = True in gbp.conf, see the bottom of: > > > http://git.debian.org/?p=users/agx/git-buildpackage.git;a=blob;f=gbp.conf;h=c7ecbb612e18227e6bb446e7cb1a8212d73f09d6;hb=refs/heads/experimental
I know that. But then it will fail if the cloned repo does not have pristine-tar. Best would be if gbp could detect automatically if it has to checkout a pristine-tar branch. > > Cheers, > -- Guido > -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
