--- FAIL: TestParseInSydney (0.00 seconds)
format_test.go:201: ParseInLocation(Feb 01 2013 EST, Sydney) = 2013-02-01 00:00:00 +0000 EST, want 2013-02-01 00:00:00 +1100 AEDT
FAIL
FAIL time 2.515s
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Utopic Unicorn (development branch)
Release: 14.10
Codename: utopic
$ hg summary
parent: 20728:85518b1d6f8d go1.3.2 release
go1.3.2
branch: release-branch.go1.3
commit: (clean)
update: (current)
Nice, thank you Andrew. I just pulled the latest changes of the release-branch.go1.3 and ran all.bash. However, when I run `go version` I get 1.3.1go version go1.3.1 darwin/amd64. Am I doing it right?
got a test fail building from source.
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi gophers,We've just released Go version 1.3.2, a minor point release.
--- FAIL: TestParseInSydney (0.00 seconds)
format_test.go:201: ParseInLocation(Feb 01 2013 EST, Sydney) = 2013-02-01 00:00:00 +0000 EST, want 2013-02-01 00:00:00 +1100 AEDT
FAIL
FAIL time 2.370s
$ hg pull
$ hg update release
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
--- FAIL: TestFormatSecondsInTimeZone-8 (0.00 seconds)
format_test.go:515: Format = 1871-01-01T05:33:02-0034:08, want 1871-01-01T05:33:02-00:34:08
format_test.go:515: Format = 1871-01-01T05:33:02+0034:08, want 1871-01-01T05:33:02+00:34:08
format_test.go:515: Format = 1871-01-01T05:33:02+0034:08, want 1871-01-01T05:33:02+00:34:08
FAIL
FAIL time 2.398s
It's a colon problem
"0034:08" vs "00:34:08"
Hi gophers,We've just released Go version 1.3.2, a minor point release.
If it were internal code, we would do exactly that. Unfortunately for us, the affected coffee is in an open-source library, and of course we can't rely on other people patching their tool chain.
That being said, I understand your reluctance. We'll make do if we have to.
– John Tuley
My apologies for the typo. There is no coffee affected; the issue isn't THAT dire.
– John Tuley
They want to release code into an open source library that wouldn't work with any Go version >1.2.2.
They rely on their users having a reasonably current Go version (so >1.2.2).
Code cannot be published cause everyone who uses it would need to patch.
That's what I understood.