It could be that Debian won't need this change. Looks like all the
triggers are now processed near the end of upgrade, due to changes in
dpkg itself.
Possibly related entry from dpkg 1.19.3 changelog:
* dpkg: Introduce a new dependency try level for trigger processing. This
completely defers trigger processing until after the dependency cycle
breaking level, so to avoid generating artificial trigger cycles, when we
end up trying to process triggers with yet unsatisifiable dependencies.
Closes: #810724, #854478, #911620
https://bugs.debian.org/810724
And from dpkg 1.19.7 changelog:
* dpkg: Split the trigger dependtry into two, the second of which will be
the one checking trigger cycles when deferring trigger processing due to
unsatisfiable dependencies. Closes: #928429
https://bugs.debian.org/928429
** Bug watch added: Debian Bug tracker #810724
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810724
** Bug watch added: Debian Bug tracker #928429
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928429
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1551623
Title:
[SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
dependency problems - leaving triggers unprocessed
Status in gconf package in Ubuntu:
Triaged
Bug description:
[Impact]
During system upgrades, triggers for gconf2 might activate too early,
while some of its dependencies aren't configured yet. This happens
several times in a loop and stops the upgrade in the end.
The attached debdiffs fix this issue by changing interest to interest-
noawait in debian/gconf2.triggers file. The triggers will now activate
near the end of upgrade.
In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
1834211).
[Test Case]
Triggers for gconf2 are usually activated on changes in
/usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
GNOME) is most suitable for reproducing the issue. To reproduce it,
install that edition, apply all updates, then try upgrading to the
next release.
[Regression Potential]
None, interest-noawait trigger is known to work well in other packages
(comment 31).
[Other Info]
Even if Cosmic goes EOL next month, the fix for it might be worth it
for release upgrades.
[Original Description]
When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured,
alongside many others related to systemd and gnome.
Notice that despite all warnings and errors, finally, the system remained
functional.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gconf2 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Tue Mar 1 09:21:15 2016
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2015-10-04 (148 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1
apt 1.2.3
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
