On Mon, Nov 11, 2019 at 08:58:42AM +0100, Thomas Goirand wrote:
> >> Please, *never* do that. It's generally a very bad idea to write
> >> anything to debian/gbp.conf. It's as if you were adding your text editor
> >> preferences in the package. Instead, please prefer writing in ~/.gbp.conf.
> >
> > I keep most of my git-buildpackage settings which are specific to my
> > developer environment in ~/.gbp.conf. However, there are some gbp
> > settings which are specific to the repository set up, and those I
> > think, IMHO, *are* appropriate for debian/gbp.conf. For example:
> >
> > [DEFAULT]
> > pristine-tar = True
> > upstream-tag='v%(version)s'
> > debian-branch=debian/master
>
> The first 2, yes. The last one, it's my opinion that it's useless, and
> that you only need it because "ignore-branch = True" isn't the default
> in git-buildpackage. It's ok as long as you always keep the same
> packagig branch, but if, like in my team, we need a new branch name
> every 6 months, and for 400+ repositories, then keeping the branch name
> declared in debian/gbp.conf becomes super annoying (as it forces one to
> change the "debian-branch" each time).
Yes, and that's why I use debian/master instead of debian/buster or
debian/bullseye. :-)
When I do create debian/buster (once it became the stable branch), the
first thing I did after I branched off debian/buster from
debian/master was to edit debian/gbp.conf was to have:
debian-branch=debian/buster
I only do this when I need to do the first stable backport of a
serious/security bug, such that I have to create the debian/buster
branch in the first place. So it hasn't been all that annoying for
me.
Cheers,
- Ted
