This bug is awaiting verification that the linux-gke/6.8.0-1004.7 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-noble-linux-gke' to 'verification-done-noble-linux-
gke'. If the problem still exists, change the tag 'verification-needed-
noble-linux-gke' to 'verification-failed-noble-linux-gke'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-gke-v2 verification-needed-noble-linux-gke
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2051468
Title:
Fix snapcraftyaml.yaml for jammy:linux-raspi
Status in linux package in Ubuntu:
Fix Released
Status in linux-raspi package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
New
Status in linux-raspi source package in Jammy:
Fix Released
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051468/+subscriptions
Комментариев нет:
Отправить комментарий