Ubuntu
golang-go.crypto package

crypto poly1305 on armhf fails to build

Bug #1636587 reported by Mathieu Trudel-Lapierre
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
golang-go.crypto (Ubuntu)
Invalid
Undecided
Unassigned
Xenial
Invalid
Undecided
Unassigned
Yakkety
Invalid
Undecided
Unassigned

Bug Description

[Impact]
golang-go.crypto-0.0~git20161012.0.5f31782-1ubuntu0.16.10.1 is a backport to Yakkety of a new snapshot for golang-go.crypto, as required by Juju.

crypto doesn't successfully build on armhf due to an unforseen issue with build rules in the poly1305 package; which explicitly wants not go1.7. We're not building with go1.7, but this throws it off anyway. Fix it so armhf works again.

[Test case]
golang-go.crypto should build succesfully. Reverse-depends should build successfully, as per bug 1634609.

[Regression Potential]
Could cause rebuilds of golang-go.crypto to fail if using go1.7.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

This doesn't apply to Zesty; which uses a newer go compiler by default.

Changed in golang-go.crypto (Ubuntu):
status: New → Invalid
Changed in golang-go.crypto (Ubuntu Xenial):
status: New → In Progress
Changed in golang-go.crypto (Ubuntu Yakkety):
status: New → In Progress
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Hello Mathieu, or anyone else affected,

Accepted golang-go.crypto into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/golang-go.crypto/1:0.0~git20161012.0.5f31782-1ubuntu0.16.10.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in golang-go.crypto (Ubuntu Yakkety):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

This does not fail validation but is unnecessary, we built juju-core without a new crypto.

Changed in golang-go.crypto (Ubuntu Yakkety):
status: Fix Committed → Invalid
Changed in golang-go.crypto (Ubuntu Xenial):
status: In Progress → Invalid
tags: added: verification-failed
removed: verification-needed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.