Note to SRU Team: Plucky and questing having the same version creates an issue, namely we would need to no-change rebuild dconf on questing to be able to fix plucky.
I did ask upstream dconf if they would be interested in making a new release, but no one seems very keen on the idea: https://gitlab.gnome.org/GNOME/dconf/-/issues/89 I think no-change building dconf on questing just creates extra work later for the Desktop Team when they need to sync dconf in from Debian. DISA STIG is not available or supported on plucky, and the number of users changing their global umask on plucky will literally be zero. I think we should deliberately not fix plucky, and only fix jammy and noble. Questing is already fixed via the change to glib, so there is a valid upgrade path. If you want plucky fixed, please let us know and we will no-change rebuild questing and make the plucky fix happen. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2072586 Title: Running "dconf update" with different umask affects the permissions of dconf databases in /etc/dconf/db/ To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/2072586/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
