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

[Michael Biebl]

Am 24.04.2013 21:38, schrieb Andreas Beckmann:
> Package: libgnome2-common,libgnomevfs2-common
> Version: 2.32.1-2
> Severity: serious
> User: debian-qa at lists.debian.org
> Usertags: piuparts
> Control: found -1 1:2.24.4-1
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'squeeze'.
> It installed fine in 'squeeze', then the upgrade to 'wheezy' fails.
> 
>>From the attached log (scroll to the bottom...):
> 
>   Preparing to replace libgnome2-0 2.30.0-1 (using .../libgnome2-0_2.32.1-2_amd64.deb) ...
>   Unpacking replacement libgnome2-0 ...
>   Preparing to replace libgnome2-common 2.30.0-1 (using .../libgnome2-common_2.32.1-2_all.deb) ...
>   /var/lib/dpkg/info/libgnome2-common.prerm: 6: gconf-schemas: not found
>   dpkg: warning: subprocess old pre-removal script returned error exit status 127
>   dpkg: trying script from the new package instead ...
>   dpkg: error processing /var/cache/apt/archives/libgnome2-common_2.32.1-2_all.deb (--unpack):
>    there is no script in the new version of the package - giving up
>   configured to not write apport reports
> 
>   Preparing to replace libgnomevfs2-common 1:2.24.3-1 (using .../libgnomevfs2-common_1%3a2.24.4-1_all.deb) ...
>   /var/lib/dpkg/info/libgnomevfs2-common.prerm: 6: gconf-schemas: not found
>   dpkg: warning: subprocess old pre-removal script returned error exit status 127
>   dpkg: trying script from the new package instead ...
>   dpkg: error processing /var/cache/apt/archives/libgnomevfs2-common_1%3a2.24.4-1_all.deb (--unpack):
>    there is no script in the new version of the package - giving up
>   configured to not write apport reports
> 
> 
> This bug seems to require a certain upgrade sequence slected by apt ...
> 
> A quick workaround would be adding back an empty prerm script.
> 

Registering gconf schemas has been triggerized, that's why the
libgnome2-common package in wheezy no longer has any maintainer scripts
which call gconf-schemas.

What's really weird though: In both squeeze and wheezy, libgnome2-common
(actually any package shipping gconf schemas) has a Depends: gconf2
(which provides the gconf-schemas tool).

So during the upgrade gconf2 is in an uninstalled state while packages
still depend on it. Isn't this a bug in apt? I know that preinst
dependencies require Pre-Depends and calling tools in postrm require
explicit checks for the existence of the tools. I wasn't aware that
prerm was problematic too?

Since libgnome2-common is not the only package shipping gconf schemas (I
count 226 packages in squeeze), wouldn't this mean potentially any of
those packages is affected by this?

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20130424/e156a338/attachment-0002.pgp>