Cannot use --build-on, architecture list is already set in snapcraft.yaml.

Bug #1885150 reported by John Lenton
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned
Snapcraft
Confirmed
Undecided
Unassigned

Bug Description

If my snap has no 'architectures' entry, I can happily do

snapcraft remote-build --build-on=armhf

However as soon as I add something like, say

architectures:
  - build-on: armhf
  - build-on: amd64

then I can no longer ask for just the armhf build from the commandline; I need to edit the yaml directly.

This is awkward when I'm trying to fix build errors in particular architectures in my snap.

John Lenton (chipaca)
description: updated
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

We error on this as launchpad will ignore the request if an architectures entry is set in snapcraft.yaml.

Happy to remove it as soon as it is fixed on Launchpad.

Chris Patterson (cjp256)
Changed in snapcraft:
status: New → Confirmed
Revision history for this message
Snapcrafters Bot (snapcrafters-bot) wrote :

Has this been fixed in Launchpad? This makes it difficult to use the GitHub actions "matrix" for building snaps, as every instance of the matrix will build all versions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.