snapcraft APT sources checking too strict
Metadata
Current evaluation
snapcraft fails builds when APT exits nonzero for non-critical warnings (e.g., outdated hash functions, unsupported PPAs). Unlabelled, zero comments, no maintainer interaction; references obsolete 2015-era sources.
Suggested action: needs triage
Reason: The issue is unlabelled with zero comments and no maintainer acknowledgement, so it has not been triaged. It is a genuine bug report (snapcraft should not fail on non-fatal APT warnings), not a support request, but it is very old (3757 days) and references obsolete sources (yakkety, ancient hash functions), so a maintainer should verify whether current apt-cache population still fails on warnings before deciding to fix or close.
Impact:
30
Quick Win:
19.5
Staleness:
95
Complexity:
35
Confidence:
55
Support Request:
15
Issue body
APT exits with nonzero value for some insignificant reasons, like The Google archive for Chrome browser using an ancient hash function, or a post-upgrade PPA not supporting yakkety yet.
snapcraft should not fail for silly warnings from APT.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
19.5
Staleness:
95
Complexity:
35
Confidence:
55
Support Request:
15
|
needs triage | snapcraft fails builds when APT exits nonzero for non-critical warnings (e.g., outdated hash functions, unsupported PPAs). Unlabelled, zero comments, no maintainer interaction; references obsolete 2015-era sources. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | snapcraft fails on non-critical APT warnings like outdated hash functions or unsupported PPAs. The report is unlabelled, has zero maintainer interaction, and references obsolete software from 2015. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
90
Support Request:
15
|
close stale | snapcraft fails builds due to strict APT exit codes from minor warnings like deprecated hash functions or outdated PPAs. Untriaged, inactive for ~10 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | snapcraft fails builds due to strict APT source checking on non-critical warnings. Untriaged and inactive for over 10 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
100
Complexity:
20
Confidence:
95
Support Request:
10
|
close stale | snapcraft halts builds on non-critical APT warnings like deprecated hashes or outdated PPAs. It should ignore these minor exit codes instead. Status: open, no comments or labels, awaiting triage. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1638840 snapcraft copies /etc/apt/sources but ignores /etc/apt/preferences | snapcraft (launchpad) | open | Snapcraft copies /etc/apt/sources but ignores /etc/apt/preferences, causing wrong package selection in complex setups. 9.8 years old, zero comments, no labels, no maintainer interaction. Current codebase uses craft-archives with AptPreferencesManager, a completely different architecture. | |
| #1992213 Snapcraft crashes when the APT unprivileged user owns the host's source list file instead of root | snapcraft (launchpad) | open | Snapcraft crashes when APT source list files have restrictive permissions (owned by _apt user with 0600). Issue is 4 years old with no maintainer response. | |
| #1841618 snapcraft should run apt-get update | snapcraft (launchpad) | open | Feature request (2019) for snapcraft to refresh stale apt-get caches in process containers to avoid build failures. Open ~7 years with zero comments, no labels, no maintainer response; no general cache-refresh logic found in the build path. | |
| #1800119 snapcraft cleanbuild | snapcraft (launchpad) | closed | Closed without resolution. The report details a PermissionError during snapcraft cleanbuild caused by restricted access to the .aptitude directory. With zero comments and no fix applied, the issue was abandoned or marked stale. | |
| #1790819 snapcraft 2.43 snap can't access to HTTPS APT sources | snapcraft (launchpad) | closed | Abandoned. The missing HTTPS APT method driver in snapcraft 2.43 was not addressed. | |
| #1548225 Snapcraft/snappy should detect incompatible version mismatches | snapcraft (launchpad) | closed | Abandoned. The report detailed Snapcraft failing to detect version mismatches, causing large snaps to install incorrectly. With zero comments and over a decade of dormancy, it received no resolution and was closed. | |
| #2099923 Snapcraft builds are failing: install of snap "snapcraft" failed | snapcraft (launchpad) | open | Snapcraft builds failing due to outdated snapd (2.61) on build infrastructure unable to install core20 base. Issue is 556 days old with no maintainer response. | |
| #1626632 snapcraft part sources are not verified for authenticity | snapcraft (launchpad) | open | Feature request to add GPG signature verification for snapcraft part sources (source-signer-keys). Open ~10 years with 0 comments, no labels, no maintainer interaction; feature never implemented in current codebase. | |
| #4408 Snapcraft 7 fails with inline deb822 signing blocks | snapcraft | open | Snapcraft 7 core20 LXD builds fail on hosts with modern apt deb822 Signed-By blocks due to a legacy apt package check in snapcraft_legacy. Triaged; root cause identified, but snapcraft_legacy and core20 have since been removed from the codebase. | |
| #2054099 snapcraft (edge) fails to build core24 snaps. Running "apt update" within base container fails | snapcraft (launchpad) | open | snapcraft edge fails to build core24 snaps due to apt update failing with unresolved ftpmaster.internal in base container. Issue is 931 days old with no maintainer response. |