As long as all policies from: https://www.debian.org/doc/debian-policy/ch-files.html#configuration- files
and other packaging guidelines are kept, there should be no issues. But, the intent here is something else in my understanding: to avoid breakage so the SRU is accepted by the SRU team. Let's say an user has the environment configured and working and suddenly we decide to move correctly configured files to .bak just because the binaries were updated and we "thought" it could be better. That would break an environment for no reason. Like open-iscsi iqn generation, we want also to make sure that generated uuids/iqns/nqns are NOT wiped in the package purging (thus the test in my first comment for Groovy). We have to make sure the Focal version also behaves like that... just like open-iscsi does: [rafaeldtinoco@work iscsi]$ ls initiatorname.iscsi iscsid.conf [rafaeldtinoco@work iscsi]$ apt-file list open-iscsi | grep etc open-iscsi: /etc/default/open-iscsi open-iscsi: /etc/init.d/iscsid open-iscsi: /etc/init.d/open-iscsi open-iscsi: /etc/iscsi/iscsid.conf where /etc/iscsi/initiatorname.iscsi is not wiped (cause it contains the iqn). Makes sense to you both ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867366 Title: hostnqn fails to automatically generate after installing nvme-cli To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1867366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
