Bug 1136133 - 4.2.1 hotfix generates invalid pot files with duplicate msgids
Summary: 4.2.1 hotfix generates invalid pot files with duplicate msgids
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 4.2
Assignee: Jeff Fearn 🐞
QA Contact: Ruediger Landmann
URL:
Whiteboard:
: 1133745 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-02 01:57 UTC by Yuko Katabami
Modified: 2014-10-14 03:44 UTC (History)
3 users (show)

Fixed In Version: 4.2.2
Clone Of:
Environment:
Last Closed: 2014-09-16 23:44:45 UTC
Embargoed:

Attachments (Terms of Use)

Description Yuko Katabami 2014-09-02 01:57:46 UTC 
Description of problem:
When running publican update_pot, it generates file(s) containing a number of duplicate msgids.
Zanata push fails as result.

Version-Release number of selected component (if applicable): 4.2.1


How reproducible: 100%


Steps to Reproduce:
1. Go to a book root directory and run "publican update_pot"
2. Check the content of Revision_History.pot file
3. You will see duplicated msgids (with authors' names)

Actual results:
There are a lot of duplicated msgids

Expected results:
There should not be duplicated msgids

Additional info:
Reported to Rudi on IRC.
Comment 2 Ruediger Landmann 2014-09-04 05:17:41 UTC 
Workaround: msguniq can dedupe the msgids:

msguniq test.pot > test_fixed.pot
mv test_fixed.pot test.pot
Comment 3 Jeff Fearn 🐞 2014-09-08 23:03:20 UTC 
To ssh://git.fedorahosted.org/git/publican.git
   41269d0..33eb833  devel -> devel
Comment 4 Ruediger Landmann 2014-09-15 03:58:09 UTC 
Verified on publican-4.2.2-1.fc20.noarch

Duplicate strings in English XML do not create duplicate msgids in the POT.
Comment 5 Jeff Fearn 🐞 2014-09-16 23:44:45 UTC 
Publican 4.2.2 has shipped with a fix for this issue.
Comment 6 Jeff Fearn 🐞 2014-10-14 03:44:28 UTC 
*** Bug 1133745 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.