Hello Alexandre, or anyone else affected, Accepted util-linux into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/util- linux/2.36.1-8ubuntu2 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- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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/PerformingSRUVerification . 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. ** Changed in: util-linux (Ubuntu Impish) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944741 Title: HiFive Unmatched partitions are named "Unleashed" Status in util-linux package in Ubuntu: New Status in util-linux source package in Impish: Fix Committed Status in util-linux package in Debian: Confirmed Bug description: [Impact] Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. This issue gives the feeling that the Ubuntu RISC-V images made specifically for those 2 boards were assembled in a rushed manner. The attached patch fixes this by removing the 'Unleashed' part of the current name so that it fits both, it was build againt all architectures here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12783067/+listing-archive-extra [Test Plan] 1. Download the SiFive Unmatched image here: https://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/pending/impish-preinstalled-server-riscv64+unmatched.img.xz 2. Follow instructions here to launch a riscv64 VM: https://wiki.ubuntu.com/RISC-V 3. Execute the following command: ubuntu@ubuntu:~$ sudo fdisk -l Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 0F66C0C3-A5E4-439B-907E-ABAD106FE4A7 Device Start End Sectors Size Type /dev/vda1 235554 83886046 83650493 39.9G Linux filesystem /dev/vda12 227362 235553 8192 4M Linux filesystem /dev/vda13 34 2081 2048 1M HiFive Unleashed FSBL /dev/vda14 2082 10273 8192 4M HiFive Unleashed BBL /dev/vda15 10274 227361 217088 106M EFI System Partition table entries are not in disk order. 4. Download and install the new packages that contain the fix here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/libfdisk1_2.36.1-8ubuntu4_riscv64.deb https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/libfdisk-dev_2.36.1-8ubuntu4_riscv64.deb https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+files/fdisk_2.36.1-8ubuntu4_riscv64.deb 5. Re-execute the same command as above: ubuntu@ubuntu:~$ sudo fdisk -l Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 0F66C0C3-A5E4-439B-907E-ABAD106FE4A7 Device Start End Sectors Size Type /dev/vda1 235554 83886046 83650493 39.9G Linux filesystem /dev/vda12 227362 235553 8192 4M Linux filesystem /dev/vda13 34 2081 2048 1M HiFive FSBL /dev/vda14 2082 10273 8192 4M HiFive BBL /dev/vda15 10274 227361 217088 106M EFI System Partition table entries are not in disk order. [Where problems could occur] We may expect regressions if one uses fdisk output (ie the partition names instead of the UUIDs) in her software: this risk is mitigated by the fact the upstream accepted the patch and then does not expect this interface to be immutable and that RISC-V is not widely used yet. [Other Info] None. === old bug description === Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same UUIDs to load the next stage bootloader: the current name makes partitions on Unmatched board appear as 'Unleashed'. Fix that by removing the 'Unleashed' part of the current name so that it fits both. The attached debdiff contains the patch that was merged upstream (https://github.com/karelzak/util-linux/commit/10fd91d389497d8be435cc66abbdeb2eb6ea2f07). ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
