Install wpasupplicant by default on RISC-V images
Bug #1983008 reported by
Alexandre Ghiti
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Most of RISC-V boards come with a Wifi chipset and some (like the licheeRV) don't even have an ethernet port. To ease user's life, we should install wpasupplicant by default so they can use the Wifi.
[Test Plan]
Build a VisionFive image (which is the only one that supports the Wifi for now) and at first boot, try to configure the Wifi using netplan.
Also, check if our raspi images are still building correctly with the same set of pre-installed packages.
[Where problems could occur]
There is always the risk to break the image for other architectures, and other RISC-V boards. Checking if raspi builds are still fine should be done as part of the validation.
Related branches
~alexghiti/livecd-rootfs:int/alex/riscv_wpasupplicant
- Łukasz Zemczak: Approve
- Ubuntu Core Development Team: Pending requested
-
Diff: 30 lines (+8/-0)2 files modifieddebian/changelog (+4/-0)
live-build/auto/config (+4/-0)
Changed in livecd-rootfs (Ubuntu Jammy): | |
milestone: | none → ubuntu-22.04.1 |
description: | updated |
To post a comment you must log in.
Hello Alexandre, or anyone else affected,
Accepted livecd-rootfs into jammy-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ livecd- rootfs/ 2.765.7 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification- needed- jammy to verification- done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- jammy. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.