-
Notifications
You must be signed in to change notification settings - Fork 441
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
dpkg --add-architecture fails when using package-repositories #4289
Labels
bug
Actual bad behavior that don't fall into maintenance or documentation
Comments
I can confirm the same on MacOS snapcraft. (snapcraft 7.3.1). Inside the building instance it reports snapcraft 7.5.0.
|
This looks similar to #4298 |
|
tigarmo
added a commit
that referenced
this issue
Aug 4, 2023
Version 1.1.3 fixes the issue with package-repositories that declare architectures. In addition to addressing the wrong parameter order, the new version also improves the handling of architectures. The summary of the change is: if the host system is amd64 and the arch of the package repository is i386, _or_ if the host is arm64 and the repo armhf, then `dpkg --add-architecture <repo_arch>` will be called. Otherwise, the command is not called. This lets us preserve the behavior of enabling i386 in the official repositories when a repo using i386 is added, with the improvement of _not breaking_ apt update when an "incompatible" architecture combination is declared. The new spread tests reflect this. Both run in amd64 and add the deadsnakes ppa to fetch Python in a foreign arch: - For i386, only the deadsnakes ppa is necessary, as the architecture will be added "globally" and Python's dependencies are found in the default archives; - For armhf, the ports.ubuntu.com repo is necessary in addition to the deadsnakes one. This lets the dependencies be found in the ports repo, _and_ doesn't break the build (this combination is broken in Snapcraft 7.2, 7.3 and 7.4). Fixes #4289 and #4298
Can you please try Snapcraft from candidate? It shall be released as soon as build issues with armhf, ppc64el and riscv64 are solved |
@sergiusens Ok, although it will take some time as i have removed that part for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
Recently we were trying to snap up lutris after a break but now snapcraft build fails both with remote and the online(using launchpad as a back-end) , giving out this particular error.
This was not the case earlier with us having success previously in building the lutris snap.
Full build-log --> https://launchpadlibrarian.net/678501471/buildlog_snap_ubuntu_jammy_amd64_lutris_BUILDING.txt.gz
To Reproduce
Environment
In remote builds ;
--> Lubuntu
Rest was on launchpad side so cant be sure.
snapcraft.yaml
In non-remote builds we do use lint part only disabled it for remote-builds.
Relevant log output
--> https://launchpadlibrarian.net/678501471/buildlog_snap_ubuntu_jammy_amd64_lutris_BUILDING.txt.gz
Additional context
This error recently occurs no such errors were faced earlier i.e June and before.
The text was updated successfully, but these errors were encountered: