reassign 671711 dpkg affects 671711 src:monodoc-browser thanks Hi,
Reassigning to dpkg per Ian and full-quoting for context in the bug.
On Wed, May 23, 2012 at 02:05:12PM +0100, Ian Jackson wrote:
> Iain Lane writes ("Assumptions when processing triggers (was [pkg-mono-group]
> Bug#671711: monodoc-browser: fails to upgrade) from 'testing'"):
> > 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=2.12.0.0, 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?)
Thanks a lot for your analysis. So it seems like this is the assumption
that isn't being held here: that dependencies will be satisfied when
postinst is run.
It would be great if you could prepare a patch. This issue could come up
whenever libgtk2.0-cil and monodoc-browser are upgraded in the same run,
which certainly will happen with squeeze→wheezy upgrades. Since failing
upgrades is really unfriendly, a patch for squeeze's dpkg seems required
(or, if this proves to be too hard, we could work around it with my
mentioned hack of having monodoc-browser register gtk# into the GAC
itself, or || true the failing call since having outdated documentation
indices isn't the end of the world).
Cheers,
--
Iain Lane [ [email protected] ]
Debian Developer [ [email protected] ]
Ubuntu Developer [ [email protected] ]
PhD student [ [email protected] ]
signature.asc
Description: Digital signature
