Re: Plans for backporting golang 1.13 to buster

2020-01-20 Thread Dr. Tobias Quathamer
Am 17.01.20 um 20:00 schrieb 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~. Thanks for your suggestion,

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: Plans for backporting golang 1.13 to buster

2020-01-06 Thread Pirate Praveen
On ഞാ, Jan 5, 2020 at 21:55, Dr. Tobias Quathamer wrote: I've just uploaded golang 1.13 to bpo. After it gets ACCEPTED, dh-golang needs a backport, too. Also golang-defaults should be updated for backports. Thanks Tobias for the upload and it is already accepted. Btw these could have bee

Re: Plans for backporting golang 1.13 to buster

2020-01-05 Thread Dr. Tobias Quathamer
Am 03.01.20 um 21:03 schrieb Pirate Praveen: > I think more and more packages will be expecting golang 1.13 from now > on. Is there any plan to backport golang 1.13 to buster? Or any > objections if I were to backport it? Hi, I've just uploaded golang 1.13 to bpo. After it gets ACCEPTED, dh-golan

Re: Plans for backporting golang 1.13 to buster

2020-01-04 Thread Stephen Gelman
On Jan 4, 2020, at 7:57 PM, Daniel Swarbrick wrote: > > I have noticed a lot of CNCF projects have made the switch to Go 1.13. I > think that for some of them, it's simply been more or less a housekeeping > thing, but for others, they are genuinely starting to use Go 1.13 features. > > As an

Re: Plans for backporting golang 1.13 to buster

2020-01-04 Thread Daniel Swarbrick
I have noticed a lot of CNCF projects have made the switch to Go 1.13. I think that for some of them, it's simply been more or less a housekeeping thing, but for others, they are genuinely starting to use Go 1.13 features. As an example, I updated a couple of Prometheus exporters yesterday. The bl