retitle 824801 buildpackage: option to force sloppy test builds summary 824801 It should be simple to perform a build of the current HEAD without having to worry about upstream branches, pristine-tar and the like
On Fri, May 20, 2016 at 08:37:54AM +0200, Guido Günther wrote: > On Thu, May 19, 2016 at 11:40:38PM +0200, Eduard Bloch wrote: > > Package: git-buildpackage > > Version: 0.7.4 > > Severity: wishlist > > > > Hi, > > > > I remember having reported a similar issue a couple of years ago and > > back then it was closed with a useless coment. This time I stumbled upon > > it again and still cannot find a SANE solution. With SANE, I mean > > user-friendly. I, as user, wish to have an option to make a test build. > > Without having an upstream tarball! > > (that is the key point. The debian branch is a fork of the upstream > > branch after all, it should just work). > > > > WRT dpkg-buildpackage itself, I can easily force it to act like on a > > native package and just build me my binary packages. But with gbp, this > > simple task becomes PITA: it wants me to have some upstream reference or > > else... (see below). > > > > Sorry, there really should be an easy and user-friendly way to let me > > just build it, no matter whether there is an upstream tag or not. I > > did RTFM and nothing ringed a bell there. If there is an easy way, > > please document it properly. > > > > > > > > dh_clean > > rm -rf debian/apt-cacher-ng.service debian/apt-cacher-ng.tmpfile > > dbgen/dbgenerator.* dbgen/dbupdate > > debconf-updatepo > > ... > > gbp:info: Orig tarball 'apt-cacher-ng_0.9.3.orig.tar.xz' not found at > > '../tarballs/' > > gbp:error: Pristine-tar couldn't checkout > > "apt-cacher-ng_0.9.3.orig.tar.xz": fatal: Path > > 'apt-cacher-ng_0.9.3.orig.tar.xz.delta' does not exist in > > 'refs/heads/pristine-tar' > > pristine-tar: git show > > refs/heads/pristine-tar:apt-cacher-ng_0.9.3.orig.tar.xz.delta failed > > It's still the same as back then: don't sue pristine tar if you don't > want it and tell gbp that you're fine with just picking the head of your > upstrema branch. That said an option that creates a tarball not from the upstream branch but just takes the current tree, drops debian/ and creates an upstream tarball from it would probably also helpful in the above situation (at least for 3.0 (quilt). This would also allow to test patches without having to move to a pq first. We would just have to make sure we create a unique version number just like -S in gbp dch. Cheers, -- Guido
