← Back to issue list

Wrong package source list

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1829819
Type
issue
State
open
Author
~holger-seelig
Labels
—
Created
Updated
Closed
—

Current evaluation

User (Feb 2019, snapcraft 3.4.1) asks how to build a core18 snap using host 19.04 Disco apt sources instead of the default bionic build VM. Usage question, no maintainer reply; documented answer is --destructive-mode.

Suggested action: close not a bug

Reason: The behaviour reported is snapcraft working as designed: the snap-packaged snapcraft builds in a clean Multipass/LXD VM pinned to the base's release (bionic for core18), while the reporter's working 2.43.1 deb was building on the host. This is a configuration/usage question, not a code defect, and the documented answer is the `--destructive-mode` flag (docs/reference/build-environment-options.rst: 'builds the snap directly on the machine where Snapcraft is run without launching a build container'). Confidence is not higher because I could not inspect snapcraft 3.4.1 itself (repo HEAD is 8.x) to confirm destructive mode was supported for core18 at the time, and no maintainer ever assessed the report, so the core18-base-vs-Disco-packages mismatch is unvalidated.

Evaluated by: mr-cal-bot

Impact: 18 Quick Win: 5 Complexity: 8 Confidence: 66 Actionability: 32

Issue body

With snapcraft, version 3.4.1 (from snap), it complains about missing packages that cannot be found, because it has Bionic source lists. With snapcraft, version 2.43.1+18.10 (from Ubuntu) everything works fine, it takes the sources from the system 19.04 (Disco). For my package I need the Disco sources. But i also need the new snapcraft, because I need the 'layout' keyword in the yaml. Is there a way to make the new snapcraft work with 19.04 Disco sources?

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 18
Quick Win: 5
Complexity: 8
Confidence: 66
Actionability: 32
close not a bug User (Feb 2019, snapcraft 3.4.1) asks how to build a core18 snap using host 19.04 Disco apt sources instead of the default bionic build VM. Usage question, no maintainer reply; documented answer is --destructive-mode.
stealth/space-bunny-alpha
Impact: 35
Quick Win: 10
Complexity: 25
Confidence: 78
Actionability: 40
needs triage Snapcraft 3.4.1 inside its snap used Bionic package sources rather than the host’s Disco lists; the reporter needs a documented way to build against those host sources.
qwen/qwen3.8-27b
Impact: 10
Quick Win: 9
Staleness: 95
Complexity: 10
Confidence: 72
Support Request: 90
close not a bug User asks how to make snapcraft 3.4.1 use Disco (19.04) apt sources instead of Bionic; behavior is working as intended for a core18 base. 7+ years old, no labels, no maintainer response.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 25
Confidence: 95
Support Request: 85
close stale User asks how to configure snapcraft 3.4.1 to use Ubuntu 19.04 Disco package sources instead of default Bionic lists. Issue is 7 years old with no activity.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 30
Confidence: 90
Support Request: 60
close stale User requests a way to make snapcraft 3.4.1 use Ubuntu 19.04 Disco sources instead of Bionic. Issue is 7 years old, inactive, and refers to an EOL OS.
qwen3.6-35b-a3b-mtp-q6
Staleness: 100
Complexity: 20
Confidence: 95
Support Request: 90
close stale User asks how to configure snapcraft to use Ubuntu 19.04 Disco sources instead of Bionic. Issue is 7 years old, has no comments or labels, and concerns an EOL OS.

Update history

Date Change
created

Related work

  • Related To: snapcraft (launchpad)#1583236 (confidence 35%)

    Same theme of snapcraft apt source handling, but that bug is about apt-get update failures being turned into package-list refresh errors, not about host-vs-VM source selection.

Related issues

No related issues found above the similarity threshold.