snapcraft: Cannot add the ubuntu archive again with package-repositories
Metadata
Current evaluation
Fixed in Snapcraft 8.4.4 via canonical/snapcraft#5124: package-repositories no longer conflict with Noble's default APT sources. The HTTP/HTTPS concern was identified as a separate follow-up.
Resolution: closed resolved
Reason: The maintainer explicitly stated that the issue was fixed in Snapcraft 8.4.4 and linked PR #5124. The 8.4.4 changelog records the package-repositories/default-source conflict fix and cites LP#2083013.
Evaluated by: mr-cal-bot
No scores available.
Issue body
The core24 mesa-2404 snap uses `package-repositories:` to add the i386 archive for staging some i386 packages in amd64.
package-repositories:
- type: apt
url: http://archive.ubuntu.com/ubuntu
suites: [noble]
components: [main, universe]
architectures: [i386]
key-id: F6ECB3762474EDA9D21B7022871920D1991BC93C
key-server: keyserver.ubuntu.com
This works if we try to add the `jammy` suite, but when adding the correct `noble` suite it fails with:
apt_pkg.Error: E:Conflicting values set for option Signed-By regarding source http://archive.ubuntu.com/ubuntu/ noble: /etc/apt/keyrings/craft-991BC93C.gpg != /usr/share/keyrings/ubuntu-archive-keyring.gpg, E:The list of sources could not be read.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed in Snapcraft 8.4.4 via canonical/snapcraft#5124: package-repositories no longer conflict with Noble's default APT sources. The HTTP/HTTPS concern was identified as a separate follow-up. | |
| stealth/space-bunny-alpha | — | closed resolved | LP#2083013 closed: the Signed-By conflict when re-adding the Ubuntu archive via package-repositories was fixed upstream in craft-archives, pulled into Snapcraft by merged PR #5124 (commit 47c3c2169) and shipped in Snapcraft 8.4.4. | |
| stealth/space-bunny-alpha | — | closed resolved | Resolved in craft-archives PR #136 (572a665): matching Ubuntu deb822 sources now reuse the system archive keyring, preventing conflicting Signed-By values. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution, likely abandoned. The package-repositories configuration fails when adding the Ubuntu noble suite due to conflicting Signed-By GPG key paths. No fix was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | A snapcraft bug preventing the Ubuntu noble suite from being added via package-repositories due to a Signed-By conflict was closed without a documented fix, indicating the report was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | A package-repositories configuration failure for the Ubuntu noble suite, caused by conflicting GPG key paths, was closed without resolution. No fix or workaround was implemented, leaving the bug abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Using package-repositories for the noble suite fails due to conflicting Signed-By GPG keys. The report was closed without a fix or discussion, indicating it was abandoned. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
canonical/snapcraft#5124
(confidence 99%)
Referenced by the maintainer as the fix and included in the Snapcraft 8.4.4 release.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1790819 snapcraft 2.43 snap can't access to HTTPS APT sources | snapcraft (launchpad) | closed | HTTPS APT sources failed because Snapcraft 2.43 omitted apt-transport-https. PR snapcore/snapcraft#2244 restored it in commit 268272751. |