[pkg-go] DEP-14 and backports for prometheus and docker.io

[Potter, Tim (HPE Linux Support)]

On 5 May 2016, at 11:34 AM, Potter, Tim (HPE Linux Support) <timothy.potter at hpe.com> wrote:
> 
> On 4 May 2016, at 8:17 PM, Martín Ferrari <tincho at tincho.org> wrote:

>> I also get some tooling benefits: gbp will know automatically which
>> pbuilder to use, if you say dist=dep14
> 
> Oh, I didn't know about that either.  Thanks for the tip!

Hi Martin.  Here's my process for creating a backport from an existing pkg-go repository.  I
might be able to get some help to do this for the ~160 packages if you are willing to do
the uploads.

$ git clone $REPO
$ git checkout -b debian/sid # initial branch is master
$ git checkout -b debian/jessie-backports
$ vi debian/gbp.conf # create new or update existing file
[DEFAULT]
pristine-tar = True
debian-branch = debian/sid
upstream-branch = master
$ dch -i
[Create new changelog entry with jessie-backports suite and ~bpo8+1 version suffix]
$ git commit debian/changelog -m "Upload to backports"
$ git tag debian/$VERSION~bpo+1
$ git push origin --tags master debian/sid debian/jessie-backports

I'm not sure whether you want to delete the master branch and set debian-branch to
debian/sid.  I think this is what you have done in some of the other pkg-go repos you
are maintainer for.  Happy to go with whatever you think is right.

What do you think?


Tim.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.alioth.debian.org/pipermail/pkg-go-maintainers/attachments/20160506/e4a3e26c/attachment-0001.sig>