[pkg-go] golang-github-minio-cli REMOVED from testing

FYI: The status of the golang-github-minio-cli source package in Debian's testing distribution has changed. Previous version: 1.3.0+git20170313.0.8683fa7-1 Current version: (not in testing) Hint: Bug #869190: golang-github-minio-c

[pkg-go] golang-github-masterzen-winrm 0.0~git20170601.0.1ca0ba6-2 MIGRATED to testing

FYI: The status of the golang-github-masterzen-winrm source package in Debian's testing distribution has changed. Previous version: 0.0~git20170601.0.1ca0ba6-1 Current version: 0.0~git20170601.0.1ca0ba6-2 -- This email is automatically generated once a day. As the installation of new packa

[pkg-go] golang-github-neowaylabs-wabbit 0.0~git20170406.0.cfb5237-2 MIGRATED to testing

FYI: The status of the golang-github-neowaylabs-wabbit source package in Debian's testing distribution has changed. Previous version: 0.0~git20170406.0.cfb5237-1 Current version: 0.0~git20170406.0.cfb5237-2 -- This email is automatically generated once a day. As the installation of new pac

Re: [pkg-go] Minutes for the DebConf17 BoF

On 20/08/17 19:21, Michael Stapelberg wrote: >> Gccgo has many quirks. One is that it does not use the vendor directory >> (I need to check if this is true with the latest version), so you might >> need to copy vendor into the builddirectory. > > …hopefully only temporarily, though, right? Ideall

Re: [pkg-go] Minutes for the DebConf17 BoF

On Sun, Aug 20, 2017 at 7:18 PM, Martín Ferrari wrote: > On 20/08/17 17:35, Martín Ferrari wrote: >> So, my turn to describe workflows. > > Some things I forgot in my previous email: > > * I am not married to the idea of dch + debcommit, specially when I have > merge conflicts. I understand the me

Re: [pkg-go] Minutes for the DebConf17 BoF

On Sun, Aug 20, 2017 at 7:05 PM, Martín Ferrari wrote: > On 20/08/17 18:46, Michael Stapelberg wrote: > >> Side note, not meant to persuade anyone one way or the other: I just >> realized why I never saw any appeal in that argument: I find git >> packaging (or git in general?) too brittle and conf

Re: [pkg-go] Minutes for the DebConf17 BoF

On 20/08/17 17:35, Martín Ferrari wrote: > So, my turn to describe workflows. Some things I forgot in my previous email: * I am not married to the idea of dch + debcommit, specially when I have merge conflicts. I understand the merits of git commit + gbp dch. * The export=WC option in gbp.conf is

Re: [pkg-go] Minutes for the DebConf17 BoF

On 20/08/17 18:46, Michael Stapelberg wrote: > Side note, not meant to persuade anyone one way or the other: I just > realized why I never saw any appeal in that argument: I find git > packaging (or git in general?) too brittle and confusing to keep what > I consider are multiple projects in the s

Re: [pkg-go] Minutes for the DebConf17 BoF

While we’re on the topic: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859867 discusses making sbuild easier to install/use :) On Sun, Aug 20, 2017 at 6:56 PM, Martín Ferrari wrote: > On 20/08/17 18:36, Michael Stapelberg wrote: >> I use gbp with sbuild, and I do see different behavior with/

Re: [pkg-go] Minutes for the DebConf17 BoF

On 20/08/17 18:36, Michael Stapelberg wrote: > I use gbp with sbuild, and I do see different behavior with/without > exporting. Take for example the freeradius repository, where the build > fails without git-export-dir: https://paste.debian.net/982241/ I guess the difference is with not having an

Re: [pkg-go] Minutes for the DebConf17 BoF

On Sun, Aug 20, 2017 at 5:35 PM, Martín Ferrari wrote: > So, my turn to describe workflows. > > I use gbp, pristine-tar, cowbuilder (but planning to move to sbuild), > dch, debcommit as my main tools. I have not really used dh-make-golang much. > > My global gbp configuration is as follows: > > [D

Re: [pkg-go] Minutes for the DebConf17 BoF

On Sun, Aug 20, 2017 at 2:30 PM, Martín Ferrari wrote: > Hi Mickael, > > I haven't yet got the time to write down properly my workflow, but I > will still reply to some points. :) > > On 15/08/17 23:02, Michael Stapelberg wrote: > >> 1. I store packaging in e.g. ~/d/pkg/gocryptfs and build using `

Re: [pkg-go] Minutes for the DebConf17 BoF

So, my turn to describe workflows. I use gbp, pristine-tar, cowbuilder (but planning to move to sbuild), dch, debcommit as my main tools. I have not really used dh-make-golang much. My global gbp configuration is as follows: [DEFAULT] pristine-tar = True sign-tags = True [buildpackage] export =

Re: [pkg-go] Minutes for the DebConf17 BoF

Hey, On 16/08/17 04:54, Michael Hudson-Doyle wrote: > I think I /slightly/ prefer the upstream branch to be upstream's git > history not a series of imports of tarballs. But I'm not set on it, and > gbp doesn't really get on with this approach if you're just packaging a > random commit rather tha

Re: [pkg-go] Minutes for the DebConf17 BoF

Hi Mickael, I haven't yet got the time to write down properly my workflow, but I will still reply to some points. :) On 15/08/17 23:02, Michael Stapelberg wrote: > 1. I store packaging in e.g. ~/d/pkg/gocryptfs and build using `gbp > buildpackage --git-export-dir=~/d/out/gocryptfs`. By using > -