On Tuesday, 5 April 2016 3:40:13 AM AEST Martín Ferrari wrote:
> On 05/04/16 02:22, Michael Hudson-Doyle wrote:
> Again, this is my fault. The first golang packages I prepared had a +
> instead of a ~, because I was mistaken. Had to package so many
> dependencies, got some things wrong :(
Don't be
On 05/04/16 02:22, Michael Hudson-Doyle wrote:
> Oh, one thing you'll need to change: the current version is (for some
> reason) 0.0+git20150627.7ad95dd-1, which is greater than your version
> of 0.0~git20160301.0.a83829b-1 :-) I guess this means some mucking
> about in the upstream and pristine-ta
ratt seems happy to me: http://paste.ubuntu.com/15622797/. So the
version needs fixing but then it's ready for upload I think (not by me
though, I don't have upload rights).
On 5 April 2016 at 12:22, Michael Hudson-Doyle
wrote:
> Oh, one thing you'll need to change: the current version is (for so
Oh, one thing you'll need to change: the current version is (for some
reason) 0.0+git20150627.7ad95dd-1, which is greater than your version
of 0.0~git20160301.0.a83829b-1 :-) I guess this means some mucking
about in the upstream and pristine-tar branches too.
On 5 April 2016 at 12:05, Michael Huds
Hah, I was just doing exactly this. I was about to run ratt
(https://people.debian.org/~stapelberg//2015/10/12/ratt.html) on my
changes but I'll run it on yours instead and let you know how it goes
:-)
Cheers,
mwh
On 5 April 2016 at 10:27, Potter, Tim (HPE Linux Support)
wrote:
> Hi everyone. I
Hi everyone. It turns out that the golang-yaml.v2 package needs an update to
support the version of golang in stretch, version 1.6. I guess the latest
version of Go introduces backwards-incompatible changes to the language. )-:
Could someone give my latest push to alioth a review and upload p
