Warnings? Errors? When updating the whole stack today

[Roger Peppe]

This is evidently because the go.crypto repository is now using
go 1.1, which has cleverer logic around return statements.

I will try to push a patch to go.crypto that fixes the issue for
us.

However, until we start using 1.1 ourselves, we are
going to come across this kind of thing with increasing regularity
in external repositories. We do really want to benefit from
security updates to these repositories, so freezing at an old
version isn't really a great solution for us, even if it was easy to do.


On Mon, Jun 10, 2013 at 1:24 PM, Andreas Hasenack <andreas at canonical.com> wrote:
> $ go get -v launchpad.net/juju-core/...
> code.google.com/p/go.crypto/openpgp/packet
> # code.google.com/p/go.crypto/openpgp/packet
> ../go/src/code.google.com/p/go.crypto/openpgp/packet/packet.go:260: function
> ends without a return statement
> ../go/src/code.google.com/p/go.crypto/openpgp/packet/public_key.go:283:
> function ends without a return statement
>
>
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>