Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Can a dev please have a look at resolving the 3.6.1.x and 3.5.6.x debian
installs? Both break dpkg on both 32bit and 64bit systems and make it
impossible to install either with the included dict packages.


My post on the user list:

3.6.1 dictionary installs (.deb) fail & bork dpkg/apt-get

Yesterday in the 'Update to 3.6.1' thread I installed 3.6.1 (debian
files) on 32bit and 64bit systems. Both experienced installations errors:

<http://pastebin.com/3aKwSYP1>
Errors were encountered while processing:
 libreoffice3.6-dict-en_3.6.1.2-2_amd64.deb
 libreoffice3.6-dict-es_3.6.1.2-2_amd64.deb
 libreoffice3.6-dict-fr_3.6.1.2-2_amd64.deb
(and on 32bit deb as well).

To make things worse, when attempting to update an Opera browser today I
found out that the above were completely broken & couldn't be purged in
any normal fashion. Went searching and came across this bug reports:

https://bugs.freedesktop.org/show_bug.cgi?id=54202 - open
[Error while installing Dutch Linux Deb (x64) main installer with
command dpkg -i *]
https://bugs.freedesktop.org/show_bug.cgi?id=41290 - closed as dupe of 41237
[dictionaries do not install in daily builds as of 28/9/2011]
https://bugs.freedesktop.org/show_bug.cgi?id=41237 - closed
[Installation of dictionaries failed with
""/singletons/com.sun.star.deployment.ExtensionManager": loading
component library failed""]

I was finally able to clean my systems (see:
https://bugs.freedesktop.org/show_bug.cgi?id=54202#c3 ), but still have
not been able to install the dictionaries. I may have found the problem:
<https://bugs.freedesktop.org/show_bug.cgi?id=54202#c5>

$ debdiff libreoffice3.6-dict-en_3.6.0.4-104_i386.deb
libreoffice3.6-dict-en_3.6.1.2-2_i386.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in first .deb but not in second
-------------------------------------
-rwxr-xr-x  root/root   DEBIAN/postinst
-rwxr-xr-x  root/root   DEBIAN/postrm

Control files: lines which differ (wdiff format)
------------------------------------------------
Installed-Size: [-26208-] {+26224+}
Version: [-3.6.0.4-104-] {+3.6.1.2-2+}

Has anyone else experience the same issue with the .deb install?

I've just tested by backing down to 3.6.0.4 & 3.5.5:

No issues with reinstalling 3.6.04 over 3.6.1:
Setting up libreoffice3.6-dict-en (3.6.0.4-104) ...
SUCCESS: unopkg returns successful!
Setting up libreoffice3.6-dict-es (3.6.0.4-104) ...
SUCCESS: unopkg returns successful!
Setting up libreoffice3.6-dict-fr (3.6.0.4-104) ...
SUCCESS: unopkg returns successful!

Breaks dpkg with 3.6.1.1:
Processing triggers for menu ...
Errors were encountered while processing:
 libreoffice3.6-dict-en_3.6.1.1-1_i386.deb
 libreoffice3.6-dict-es_3.6.1.1-1_i386.deb
 libreoffice3.6-dict-fr_3.6.1.1-1_i386.deb

And as with 3.6.1.2:
$ debdiff libreoffice3.6-dict-en_3.6.0.4-104_i386.deb
libreoffice3.6-dict-en_3.6.1.1-1_i386.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in first .deb but not in second
-------------------------------------
-rwxr-xr-x  root/root   DEBIAN/postinst
-rwxr-xr-x  root/root   DEBIAN/postrm

Control files: lines which differ (wdiff format)
------------------------------------------------
Installed-Size: [-26208-] {+26220+}
Version: [-3.6.0.4-104-] {+3.6.1.1-1+}

Nor did I have any issues with installing 3.5.5rc3 over 3.5.6.2.


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.