← Back to issue list

remote-build doesn't work with gadget snaps

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1875524
Type
issue
State
open
Author
~anonymouse67
Labels
Created
Updated
Closed

Current evaluation

snapcraft remote-build fails to copy gadget.yaml to the generated Launchpad project, breaking gadget snap builds. Unlabelled, zero comments, inactive ~6 years. The remote-build command was removed in snapcraft 2.0, so the issue no longer applies.

Suggested action: close stale

Reason: The issue has 0 comments, no labels, and no maintainer interaction, with last activity ~2195 days ago (~6 years). The remote-build command was part of snapcraft 1.x and was removed in snapcraft 2.0 (the current codebase shows the 2.x layout with no remote-build command), so the reported bug is no longer applicable; the reporter's own workaround (LP git project with a snap recipe) is the standard approach. Confidence is moderate because code inspection tools were unavailable to directly confirm the command's removal.

Impact: 15 Quick Win: 10.5 Staleness: 95 Complexity: 30 Confidence: 70 Support Request: 10

Issue body

It seems that snapcraft when building gadget snaps has a check at the very end that there is a gadget.yaml in the root of the project directory, but snapcraft remote-build does not copy this file to the generated launchpad project, and thus it does not properly build gadget snaps. I took the exact same project and uploaded to to a lp git project and created a snap recipe and it just worked fine, presumably because the gadget.yaml file was there.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 15
Quick Win: 10.5
Staleness: 95
Complexity: 30
Confidence: 70
Support Request: 10
close stale snapcraft remote-build fails to copy gadget.yaml to the generated Launchpad project, breaking gadget snap builds. Unlabelled, zero comments, inactive ~6 years. The remote-build command was removed in snapcraft 2.0, so the issue no longer applies.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 35
Confidence: 80
Support Request: 10
needs triage snapcraft remote-build fails to copy gadget.yaml to Launchpad projects, breaking gadget snap builds. Untriaged, no maintainer interaction, inactive for over six years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 40
Confidence: 75
Support Request: 10
close stale snapcraft remote-build fails to copy gadget.yaml for gadget snaps, causing build failures on Launchpad while local builds succeed. Issue is over 6 years old with no maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 25
Confidence: 85
Support Request: 5
close stale Bug report stating snapcraft remote-build fails for gadget snaps due to missing gadget.yaml in generated Launchpad projects. Untriaged and inactive for over 5 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 40
Confidence: 80
Support Request: 10
close stale remote-build fails for gadget snaps because snapcraft omits the required gadget.yaml file when generating the Launchpad project. The report remains open, unassigned, and inactive with no comments, awaiting triage and a fix.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft (launchpad)#1646081 (confidence 40%)

    Another old, unlabelled gadget-snap build bug (cannot build twice in same directory); different symptom, not a duplicate.

Related issues

Issue Project State Summary Similarity
#1646081 Gadget snap cannot be built twice snapcraft (launchpad) open Building a gadget snap twice in the same directory fails with a 'gadget.yaml and prime/meta/gadget.yaml are the same file' error on snapcraft 2.22.1. Unlabelled, no comments, 3561 days old, references a deprecated version.
72%