Bug#706110: libgnome{, vfs}2-common: fails to upgrade from squeeze: prerm failure: gconf-schemas: not found

Josselin Mouette joss at debian.org
Thu Apr 25 14:26:23 UTC 2013


Le jeudi 25 avril 2013 à 15:05 +0200, Michael Biebl a écrit : 
> A dangling /usr/bin/python symlink is indeed bad. At least that
> convinced me to never use anything pythonish in the maintainer scripts
> in the future.

I don’t think it is a problem for scripts in the postinst, nor in
triggered scripts. I thought prerm was supposed to be OK as long as
there are no loops in the upgrade (the policy is vague on the subject),
but this is not the first such problem I hear of.

> > 4) rewriting gconf-schemas only helps if gconf-schemas is upgraded
> >    before its reverse deps
> 
> All packages shipping gconf schemas have a Depends on gconf2. It is
> generated via dh_gconf which adds "gconf2 (>= 2.28.1-2)" to misc:Depends.
> 
> This version is already satisfied by gconf2 from squeeze. We could bump
> that and binNMU the rdeps. But then we'd have some arch:all rdeps (which
> would need sourceful uploads) and I'm actually not sure if a more
> tightened Depends actually ensures that the new gconf2 is unpacked
> before its rdeps. Does anyone know?

There is no such guarantee. Actually I am afraid dpkg even prefers
unpacking the rdep first.

Cheers,
-- 
 .''`.      Josselin Mouette
: :' :
`. `'
  `-




More information about the pkg-gnome-maintainers mailing list