Lifecycle needs to track cross compilation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
Fix Released
|
High
|
Kyle Fazzari | ||
snapcraft (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* If a snap is built using a specific target architecture, and one tries to build it again for a different architecture, Snapcraft says the snap is already built.
[Test Case]
1. Build the 96boards-kernel example with `snapcraft --target-arch arm64`.
2. Build the 96boards-kernel example with `snapcraft --target-arch armhf`.
3. Note that Snapcraft doesn't try to rebuild the kernel for the new architecture, it says it's already done.
4. Apply the fix for this bug.
5. Build the 96boards-kernel example with `snapcraft --target-arch armhf`.
6. Note that Snapcraft now tries to rebuild the kernel using the new target architecture (which should fail-- all we care about is that it tries).
[Regression Potential]
* Dirty state tracking (rerunning steps if YAML sections change, bug #1477904) may not work correctly.
Changed in snapcraft: | |
assignee: | Sergio Schvezov (sergiusens) → Kyle Fazzari (kyrofa) |
Changed in snapcraft: | |
importance: | Critical → High |
milestone: | 2.7 → none |
Changed in snapcraft: | |
milestone: | none → 2.8.1 |
Changed in snapcraft: | |
milestone: | 2.8.1 → none |
Changed in snapcraft: | |
milestone: | none → 2.9 |
description: | updated |
Changed in snapcraft: | |
status: | In Progress → Fix Committed |
Changed in snapcraft (Ubuntu Xenial): | |
milestone: | none → xenial-updates |
Changed in snapcraft: | |
status: | Fix Committed → Fix Released |
Fix here: https:/ /github. com/ubuntu- core/snapcraft/ pull/450