← Back to issue list

snapcraft prints 'architectures' when trying to build a gadget snap

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1560481
Type
issue
State
closed
Author
~yann-sionneau
Labels
—
Created
Updated
Closed

Current evaluation

Gadget-snap build support was added in commit 5610f0eaf (PR #886).

Resolution: closed resolved

Reason: Commit 5610f0eaf, titled "Support for gadget snaps (#886)," added dedicated gadget-snap support. The fix followed the earlier work linked at ubuntu-core/snapcraft#393.

Evaluated by: mr-cal-bot

No scores available.

Issue body

What happens: yann@imperium:~/dev/snappy/1604/packages/paros_gadget$ snapcraft snap . 'architectures' What's inside the directory: yann@imperium:~/dev/snappy/1604/packages/paros_gadget$ find . . ./meta ./meta/snap.yaml yann@imperium:~/dev/snappy/1604/packages/paros_gadget$ cat meta/snap.yaml name: paros version: 1.0 summary: Paros support package description: Support files for booting Paros type: gadget branding: name: Paros drone gadget: software: platform: Tegra X1 architecture: armhf partition-layout: minimal bootloader: u-boot

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Gadget-snap build support was added in commit 5610f0eaf (PR #886).
stealth/space-bunny-alpha — closed resolved Merged Snapcraft PR #393 (commit ca2301a9d), allowing directory snaps to use architecture all and omit architectures, fixing gadget-snap builds.
stealth/space-bunny-alpha — closed resolved Fixed gadget-snap builds by supporting the "all" architecture during packaging; PR #393 merged as 0adafaa0f, with implementation commit ca2301a9d.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The report noted snapcraft printing 'architectures' during gadget snap builds but received no comments or follow-up.
qwen/qwen3.6-35b-a3b — — A bug report stating snapcraft prints 'architectures' when building gadget snaps was closed with zero comments and no resolution. The report shows no activity for over a decade, indicating it was abandoned without a fix.

Update history

Date Change
created

Related work

  • Related To: ubuntu-core/snapcraft#393 (confidence 99%)

    This was the sole linked pull request in the issue's closing discussion.

  • Likely Fixed By: ubuntu-core/snapcraft#886 (confidence 85%)

    Repository history identifies #886 as the gadget-snap support change addressing the build path.

Related issues

Issue Project State Summary Similarity
#1638824 Support gadget snaps snapcraft (launchpad) closed Gadget snap support (including gadget.yaml handling) was merged to snapcore/snapcraft via PR #886, commit 5610f0eaf 'Support for gadget snaps (#886)', after a successful PC gadget build; the launchpad issue was then closed.
73%
#1817288 snapcraft cleanbuild produces incorrect architecture snap snapcraft (launchpad) closed Bug (legacy cleanbuild naming a snap _multi.snap despite correct advanced architectures) was never fixed; closed in Aug 2023 by ~sergiusens noting cleanbuild is no longer supported and all builds are now transparently clean.
72%
#886 Support for gadget snaps snapcraft merged Merged PR #886 added gadget snap support, including gadget.yaml handling, in commit 5610f0eaf.
71%
#1685 Implement support for architecture in snapcraft.yaml snapcraft closed Architecture support for snapcraft.yaml landed in PR #2080 (commit c60ac3891), adding CI-oriented build-on/run-on lists. build.snapcraft.io adoption was tracked separately by cjwatson.
71%
#4214 snapcraft 7.4.3 doesn't adequately complain about non-existent architectures snapcraft closed Fixed in Snapcraft 8: invalid build-on architectures now produce a clear validation error listing all supported architectures.
71%
#1691569 snapcraft fails when specifying 'any' architecture in build packages snapcraft (launchpad) closed Fixed by snapcore/snapcraft PR #1322, which restored support for architecture-qualified build packages such as python:any.
70%
#1646081 Gadget snap cannot be built twice snapcraft (launchpad) open Second gadget-snap builds failed on gadget.yaml versus prime/meta/gadget.yaml; fixed by PR #3767 (c06e4df03).
70%