snapcraft cleanbuild produces incorrect architecture snap

Bug #1817288 reported by Ian Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Won't Fix
Low
Unassigned

Bug Description

When using the stable release of the snapcraft snap, if one uses the advanced architectures yaml like:

```
architectures:
  - build-on: amd64
    run-on: amd64
  - build-on: armhf
    run-on: armhf
```

and without a base specified so snapcraft operates in legacy mode, then snapcraft cleanbuild will produce a "multi" file snap name like "snap-name_0.1_multi.snap", even though the snap.yaml in the snap itself has the correct architecture specification.

This can be reproduced on amd64 with snapcraft stable snap (revision 2496), and a basic snap without `base` and with the above architectures snippet and specificaly using snapcraft cleanbuild

Changed in snapcraft:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

cleanbuild is no longer supported, all builds by default now transparently "cleanbuild"

Changed in snapcraft:
status: Triaged → Won't Fix
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.