Getting this in 21.04
When I close the dialog with "close" It pops right back again and the upgrade
is stuck.
** Attachment added: "Screenshot_20210727_124636.png"
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5513993/+files/Screenshot_20210727_124636.png
--
You
** Changed in: gconf (Ubuntu)
Importance: Critical => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551623
Title:
[SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
Whew, this is a long bug.
So given comment 40 indicating part of this bug has been fixed in bug
1828639, and comment 42 indicating the any remaining patches should be
sent to debian, it seems to me that the ubuntu-sponsors team does not
need to be subscribed to this, as it's unclear what parts,
19.10->20.04 the same thing.
It is happened not to be a loop but a series of identical messages from
different packages. I package name should be included int the messages,
to help user better understand the issue
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm seeing the "Could not install 'gconf2'" error during upgrade from
19.10 to the 20.04 beta.
The crash reports says the error is "dependency problems - leaving
triggers unprocessed"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, completely forgot about it... :-/
So bug 1828639 is now fixed. I guess no need to fix gconf triggers now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551623
Title:
[SRU] package gconf2
Given comment #40 and the fixed dpkg, we're going to decline the rls
nomination for eoan. It's possible/probable that those patches are right
anyway - please could you submit them ideally via a merge request on
salsa.debian.org?
** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing
--
Oh, nice. Maybe then gconf patches won't be needed. (Still need to fix
FTBFS in Bionic, bug 1834211.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551623
Title:
[SRU] package gconf2
For the record our plan is to backport the trigger processing fixes and
that work is being tracked in bug 1828639.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551623
Title:
[SRU] package gconf2
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551623
Title:
[SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
dependency problems - leaving triggers
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
No, Debian package doesn't have this change. As for the bug reports, I
only found a mention of this issue in a report for dpkg:
https://bugs.debian.org/774794
** Bug watch added: Debian Bug tracker #774794
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774794
--
You received this bug
Thanks for working on this and preparing the debdiffs. Has the debian
package changed from interest to interest-noawait? Is there a bug in
debian regarding this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
13 matches
Mail list logo
