On Tue, Jun 05, 2018 at 11:16:43PM +0200, Bill Allombert wrote:
> On Tue, Jun 05, 2018 at 11:39:52AM -0700, Julian Andres Klode wrote:
> > Package: menu
> > Severity: normal
> > User: ubuntu-de...@lists.ubuntu.com
> > Usertags: origin-ubuntu
> >
> > menu currently uses interest triggers, causing packages triggering it to
> > not be
> > configured until the trigger has run (so if A installs a menu file, dpkg
> > --configure A
> > first updates menu and then configures A). There's no point in doing that,
> > especially
> > with the intended semantic that the trigger should run after the package is
> > configured - it's mostly the opposite of what you want.
>
> Hello Julian,
>
> I agree. However update-enus is supposed to wait until dpkg terminate
> before running, so at this point the package should be configured.
>
> > The use of interest instead of interest-noawait causes a lot of upgrade
> > failures for
> > Ubuntu[1], hence I applied the patch there in the development release and
> > will push it
> > out for stable releases too.
> >
> > Please consider doing the same for Debian, to reduce upgrade failures there.
>
> 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
which is wrong. The rule for await triggers is: If your packages triggers
another,
it needs to depend on it. Hence we have two options: Change menu to noawait, or
make
all packages shipping menu files depend on menu.
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
