On Thu, Jun 07, 2018 at 02:23:15PM -0700, Julian Andres Klode wrote: > On Thu, Jun 07, 2018 at 10:57:54PM +0200, Bill Allombert wrote: > > On Thu, Jun 07, 2018 at 09:57:51AM -0700, Julian Andres Klode wrote: > > > > Are you sure the upgrade failure are not caused by another patch that it > > > > applied by ubuntu ? > > > > > > Reasonably. > > > > > > > I have yet to see a single upgrade failure in Debian proper. > > > > > > It's still broken. Let's say you have foo shipping a menu file, and an > > > upgrade for > > > menu. APT might schedule it like this: > > > > > > unpack foo > > > unpack menu > > > configure foo > > > > So ? If menu is not configured, then update-menus is not executable, so > > test -x update-menus return false. > > So? The file trigger gets activated by the package being installed, so: > > unpack foo > unpack menu > <dpkg tries to run trigger for foo> > > And dpkg then fails because menu is not configured. Though, I don't know, > maybe it only fails if a dependency of menu is not configured, like in > the bug report: > > dpkg: dependency problems prevent processing triggers for menu: > menu depends on libstdc++6 (>= 4.6); however: > Package libstdc++6:amd64 is not configured yet.
What prevent dpkg to configure libstdc++6 in the first place ? The problem might be some package that menu depend on. I did not change the menu trigger code for a long time and nobody reported upgrade problems, so the change must be in some other package (or maybe this is a change in dpkg ?). In any case, you are welcome to do the change in Ubuntu. This way we will know if that breaks something. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here.
