** Description changed: Original report ========================= Unless there’s a clear reason to change, we should continue using busybox in the initrd due to its smaller footprint. Prior to 25.10, Ubuntu images used different coreutils. gnu coreutils in the root filesystem and busybox in the initramfs. We can keep this approach, with rust-coreutils replacing GNU coreutils. ========================= [ Impact ] - * The change to rust-coreutils in the initramfs was accidental, only + * The change to rust-coreutils in the initramfs was accidental, only the userspace gnu coreutils was supposed to be replaced with rust- coreutils. We do not want to increase the size of initramfs. This has a much larger impact on devices with small boot partition like Raspberry Pi where we are not able to hold 2 sets of Boot Assets for A/B Boot. [ Test Plan ] - * detailed instructions how to reproduce the bug + * detailed instructions how to reproduce the bug - * these should allow someone who is not familiar with the affected - package to reproduce the bug and verify that the updated package - fixes the problem. + * these should allow someone who is not familiar with the affected + package to reproduce the bug and verify that the updated package + fixes the problem. - * if other testing is appropriate to perform before landing this - update, this should also be described here. + * if other testing is appropriate to perform before landing this + update, this should also be described here. + + Check that rust-coreutils in not included in the initrd. This can be + done by running: + + sudo 3cpio -tv /boot/initrd.img | grep usr/lib/cargo/bin/coreutils [ Where problems could occur ] - * Think about what the upload changes in the software. Imagine the - change is wrong or breaks something else: how would this show up? + * Think about what the upload changes in the software. Imagine the + change is wrong or breaks something else: how would this show up? - * It is assumed that any SRU candidate patch is well-tested before - upload and has a low overall risk of regression, but it's important - to make the effort to think about what ''could'' happen in the event - of a regression. + * It is assumed that any SRU candidate patch is well-tested before + upload and has a low overall risk of regression, but it's important + to make the effort to think about what ''could'' happen in the event + of a regression. - * This must never be "None" or "Low", or entirely an argument as to why - your upload is low risk. + * This must never be "None" or "Low", or entirely an argument as to why + your upload is low risk. - * This both shows the SRU team that the risks have been considered, - and provides guidance to testers in regression-testing the SRU. + * This both shows the SRU team that the risks have been considered, + and provides guidance to testers in regression-testing the SRU. [ Other Info ] - * Anything else you think is useful to include + * Anything else you think is useful to include - * Make sure to explain any deviation from the norm, to save the SRU - reviewer from having to infer your reasoning, possibly incorrectly. - This should also help reduce review iterations, particularly when the - reason for the deviation is not obvious. + * Make sure to explain any deviation from the norm, to save the SRU + reviewer from having to infer your reasoning, possibly incorrectly. + This should also help reduce review iterations, particularly when the + reason for the deviation is not obvious. - * Anticipate questions from users, SRU, +1 maintenance, security teams - and the Technical Board and address these questions in advance + * Anticipate questions from users, SRU, +1 maintenance, security teams + and the Technical Board and address these questions in advance
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2150657 Title: Use busybox instead of rust-coreutils in initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2150657/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
