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

Re: Bug#431193: openoffice.org-voikko: Potentially unsafe upgrade



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Harri Pitkänen wrote:
> Preparing to replace openoffice.org 2.2.1~rc1-1 (using .../openoffice.org_2.2.1-2+b1_amd64.deb) ...
> Unpacking replacement openoffice.org ...
> dpkg: openoffice.org-core: dependency problems, but removing anyway as you request:
>  openoffice.org-voikko depends on openoffice.org-core (>= 2.2.1~rc1).
> (Reading database ... 217245 files and directories currently installed.)
> Removing openoffice.org-core ...         <------- OLD VERSION OF OPENOFFICE.ORG IS REMOVED HERE
> (Reading database ... 217014 files and directories currently installed.)
[..]
> Preparing to replace openoffice.org-voikko 2.0.1-1 (using .../openoffice.org-voikko_2.0.1-1+b2_amd64.deb) ...
> Voikko removed from OpenOffice.org.     <-------- OLD VERSION OF THE EXTENSION IS UNREGISTERED HERE. THIS COULD FAIL!
> Unpacking replacement openoffice.org-voikko ...
> 
> [...]
> 
> Setting up openoffice.org-voikko (2.0.1-1+b2) ...
> Voikko installed for OpenOffice.org.   <--------- NEW VERSION OF THE EXTENSION IS REGISTERED HERE
> 
> [...]
> 
> 
> The safe order would be to
>   1) unregister the old version of openoffice.org-voikko
>   2) replace the openoffice.org binaries
>   3) register the new version of openoffice.org-voikko

So that would mean OOo unregistering any extension before it is upgraded
and registering them again after the upgrade. Yes, this would be
possible, but needs a policy (all extensions installed in the same
place[1] so that OOo can unregister/register them itself when needed).

I am working on this.

> Although in this particular case unregistering openoffice.org-voikko succeeded,
> this may change later when library dependencies of openoffice.org evolve, and
> may break etch->lenny upgrade.

We should fix this before lenny indeed.

Regards,

Rene

[1]
the extensions built out of the OOo source package (openoffice.org-report-builder and
openoffice.org-sdbc-postgresql) actually already use
/usr/lib/openoffice/share/extension/install, which is upstreams
recommended location for "bundled" extensions:

Selecting previously deselected package openoffice.org-sdbc-postgresql.
(Reading database ... 274074 files and directories currently installed.)
Unpacking openoffice.org-sdbc-postgresql (from openoffice.org-sdbc-postgresql_0.7.4+OOo2.3.0~oog680m1-0.1pre_i386.deb) ...
Selecting previously deselected package openoffice.org-report-builder.
Unpacking openoffice.org-report-builder (from openoffice.org-report-builder_1.0.0+OOo2.3.0~oog680m1-0.1pre_i386.deb) ...
Setting up openoffice.org-sdbc-postgresql (1:0.7.4+OOo2.3.0~oog680m1-0.1pre) ...
Adding extension /usr/lib/openoffice/share/extension/install/postgresql-sdbc-0.7.4.zip... done.

Setting up openoffice.org-report-builder (1:1.0.0+OOo2.3.0~oog680m1-0.1pre) ...
Adding extension /usr/lib/openoffice/share/extension/install/sun-report-builder.oxt... done.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGwt+u+FmQsCSK63MRAhLpAJ9TGjvJ1c431Qsp8u0z9dJ/xE05LQCffUVr
eV0ccCYKU1l7bT8lzyzIfGY=
=xzM+
-----END PGP SIGNATURE-----



Reply to: