FS#36732 - [libreoffice] -en-GB file conflict with -common

Attached to Project: Arch Linux
Opened by Ng Oon-Ee (ngoonee) - Thursday, 29 August 2013, 23:58 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 22 September 2013, 18:01 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity Medium
Priority Immediate
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Description:
/usr/lib/libreoffice/share/wordbook/en-GB.dic exists in both 'libreoffice-en-GB' and 'libreoffice-common'
/usr/lib/libreoffice/share/wordbook/en-US.dic exists in both 'libreoffice-en-GB' and 'libreoffice-common'

Additional info:
* package version(s)
4.1.1-1 for both
* config and/or log files etc.


Steps to reproduce:
Just update
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 22 September 2013, 18:01 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#36771 
Comment by Ng Oon-Ee (ngoonee) - Wednesday, 11 September 2013, 17:31 GMT
  • Field changed: Percent Complete (100% → 0%)
libreoffice-en-GB now conflicts with libreoffice-en-US. Both contain en-GB.dic and en-US.dic, which does not look correct.

Unrelated, but why is libreoffice-en-US not of type 'any' when the rest of the language packs are?
Comment by Tuomas Jäntti (qwertypoke) - Sunday, 15 September 2013, 18:17 GMT
My installation was 4.0.4-2 with libreoffice-fi installed. I tried to add libreoffice-en-GB (4.1.1-1) and got the above mentioned conflicts.

I upgraded the whole libreoffice suite and added the English language pack. This succeeded, no conflicts:

# pacman -S libreoffice
# pacman -S libreoffice-fi
# pacman -S libreoffice-en-GB

The problem might be due to different versions of individual libreoffice packets?
Comment by Ng Oon-Ee (ngoonee) - Monday, 16 September 2013, 00:11 GMT
@qwertypoke your problem is not doing full updates, I think. Here the conflict is because of an upstream error (see #36771), if you are able to update it is not the same problem (actually, you don't seem to have a problem).
Comment by Tuomas Jäntti (qwertypoke) - Tuesday, 17 September 2013, 08:38 GMT
Right you are. I did not read the error report carefully enough.
My original problem was a conflict between libreoffice-common and libreoffice-en-GB
This has nothing to do with the issue here nor is a problem :)

Loading...