On Wed, Dec 29, 2010 at 07:51, Guido Günther <a...@sigxcpu.org> wrote: > On Tue, Dec 28, 2010 at 09:22:15PM -0300, Felipe Sateler wrote: >> On Sun, Dec 26, 2010 at 10:24, Guido Günther <a...@sigxcpu.org> wrote: >> > Hi Felipe, >> > On Tue, Dec 21, 2010 at 09:23:40PM -0300, Felipe Sateler wrote: >> >> Package: git-buildpackage >> >> Version: 0.5.11 >> >> Severity: normal >> >> >> >> Currently, git-buildpackage warns if it found no pristine-tar branch. It >> >> should fail noisily (as it used to). >> > >> > It still fails here with 0.5.12, the code didn't change so 0.5.11 should >> > fail >> > as well: >> > >> > $ /var/scratch/debian/git-buildpackage/git-buildpackage/git-buildpackage >> > --git-ignore-new >> > gbp:warn: Pristine-tar branch "pristine-tar" not found >> > /usr/bin/pristine-tar: no pristine-tar branch found, use "pristine-tar >> > commit" first >> > /usr/bin/pristine-tar returned 1 >> > Couldn't run '/usr/bin/pristine-tar' >> > >> > Can you post the output and/or recheck with 0.5.12? >> >> With 0.5.11: >> >> fel...@pcfelipe:ladspa-sdk% cat debian/gbp.conf >> >> [DEFAULT] >> pristine-tar = True >> sign-tags = True >> fel...@pcfelipe:ladspa-sdk% git branch -a >> * master >> upstream >> remotes/origin/HEAD -> origin/master >> remotes/origin/master >> remotes/origin/pristine-tar >> remotes/origin/upstream >> fel...@pcfelipe:ladspa-sdk% git-buildpackage >> dh --with quilt clean >> dh_testdir >> debian/rules override_dh_auto_clean >> make[1]: Entering directory `/home/felipe/src/deb/ladspa-sdk/ladspa-sdk' >> dh_auto_clean >> /usr/bin/make -C src clean >> make[2]: Entering directory `/home/felipe/src/deb/ladspa-sdk/ladspa-sdk/src' >> rm -f `find . -name "*.o"` ../bin/* ../plugins/* >> rm -f `find .. -name "*~"` >> rm -f *.bak core score.srt >> rm -f *.bb *.bbg *.da *-ann gmon.out bb.out >> rm -f `find .. -name "*.class"` >> make[2]: Leaving directory `/home/felipe/src/deb/ladspa-sdk/ladspa-sdk/src' >> make[1]: Leaving directory `/home/felipe/src/deb/ladspa-sdk/ladspa-sdk' >> dh_quilt_unpatch >> No patch removed >> dh_clean >> gbp:warn: Pristine-tar branch "pristine-tar" not found >> /usr/bin/pristine-tar: successfully generated > > Now I see. Pristine-tar aborts if it can't find the pristine-tar data > but it can since it looks at remotes/origin/pristine-tar in you case. > That behaviour didn't change. Why should we abort when the tarball gets > generated fine?
Hmm, I was not sure if it was generated fine. I've had issues of tarballs uploaded not matching the pristine-tar data, and assumed this was the culprit. If the tarball is being generated fine (which it seems so), then this could be closed. -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
