This bug was fixed in the package mutter - 3.30.2-1~ubuntu18.10.2
---------------
mutter (3.30.2-1~ubuntu18.10.2) cosmic; urgency=medium
* Update gbp.conf and Vcs metadata for cosmic
* control: Depend on g-s-d-schemas instead of g-s-d. We only need the
schemas. (LP: #1808796)
-- Iain Lane <[email protected]> Mon, 17 Dec 2018 10:53:41 +0000
** Changed in: mutter (Ubuntu Cosmic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1808796
Title:
gnome-settings-daemon FTBFS in cosmic-proposed due to circular
relationship involving mutter
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Cosmic:
Fix Released
Bug description:
[ Description ]
Currently gnome-settings-daemon can't be built in cosmic-proposed for
arm64 and armhf:
The following packages have unmet dependencies:
sbuild-build-depends-gnome-settings-daemon-dummy : Depends: mutter (>=
3.27.90) but it is not going to be installed
analysing the situation with chdist shows:
The following packages have unmet dependencies.
mutter : Depends: gnome-settings-daemon but it is not going to be installed
and then diving further:
The following packages have unmet dependencies.
gnome-settings-daemon : Depends: gnome-settings-daemon-schemas (=
3.30.1.2-1ubuntu2) but 3.30.1.2-1ubuntu3 is to be installed
What has happened is that gnome-settings-daemon indirectly ends up
Build-Depending on gnome-settings-daemon again:
src:g-s-d - (BD) -> mutter - (D) -> g-s-d
gnome-settings-daemon has "Depends: gnome-settings-daemon-schemas (=
${source:Version})". This in itself is correct, but when the arch:all
gnome-settings-daemon-schemas is published before an arch-only build
is picked up, we have skew that results in this failure. g-s-d-schemas
3.30.1.2-1ubuntu3 is available, but g-s-d 3.30.1.2-1ubuntu2, the
strict dependency means it is uninstallable.
Presumably we'd gotten lucky up until now and never had a newer
g-s-d-schemas published before all other arches at least started
building.
[ Fix ]
Cut the arch:any part of the circular dependency. We make mutter
Depend on gnome-settings-daemon-schemas instead, since it only needs
the schemas and not running daemons. We still have a circular BD/D
chain from g-s-d to itself, but now it looks like:
src:g-s-d - (BD) -> mutter - (D) -> g-s-d-schemas
...importantly there are no strict version requirements any more, so
this kind of skew isn't a problem. If mutter ever changes to have
"Depends: gnome-settings-daemon-schemas (>= some-version)", this
should also work - since the arch:all gnome-settings-daemon-schemas
will be installable everywhere.
[ QA ]
I tested this in a bileto silo and it worked:
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3567/+packages
Once the fixed mutter is published, we should be able to retry the
g-s-d builds.
[ Regression potential ]
mutter will no longer Depend on gnome-settings-daemon itself (the
daemons). This might expose missing g-s-d dependencies from other
packages. These could only be out-of-archive packages though:
laney@raleigh> reverse-depends -r cosmic mutter
Reverse-Depends
===============
* gnome-shell
* vanilla-gnome-desktop
and both of these depend on gnome-settings-daemon already.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1808796/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
