New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilation fails on all architectures on Ubuntu Xenial #279
Comments
looks like recently backported go 1.13 has a bug. |
/assign @adjackura |
It looks like this is an issue with 1.13 on Xenial correct? Is the 1.13 the latest version available for Xenial building? |
It is 1.13.8-1ubuntu1~16.04.2 , which is a backport of the latest 1.13.x version in Ubuntu:
|
There is a fix in the xenial unapproved queue now. |
@mwhudson thanks! |
@mwhudson thanks, confirmed that the fix works. what is the approximate timeline for its release? |
@rojer the fix has just been accepted into proposed, which is actually enough (once published) to fix your needs I think as subsequent package builds will use the toolchain from proposed. Would you as reporter be able to verify the fix as described in the bug? If not, I can. |
retried one of the failing builds but it still used the old package (...16.04.2) and failed again. |
is this in a ppa? does it have proposed enabled? |
yes it is and no it wasn't. switched to proposed and the build succeeded. thanks for taking care of this! |
Great thanks. Can you share the build logs in the bug? Or here and I will paste them in? |
here's a successful build - https://launchpad.net/~mongoose-os/+archive/ubuntu/mos/+build/21000322 |
It might still be available from a build failure email, there's nowhere in the UI to retrieve it from unfortunately. |
links from failure notifications point to the same log, unfortunately |
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4159/+build/20820342
https://launchpadlibrarian.net/517348792/buildlog_ubuntu-xenial-amd64.google-osconfig-agent_20210112.00-0ubuntu1~16.04.0~rbalint2_BUILDING.txt.gz
The text was updated successfully, but these errors were encountered: