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

Re: Assumptions when processing triggers (was [pkg-mono-group] Bug#671711: monodoc-browser: fails to upgrade) from 'testing'

Iain Lane writes ("Assumptions when processing triggers (was [pkg-mono-group] Bug#671711: monodoc-browser: fails to upgrade) from 'testing'"):
> Greetings,
> [ I already asked this on d-dpkg, but go no response, so am "re-posting"
>   this question to -devel. The original report along with full log is in
>   #671711 ]
> On Sun, May 06, 2012 at 10:37:53AM +0200, Andreas Beckmann wrote:
> > […]
> > Hi,
> > 
> > during a test with piuparts I noticed your package fails to upgrade from
> > 'testing'.
> > It installed fine in 'testing', then the upgrade to 'sid' fails.
> > 
> > >From the attached log (scroll to the bottom...):
> > 
> >   Preparing to replace monodoc-clutter-manual 1.0.0~alpha3~git20090817.r1.349dba6-7 (using .../monodoc-clutter-manual_1.0.0~alpha3~git20090817.r1.349dba6-8_all.deb) ...
> >   Unpacking replacement monodoc-clutter-manual ...
> >   Processing triggers for monodoc-browser ...
> >   generating monodoc search index...
> >   grep: /etc/gre.d/*.conf: No such file or directory
> >   
> >   Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'gtk-sharp, Version=, Culture=neutral, PublicKeyToken=35e10195dab3c99f' or one of its dependencies.
> >   dpkg: error processing monodoc-browser (--unpack):
> >    subprocess installed post-installation script returned error exit status 1
> It's because libgtk2.0-cil (on which monodoc-browser depends) has been
> unpacked but not configured at this point. I thought (from reading
> /usr/share/doc/dpkg-dev/triggers.txt.gz):

I think this is a bug.

> ,----
> | Packages in t-awaited and t-pending demand satisfaction of their
> | dependencies just like packages in installed.
> `----

This is true, but doesn't help you.  The unpack of libgtk2.0-cil can
be started, moving it from installed to (eventually) unpacked, without
causing monodoc-browser to be deconfigured, and this is nothing to do
with triggers.

But as you point out there is an additional requirement (perhaps not
specified in the docs) that all the dependencies should be satisfied
when the postinst is run.

Would you like me to try to look into it and prepare a patch for dpkg ?
(Do you need this to be fixed in squeeze or will wheezy/sid do?)


Reply to: