One clarification to my previous comment, since I don't want this to block the SRUs unnecessarily: the noble and jammy SRU branches (the 26.02.2 SRU exception uploads for LP: #2143088) ship the same postinst as develL neither includes the group changes. So there is no regression path for noble upgraders: devel and the proposed SRUs are consistent.
The substantive fix for this bug (the Python-side group ownership of the data path and persist files, which is what resolves the landscape-config failure under umask 027) is already in 26.02.2, i.e. in devel and in both SRU uploads. The devel postinst sync MP is a follow-up to fully align the packaging with upstream 26.02.2. Nice to land, but it doesn't need to gate the noble/jammy sponsorship. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065879 Title: [SRU] landscape-config problem with hardened umask 027 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2065879/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
