[pology] Pology posummit not propagating header changes to branch PO files

[Karl Ove Hufthammer]

I’m having some problems with header changes in the summit files not 
being propagated to the branches. If the summit PO file doesn’t contain 
any string changes, any header changes are not being applied to the 
branch files, even with ‘--force’.

Here’s a reproducible example based on the KDE translations
(svn+ssh://svn@svn.kde.org/home/kde/ and subfolders).
The ‘nb’ translations uses local merging, so running
posummit with the ‘--force merge,scatter’
*should* (basically) result in branch PO files being completely regenerated.

When I’m in the folder trunk/l10n-support and run

posummit --force scripts/messages.summit nb merge,scatter 
nb/summit/messages/falkon/falkon_statusbaricons_qt.po

*nothing* is changed in the file
branches/stable/l10n-kf5/nb/messages/falkon/falkon_statusbaricons_qt.po

However, if I delete the branch PO file and rerun the command, the file 
is regenerated, but with some changes. It now contains a 
PO-Revision-Date and a Last-Translator header (taken from the summit PO 
file), and one of the strings have a different formatting (different 
line breaks). This is the *expected* result from the original command.

And if I don’t delete the branch PO file, but change one of the 
non-header summit strings, this change is scattered to the branch file 
*and* the headers are updated.

So I think the problem only occurs when all non-header strings are 
identical in the summit and in the branch.

Note that the branch PO file originally didn’t contain the two headers 
at all. But the same thing happens with other files in falkon folder, 
also with files that already contain the headers. One example is 
falkon_qt.po, which has an *updated* Last-Translator
header in the summit file, which is not being scattered to the l10n-kf5 
branch.

I think this is a bug in Pology. The branch headers should reflect the 
summit headers.


-- 
Karl Ove Hufthammer