Hi seth-arnold Thanks for the review. For 1 - why do we need to set the permissions on /home/ubuntu and /boot/System.map - These permissions are different on ppc64el and s390x on prodstack. Adding needs-root to debian/tests/control also does not change anything, and I believe this is a configuration difference between architectures.
For 2 - I have rebased https://code.launchpad.net/~r41k0u/ubuntu/+source/nbd/+git/nbd/+merge/474033 to have a unified AppArmor policy, which gives the required capabilities just to mkfs.ext4. (I dived into debvm-create code, and it looks like if we run debvm-create as root, unshare should never have been called. These 2 issues only occurred on ppc64el and s390x even after needs-root was specified, which leads me to believe that these architectures on prodstack maybe don't honour that option, but I couldn't find this documented anywhere) Please let me know if there are any more concerns. We want to have nbdclient in 24.04.2, so this MIR would need to go through before that -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054480 Title: [MIR] nbd-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
