Bug 40167 - dh-umc-module-build created invalid .po files with duplicate entries
dh-umc-module-build created invalid .po files with duplicate entries
Status: RESOLVED DUPLICATE of bug 40341
Product: UCS
Classification: Unclassified
Component: UMC (Generic)
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1-x
Assigned To: UMC maintainers
:
Depends on: 40164 40165
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-03 14:58 CET by Philipp Hahn
Modified: 2016-01-14 11:16 CET (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments
Don't create duplicate entries (1.48 KB, text/plain)
2015-12-03 14:58 CET, Philipp Hahn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2015-12-03 14:58:11 CET
Created attachment 7343 [details]
Don't create duplicate entries

uvmmd provided two umc/*.xml files with the same texts, which are added two times to the temporary messages.po files; `msgmerge` then fails:

*** MODULE={'Icons': 'umc/icons', 'Definition': 'umc/uvmm.xml', 'package': 'univention-management-console-module-uvmm', 'Python': 'umc/python', 'Javascript': 'umc/js', 'Module': 'uvmm'} XML
        msgmerge --update --sort-output umc/de.po umc/messages.po
umc/messages.po:21: duplicate message definition...
umc/messages.po:16: ...this is the location of the first definition
umc/messages.po:24: duplicate message definition...
umc/messages.po:19: ...this is the location of the first definition
msgmerge: found 2 fatal errors

+++ This bug was initially created as a clone of Bug #40165 +++
+++ This bug was initially created as a clone of Bug #40164 +++
Comment 1 Florian Best univentionstaff 2016-01-14 11:16:31 CET
This has been fixed at Bug #40341.

*** This bug has been marked as a duplicate of bug 40341 ***