Re: [pkg-go] Bug#827697: Bug#827697: golang-github-shirou-gopsutil: Please update to latest release

2016-06-24 Thread Ian Campbell
On Fri, 2016-06-24 at 02:11 +0100, Martín Ferrari wrote: > On 23/06/16 22:11, Dmitry Smirnov wrote: > > On Friday, 24 June 2016 8:28:17 AM AEST Michael Hudson-Doyle wrote: > >> Isolating the packaging changes is hardly difficult: > >>

Re: [pkg-go] Bug#827697: Bug#827697: golang-github-shirou-gopsutil: Please update to latest release

2016-06-23 Thread Martín Ferrari
On 23/06/16 22:11, Dmitry Smirnov wrote: > On Friday, 24 June 2016 8:28:17 AM AEST Michael Hudson-Doyle wrote: >> Isolating the packaging changes is hardly difficult: >> https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-shirou-gopsut >> il.git/log/debian > > Cool that you can do it so

Re: [pkg-go] Bug#827697: Bug#827697: golang-github-shirou-gopsutil: Please update to latest release

2016-06-23 Thread Dmitry Smirnov
On Friday, 24 June 2016 8:28:17 AM AEST Michael Hudson-Doyle wrote: > Isolating the packaging changes is hardly difficult: > https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-shirou-gopsut > il.git/log/debian Cool that you can do it so easy in cgit. How about Gitg for a change? I

Re: [pkg-go] Bug#827697: Bug#827697: golang-github-shirou-gopsutil: Please update to latest release

2016-06-23 Thread Michael Hudson-Doyle
Isolating the packaging changes is hardly difficult: https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-shirou-gopsutil.git/log/debian On 24 June 2016 at 05:52, Dmitry Smirnov wrote: > On Tuesday, 21 June 2016 6:32:46 PM AEST Martín Ferrari wrote: >> On 20/06/16

Re: [pkg-go] Bug#827697: Bug#827697: golang-github-shirou-gopsutil: Please update to latest release

2016-06-23 Thread Dmitry Smirnov
On Tuesday, 21 June 2016 6:32:46 PM AEST Martín Ferrari wrote: > On 20/06/16 05:11, Dmitry Smirnov wrote: > > I do not mind having full upstream history in "upstream" > > branch but not in "master"... > I don't really have any issue with having all the > commits, as it is pretty clear to me which

Re: [pkg-go] Bug#827697: Bug#827697: golang-github-shirou-gopsutil: Please update to latest release

2016-06-21 Thread Martín Ferrari
Dmitry, On 20/06/16 05:11, Dmitry Smirnov wrote: > I think your procedure could be improved if "git merge upstream/2.1" > is modified with "--squash" to produce one neat merge commit to "master" > instead of flood of upstream commits that make it difficult to identify > packaging-related

Re: [pkg-go] Bug#827697: Bug#827697: golang-github-shirou-gopsutil: Please update to latest release

2016-06-19 Thread Potter, Tim (HPE Linux Support)
On 20 Jun 2016, at 2:11 PM, Dmitry Smirnov wrote: > > On Sunday, 19 June 2016 9:59:30 PM AEST Martín Ferrari wrote: >> On 19/06/16 20:47, Dmitry Smirnov wrote: >>> I would be happy to upload updated package but I've noticed that >>> "upstream" branch follows upstream history

Re: [pkg-go] Bug#827697: Bug#827697: golang-github-shirou-gopsutil: Please update to latest release

2016-06-19 Thread Dmitry Smirnov
On Sunday, 19 June 2016 9:59:30 PM AEST Martín Ferrari wrote: > On 19/06/16 20:47, Dmitry Smirnov wrote: > > I would be happy to upload updated package but I've noticed that > > "upstream" branch follows upstream history so "gbp import-orig" would > > break it and I'm not sure how to handle such

[pkg-go] Bug#827697: Bug#827697: golang-github-shirou-gopsutil: Please update to latest release

2016-06-19 Thread Martín Ferrari
On 19/06/16 20:47, Dmitry Smirnov wrote: > I would be happy to upload updated package but I've noticed that "upstream" > branch follows upstream history so "gbp import-orig" would break it and I'm > not sure how to handle such repository configuration... I have just done it. These are the