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
Desktop Bugs, 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
