Bug#703486: [libreoffice] Does not keep extensions on upgrate from 3.x
Hi,
On Wed, Mar 20, 2013 at 10:31:42AM +0100, Landry MINOZA wrote:
> When migrating from version 3.6, none of my user extensions are kept,
Which ones? Some are blacklisted:
http://cgit.freedesktop.org/libreoffice/core/tree/officecfg/registry/data/org/openoffice/Setup.xcu?id=7e5467ff8f30d821f4fbf69cb2769163eb64c2cc#n790
(but those listed there shouldn't have been installed as user extension
anyways as they always were available "proper")
Discussed this with upstream:
10:36 <@_rene_> user extensions are not migrated from 3.6 -> 4.0 on
purpose, right?
10:37 <@_rene_> (I just got http://bugs.debian.org/703486)
10:39 <@sberg> _rene_, no, per-user (not shared or bundled) extensions
should be migrated (except for those blacklisted in
officecfg/registry/data/org/openoffice/Setup.xcu)
10:39 <@_rene_> since when?
10:39 <@_rene_> http://bugs.debian.org/703486 claims it isn't...
10:39 <@sberg> _rene_, should always have worked with LO 4
10:40 <@_rene_> so what might have gone wrong here?
10:41 <@sberg> _rene_, I don't see any relevant data backing the claim
there, so hard to tell what went wrong
10:41 <@_rene_> yeah, I am writing a reply now asking him for that, that's
why I asked the initial question...
so we need more info. probably the user profile of both. (you can send it per
PM if you don't want to attach it here.)
(That said, I personally consider it not "important", it's trivial to
re-add them.
And
- binary-only extensions using stlport will only work by
chance in 4.0.x as long as you still have libstlport4.6 installed, see
e.g. https://wiki.documentfoundation.org/ReleaseNotes/4.0#Duden_Rechtschreibpr.C3.BCfung_.2F_Duden_Korrektor
- python extensions need to work with python 3.3 (python3-uno is default,
python-uno is just fallback and debian-only for compatibility)
so you need to have a look at what you install anyway)
Regards,
Rene
Reply to: