forcemerge 669267 702794 thanks Hi Felipe, On Tue, Mar 12, 2013 at 07:19:04PM -0300, Felipe Sateler wrote: > On Mon, Mar 11, 2013 at 1:58 PM, Guido Günther <a...@sigxcpu.org> wrote: > > On Mon, Mar 11, 2013 at 10:36:09AM -0400, Felipe Sateler wrote: > >> Package: git-buildpackage > >> Version: 0.6.0~git20121124 > >> Severity: normal > >> > >> When building a full (source+binary) package, dpkg-source is invoked by > >> dpkg-buildpackage. dpkg-source needs the orig tarball in order to create > >> the source package. git-buildpackage should extract the tarball from the > >> pristine-tar branch (if it exists) before invoking dpkg-source (if the > >> tarball does not already exist), otherwise the build fails because the > >> orig tarball was not found. > > > > Please attach the command you're using. gbp should behave exactly as you > > describe. > > Further experimentation reveals that the problem is not the invocation > of gbp, but my package. However, gbp could be smarter about this. > > The package I was trying to build had a wrong version number. It was a > 3.0 (quilt) package, but the version didn't have a debian revision > number. > > I'm thinking gbp assumed it was a native package, so it didn't extract > the pristine-tar data. Thus the behavior I was seeing. > > I'm not sure what gbp should do in this case. But I think if the > package format is 3.0 it can avoid guessing from the version if it > should extract upstream data or not.
gbps idee about this for 3.0 is currently wrong. It fails to check debian/source. It's on the todo list to have this fixed. Sorry for the trouble. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
