FS#36771 - [libreoffice] Duplicate file in libreoffice-en-{GB,US}

Attached to Project: Arch Linux
Opened by Johannes Krampf (wuischke) - Monday, 02 September 2013, 06:55 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 12 October 2013, 14:51 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 10
Private No



When updating libreoffice with its language packes to version 4.1.1-2, I get the following error:

error: failed to commit transaction (conflicting files)
/usr/lib/libreoffice/share/wordbook/en-GB.dic exists in both 'libreoffice-en-GB' and 'libreoffice-en-US'
/usr/lib/libreoffice/share/wordbook/en-US.dic exists in both 'libreoffice-en-GB' and 'libreoffice-en-US'

Additional info:
* package version(s) libreoffice-en-GB-4.1.1-1 libreoffice-en-US-4.1.1-2
* config and/or log files etc.

Steps to reproduce:

Have libreoffice with both of these language packs installed and try to upgrade to version 4.1.1-2.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 12 October 2013, 14:51 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in -common and -i18n 4.1.2-2
Comment by Andreas Radke (AndyRTR) - Monday, 02 September 2013, 08:04 GMT
this is how upstream ships the langpacks. discuss this upstream if you think it should be changed.

both dictionaries are part of all three langpacks: en-GB, en-US and en-ZA.

I tend to say not a bug as not many users will install two different english langpacks.
Comment by Johannes Krampf (wuischke) - Tuesday, 03 September 2013, 08:48 GMT
In this case I think that the three packages should conflict so that pacman can handle the situation correctly.

BTW: Thanks for the work packaging Libreoffice!
Comment by CalimeroTeknik (Calimero) - Friday, 13 September 2013, 15:08 GMT
Or maybe put this file in a separate package the others can depend on?
I'm using differentiated US and UK English, here. (depending on whether the recipient is from the US or UK, obviously)
Comment by Vasili (3point2) - Sunday, 15 September 2013, 20:49 GMT
i also ran into this. i agree that something should be done so that pacman handles this better. either the packages should conflict or the duplicate file should be in another package that they depend on.
Comment by Ng Oon-Ee (ngoonee) - Monday, 16 September 2013, 00:10 GMT
This is a duplicate (not in title, but in essence) of my bug #36732.
Comment by Andreas Radke (AndyRTR) - Sunday, 22 September 2013, 18:03 GMT
If you don't bring this to an upstream solution things won't change.

4.1.2 is right around the corner and if I don't see any upstream statement about this I won't change the upstream RPM langpacks.
Comment by J. Berger (jmb) - Sunday, 22 September 2013, 18:37 GMT
Actually, that is *not* how upstream ships the langpacks. Each langpack is split into several rpms, then to facilitate downloads, all rpms needed for a given language are grouped together in a single tarball. However, some of those rpms are present in several tarballs. This makes it easier to users who want to download a language, since they are sure to get all needed packages at once and since rpm will do the right thing if the user tries to install the same package more than once (pacman would do the right thing too if there was a one-on-on mapping between arch package and rpm file).

In the specific case of the english variants, there is a libreoffice4.1-dict-en-${version}.rpm which contains the files common to all variants, then there are libreoffice4.1-en-{GB,ZA}-${version}.rpm for the files specific to each variant.

The issue comes from the way the arch packages group several rpms into a single arch package, if the arch packages followed the upstream packages there would be no issue.
Comment by Doug Newgard (Scimmia) - Sunday, 29 September 2013, 20:25 GMT
Edit: Sorry, I was looking at the en-US language pack only, not the others.
Comment by Andreas Radke (AndyRTR) - Monday, 30 September 2013, 14:55 GMT
Sorry guys. I don't have much time these days and a new LibO release is pretty near.

Please tell me what changes are required to get proper english support back. Best would to not split LibO any further if not needed.
Comment by t-ask (tAsk) - Thursday, 03 October 2013, 14:51 GMT
The same error message here. I hope this will change with the next upgrade. Any idea how to fix this temporarily?

Edit: I removed one package with "pacman -R libreoffice-en-US" and no more error message is popping up.