[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: gitweb breaks apache upgrade

Control: unmerge -1
Control: reopen -1
Control: affects -1 - gitweb src:git
Control: reassign -1 gitweb 1:2.1.4-2
Control: forcemerge 774803 -1


Giving it back. :)

On Mon, 2015-01-05 at 16:54:19 -0800, Jonathan Nieder wrote:
> Jonathan Nieder wrote:
> > Erwan David wrote[1]:
> >> dpkg: cycle found while processing triggers:
> >>  chain of packages whose triggers are or may be responsible:
> >>   gitweb -> gitweb
> >>  packages' pending triggers which are or may be unresolvable:
> >>   gitweb: /usr/share/apache2/apache2-maintscript-helper
> >> dpkg: error processing package gitweb (--configure):
> >>  triggers looping, abandoned
> >
> > gitweb does not contain a /usr/share/apache2/apache2-maintscript-helper
> > file.
> >
> > What's going on?
> [...]
> >> ii  dpkg             1.17.22

On 2015-01-07 21:29, Jonathan Nieder wrote:
> Puzzling.  What prevents the following upgrade path?
>  1. deconfigure gitweb
>  2. configure apache2
>  3. configure gitweb

Package deconfiguration is an exceptional operation, and there's no
way to explicitly request a deconfiguration, the closest thing is to
redo an unpack, something that frontends do not usually do. But more
importantly in this case doing that unpack resets the pending triggers
in gitweb which means they get lost, partially defeating the interest
directive, although the code will still be executed on the latter

In this case though, it seems switching to interest-noawait is the
correct fix, because gitweb just wants to be notified when the
apache2-maintscript-helper program appears to be able to configure
itself, but apache does not care and does not need to await the
trigger processing from gitweb for itself to be operational.

Hope that explains.


Reply to: