Ravi's asked me to take a look at sponsoring the noble upload. The diff looks reasonable (or at least as reasonable as binary blob packages ever do!), though I'm a bit concerned about the test plan...
1. The test plan talks about a noble image for one board, and a jammy image for one other board. It would appear no testing can be done for the current plucky and questing uploads because there are no corresponding images (what happens if users attempt to upgrade a noble image to plucky or questing?), and jammy is marked won't fix anyway (is that part of the test plan still relevant?) 2. The firmware files which are touched (according to the other info section) appear to cover rather more than just bluetooth and wifi (e.g. nvenv, nvjpg, presumably for video / image encode/decode, and a whole bunch of encryption stuff), but the test plan only seems to check bluetooth and wifi functionality? 3. The test plan talks about riverside-proposed; but I'd assume validators should be grabbing the package to test from $series-proposed (e.g. noble-proposed) Could someone take a look at the test plan again, and see if these concerns can be addressed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127473 Title: [SRU] Update linux-firmware-nvidia-tegra to 38.2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-nvidia-tegra/+bug/2127473/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
