Re: Re: Plans for backporting golang 1.13 to buster

2020-01-17 Thread Stephen Gelman
That seems extremely reasonable to me. Stephen On Fri, Jan 17, 2020 at 1:01 PM Pirate Praveen wrote: > > I think it makes sense to add Breaks: dh-golang << 1.43~ to golang-1.13 to > force upgrade of dh-golang especially in backports. Else every package that > uses golang-any >= 1.13~ will also

Re: Re: Plans for backporting golang 1.13 to buster

2020-01-17 Thread Pirate Praveen
I think it makes sense to add Breaks: dh-golang << 1.43~ to golang-1.13 to force upgrade of dh-golang especially in backports. Else every package that uses golang-any >= 1.13~ will also need to add dh-golang >= 1.43~. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: gopasspw packaging (#901133)

2020-01-17 Thread Shengjing Zhu
It might be interesting to try, since they are two Go modules, and in one repo. -- Shengjing Zhu

Re: gopasspw packaging (#901133)

2020-01-17 Thread Balasankar "Balu" C
Hi, On 17/1/20 7:23 PM, Balasankar "Balu" C wrote: > Yes. I am trying to figure out if dh's Golang build system can do it or not. I found that there are packages like syncthing, influxdb, toxyproxy, etc. which do multiple binary packages. Let me check them out. Regards Balu signature.asc Des

Re: gopasspw packaging (#901133)

2020-01-17 Thread Balasankar "Balu" C
Hi, On 17/1/20 5:38 PM, Pirate Praveen wrote: > > On വെ, Jan 17, 2020 at 17:31, Balasankar Balu C > wrote: >> I think the plan is to have a `vault` source package, that currently >> only builds/installs `golang-github-hashicorp-vault-api` >> and `golang-github-hashicorp-vault-sdk` binary packages

Re: gopasspw packaging (#901133)

2020-01-17 Thread Pirate Praveen
On വെ, Jan 17, 2020 at 17:31, Balasankar Balu C wrote: Hi, On 17/1/20 3:14 PM, Clément Hermann wrote: In any case, it would be interesting to answer this question anyway: how do we make sure we don't have duplicate code in packages when we do this ? I think the plan is to have a `vau

Re: gopasspw packaging (#901133)

2020-01-17 Thread Balasankar "Balu" C
Hi, On 17/1/20 3:14 PM, Clément Hermann wrote: > In any case, it would be interesting to answer this question anyway: > how do we make sure we don't have duplicate code in packages when we > do this ? I think the plan is to have a `vault` source package, that currently only builds/installs `gola

Re: gopasspw packaging (#901133)

2020-01-17 Thread Clément Hermann
Hi, On 17/01/2020 10:13, Balasankar "Balu" C wrote: > Hi, > > On 17/1/20 2:38 PM, Pirate Praveen wrote: >> We discussed about packaging only part of bigger repos recently and >> agreed on packaging parts, just package vault-api and vault-sdk. > > That also works (Though I am not sure how that w

Re: gopasspw packaging (#901133)

2020-01-17 Thread Pirate Praveen
On വെ, Jan 17, 2020 at 14:43, Balasankar Balu C wrote: Hi, On 17/1/20 2:38 PM, Pirate Praveen wrote: We discussed about packaging only part of bigger repos recently and agreed on packaging parts, just package vault-api and vault-sdk. That also works (Though I am not sure how that will

Re: gopasspw packaging (#901133)

2020-01-17 Thread Balasankar "Balu" C
Hi, On 17/1/20 2:38 PM, Pirate Praveen wrote: > We discussed about packaging only part of bigger repos recently and > agreed on packaging parts, just package vault-api and vault-sdk. That also works (Though I am not sure how that will turn out if/when we actually want to package Vault). Do we ha

Re: gopasspw packaging (#901133)

2020-01-17 Thread Pirate Praveen
On 2020, ജനുവരി 17 1:07:54 PM IST, "Balasankar "Balu" C" wrote: >Hi, > >On 30/3/19 8:01 PM, Balasankar C wrote: > >> Hi all, I am interested in packaging gopasspw[0], and have marked the >corresponding bug(#901133) to an ITP. >> I have written a few Go programs as hobby projects, but am new to