LP2099966 is unrelated [1].
With the README's debug options [2]:
```
Selected version '0.40.0-4ubuntu0.1' (Ubuntu:24.04/noble-proposed [amd64]) for
'dconf-cli'
Selected version '0.40.0-4ubuntu0.1' (Ubuntu:24.04/noble-proposed [amd64]) for
'libdconf1' because of 'dconf-cli'
MarkInstall dconf-cli:amd64 < 0.40.0-4build2 -> 0.40.0-4ubuntu0.1 @ii pumU Ib
> FU=1
Upgrading libdconf1:amd64 < 0.40.0-4build2 | 0.40.0-4ubuntu0.1 @ii umH > due
to dconf-cli:amd64
Upgrading: dconf-service:amd64 < 0.40.0-4build2 @ii mK Ib > due to
dconf-service:amd64 Depends on libdconf1:amd64 < 0.40.0-4build2 ->
0.40.0-4ubuntu0.1 @ii pumU > (= 0.40.0-4build2)
Upgrading: dconf-gsettings-backend:amd64 < 0.40.0-4build2 @ii mK Ib > due
to dconf-gsettings-backend:amd64 Depends on libdconf1:amd64 < 0.40.0-4build2 ->
0.40.0-4ubuntu0.1 @ii pumU > (= 0.40.0-4build2)
MarkInstall libdconf1:amd64 < 0.40.0-4build2 -> 0.40.0-4ubuntu0.1 @ii pumU
> FU=0
MarkInstall dconf-service:amd64 < 0.40.0-4build2 @ii mK Ib > FU=0
dconf-service:amd64 Depends on libdconf1:amd64 < 0.40.0-4build2 ->
0.40.0-4ubuntu0.1 @ii pumU > (= 0.40.0-4build2) can't be satisfied! (dep)
Removing: dconf-service:amd64 as upgrade is not possible
MarkDelete dconf-service:amd64 < 0.40.0-4build2 @ii mK Ib > FU=0
MarkInstall dconf-gsettings-backend:amd64 < 0.40.0-4build2 @ii mK Ib >
FU=0
dconf-gsettings-backend:amd64 Depends on dconf-service:amd64 <
0.40.0-4build2 @ii pmR > (< 0.40.0-4build2.1~) can't be satisfied! (dep)
Removing: dconf-gsettings-backend:amd64 as upgrade is not possible
MarkDelete dconf-gsettings-backend:amd64 < 0.40.0-4build2 @ii mK Ib > FU=0
MarkInstall libc6:amd64 < 2.39-0ubuntu8.5 @ii pmK > FU=0
MarkInstall libgcc-s1:amd64 < 14.2.0-4ubuntu2~24.04 @ii pmK > FU=0
MarkInstall gcc-14-base:amd64 < 14.2.0-4ubuntu2~24.04 @ii pmK > FU=0
MarkInstall libglib2.0-0t64:amd64 < 2.80.0-6ubuntu3.4 @ii pmK > FU=0
MarkInstall libffi8:amd64 < 3.4.6-1build1 @ii pmK > FU=0
MarkInstall libmount1:amd64 < 2.39.3-9ubuntu6.3 @ii pmK > FU=0
MarkInstall libblkid1:amd64 < 2.39.3-9ubuntu6.3 @ii pmK > FU=0
MarkInstall libselinux1:amd64 < 3.5-2ubuntu2.1 @ii pmK > FU=0
MarkInstall libpcre2-8-0:amd64 < 10.42-4ubuntu2.1 @ii pmK > FU=0
MarkInstall zlib1g:amd64 < 1:1.3.dfsg-3.1ubuntu2.1 @ii pmK > FU=0
Starting pkgProblemResolver with broken count: 52
...
```
Grabbing all three packages instead of just one skips the
pkgProblemResolver and allows the install to proceed without issues:
```
sudo apt install dconf-cli/noble-proposed dconf-service/noble-proposed
dconf-gsettings-backend/noble-proposed
```
To test upgrades, I pinned -proposed to the same priority as the
archive:
```
sudoedit /etc/apt/preferences.d/proposed-upgrades
```
```
Package: *
Pin: release a=noble-proposed
Pin-Priority: 500
```
And the upgrade works just fine. I'm convinced that this isn't a
regression in dconf and won't cause issues for users in typical upgrade
scenarios. I've opened a bug to confirm that the behavior of
pkgProblemResolver is expected in this context [3].
The autopkgtest failures look mostly transient (lots of clock skew
failures due to meson's checking); thanks @mruffel for the re-runs.
[1]
https://salsa.debian.org/apt-team/apt/-/commit/935a9ab334e55a29363f45e7de6338c47337e806
[2] https://salsa.debian.org/apt-team/apt#dependency-resolution
[3] https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2121820
See also: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2099829
--
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
