[Bug 2072586] [NEW] Running "dconf update" with different umask affects the permissions of dconf databases in /etc/dconf/db/

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[ Test Plan ]

```
sudo apt-get install dconf-cli
mkdir -p /etc/dconf/db/database.d
cat >/etc/dconf/db/database.d/test <<EOF
[test]
hello='world'
EOF
dconf update
ls -la /etc/dconf/db/database
umask 0077
dconf update
ls -la /etc/dconf/db/database
```

/etc/dconf/db/database should be 0644 after the second `dconf update`.


[ Original Description ]

Is it possible to include this [1] upstream fix in Jammy and Noble?

Steps to reproduce:
```
root at test-jammy-01:/etc/dconf/db# dconf update
root at test-jammy-01:/etc/dconf/db# ls -l local
-rw-r--r-- 1 root root 61 Jul  9 12:27 local
root at test-jammy-01:/etc/dconf/db# umask
0022
root at test-jammy-01:/etc/dconf/db# umask 0077
root at test-jammy-01:/etc/dconf/db# umask
0077
root at test-jammy-01:/etc/dconf/db# dconf update
root at test-jammy-01:/etc/dconf/db# ls -l local
-rw------- 1 root root 61 Jul  9 12:28 local
root at test-jammy-01:/etc/dconf/db# apt-cache policy dconf-cli
dconf-cli:
  Installed: 0.40.0-3
  Candidate: 0.40.0-3
  Version table:
 *** 0.40.0-3 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status
```

Danger of unexpected misconfiguration is great: others require read
access to dconf-databases or their dconf-settings will not update as
expected.

[1] - https://gitlab.gnome.org/GNOME/dconf/-/issues/25

** Affects: glib2.0 (Ubuntu)
     Importance: Undecided
     Assignee: Wesley Hershberger (whershberger)
         Status: Triaged


** Tags: sts
-- 
Running "dconf update" with different umask affects the permissions of dconf databases in /etc/dconf/db/
https://bugs.launchpad.net/bugs/2072586
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to glib2.0 in Ubuntu.