Fix snapcraftyaml.yaml for jammy:linux-raspi
Bug #2051468 reported by
Masahiro Yamada
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
New
|
Undecided
|
Unassigned | ||
linux-raspi (Ubuntu) |
Fix Released
|
Medium
|
Masahiro Yamada | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
SRU Justification:
[Impact]
The in-tree snapcraft.yaml is stale. It does not produce any functional kernel
snap for jammy:linux-raspi.
[Fix]
Replace the stale snapcraft.yaml with a newly implemented one.
[Testcase]
Build a pi-kernel with the following command:
[for arm64]
$ snapcraft --use-lxd --build-for=arm64
for armhf]
$ snapcraft --use-lxd --build-for=armhf
Then, install it to Ubuntu Core 22 running on a raspi board.
$ snap install --dangerous <kernel-snap>
Please note you need "grade: dangerous" for replacing
the kernel using the local snap.
Changed in linux-raspi (Ubuntu): | |
assignee: | nobody → Masahiro Yamada (myamada) |
importance: | Undecided → Medium |
description: | updated |
description: | updated |
description: | updated |
Changed in linux-raspi (Ubuntu): | |
status: | New → Confirmed |
Changed in linux-raspi (Ubuntu Jammy): | |
status: | New → Fix Committed |
To post a comment you must log in.
the same is true for unstable and generic pc-kernel too