-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
[BUG] Failing to build on fedora 35 AARCH64 #502
Comments
Can you try it again? |
Same here on Fedora 34 x86_64. Exporting Also, at the end of the build, I get the following log. A working
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When building on FEDORA 35 AARCH64 I get
get "launchpad.net/gocheck": found meta tag vcs.metaImport{Prefix:"launchpad.net/gocheck", VCS:"bzr", RepoRoot:"https://launchpad.net/~niemeyer/gocheck/trunk"} at //launchpad.net/gocheck?go-get=1 go: launchpad.net/gocheck@v0.0.0-20140225173054-000000000087: unrecognized import path "launchpad.net/gocheck": GOVCS disallows using bzr for public launchpad.net/gocheck; see 'go help vcs' make: *** [Makefile:40: build-axolotl] Error 1
[Description of the issue]
See above
Steps to Reproduce
Expected behavior: [What you expect to happen]
To build fine
Actual behavior: [What actually happens]
get "launchpad.net/gocheck": found meta tag vcs.metaImport{Prefix:"launchpad.net/gocheck", VCS:"bzr", RepoRoot:"https://launchpad.net/~niemeyer/gocheck/trunk"} at //launchpad.net/gocheck?go-get=1 go: launchpad.net/gocheck@v0.0.0-20140225173054-000000000087: unrecognized import path "launchpad.net/gocheck": GOVCS disallows using bzr for public launchpad.net/gocheck; see 'go help vcs' make: *** [Makefile:40: build-axolotl] Error 1
Versions
Please provide the Version as written in
Settings->About Axolotl
Device
What device or OS are you using? Fedora 35 AARCH64 PinePhone
Link to Debug Log
Please provide a link to debug from ~/.cache/upstart/application-click-textsecure.nanuc_textsecure*.log
Be careful it contains sensible data
The text was updated successfully, but these errors were encountered: