Ian Jackson wrote:
> Joey Hess writes ("Re: Bug#720522: cannot NMU dgit using dgit"):
> > Ian Jackson wrote:
> > > Please go ahead, but into experimental. You will probably want to use
> > > 0.8 which I have just pushed.
> > >
> > > You should be able to make an "empty" NMU by just adding a
> > > debian/changelog entry.
> >
> > I did this successfully. However, my first build attempt failed
> > because git-buildpackage wanted to be on an experimental branch rather
> > than the sid branch dget clone set up.
>
> I guess this was using git-buildpackage directly ? dgit build would
> canonicalise "experimental" to "sid" and pass the result to
> git-buildpackage.No, that was a straight dgit build. joey@gnu:~/tmp/dgit[sid]>dgit build dh clean dh_testdir dh_auto_clean dh_clean gbp:error: You are not on branch 'dgit/experimental' but on 'dgit/sid' gbp:error: Use --git-ignore-branch to ignore or --git-debian-branch to set the branch name. git-buildpackage: failed command: git-buildpackage -us -uc --git-no-sign-tags '--git-builder=dpkg-buildpackage -i\\.git/ -I.git' '--git-debian-branch=dgit/experimental' dgit: subprocess failed with error exit status 1 > > My next build failed because I ran dpkg-buildpackage in my usual way, > > which includes -I, and this excluded .gitignore from the tarball. The > > source consistency check then failed. > > I guess this was dpkg-buildpackage directly. Yes, this is why I > provided dgit build. Indeed. Although really it was a wrapper script I reflexively reach for, since it normally always works.. (Everything in that wrapper is obsoleted in one way or another by dgit though.) > > Seems that some of this could be improved, but I don't know how, other > > than perhaps passing --git-ignore-branch to git-buildpackage by default. > > Perhaps that would be best. It would also avoid the need to try to > canonicalise the suite name. Seems like a win. > > (Probably doesn't help that I have never bothered to learn > > git-buildpackage, since I considered it a fundamentally wrong approach > > to the problem, and insanely complicated for what it does. It is thus > > somewhat disconcerting to see it used in dgit..) > > It's optional. If you use "dgit sbuild" it doesn't get used at all. > "dgit build" uses git-buildpackage in a pretty simple mode. Maybe it > would be best for it to just use dpkg-buildpackage directly now that > "dgit sbuild" has much of the same infrastructure. My netbook doesn't have the grunt to run sbuild, but I think it's a fine alternative for many. I would be personally happier if dgit build ran as close to the dpkg-buildpackage bare metal as possible, since it would make the whole easier to understand. -- see shy jo
signature.asc
Description: Digital signature
