Strange .po files in KF5 branch without .pot files

[Łukasz Wojniłowicz]

On Sun, 23 Jul 2023 15:42:16 +0200
Albert Astals Cid <aacid at kde.org> wrote:

> El diumenge, 23 de juliol de 2023, a les 13:41:37 (CEST), Freek de
> Kruijf va escriure:
> > Op zaterdag 22 juli 2023 23:02:27 CEST schreef Albert Astals Cid:  
> > > El dissabte, 22 de juliol de 2023, a les 22:54:08 (CEST), Albert
> > > Astals Cid  
> > 
> > va escriure:  
> > > Did you not do that on purpose?
> > > 
> > > Have you updated your lokalize recently maybe?  
> > 
> > Yes, I work with openSUSE Tumbleweed, which means always the newest
> > available.
> > 
> > There is an option in lokalize to make changes in trunk which get
> > copied in branch as well. Apparently this works wrongly. It should
> > only work when branch does have the equivalent template and the
> > element in the template in branch is the same in template in trunk.
> > I will change the configuration in the project file for trunk and
> > remove the reference to branch.  
> 
> 
> Łukasz can you investigate this? 
> 
> It could be related to your change in 
> https://invent.kde.org/sdk/lokalize/-/merge_requests/25
> 
> Cheers,
>   Albert

Hi Albert, yes it seems to be related to my change, but I don't know
yet how.

@Freek de Kruijf
I need more information about your setup:
1) Is there any bug report opened already? If not, it would be good to
do it.
2) Could you post your project file(s) from Lokalize? The one that you
open through the menu Project->Open project.
3) Do you use PO summit?
https://techbase.kde.org/Localization/Workflows/PO_Summit
4) Do those strange .po files in KF5 branch keeps reappearing to you, or
was it only a single occurrence?
5) Are your .po and .pot files stored on a network storage?
6) Is there any symlink directory anywhere in the path to your your
.po and .pot files?

In general, my change uses BranchDir and PotBaseDir to figure out if
respective .pot file in a branch exists and has no .po file, before it
creates the .po file. Code before me only looked for the .po file, and
if it didn't exist, it did nothing.

The code must have returned positive for the .pot
file because otherwise I pass an empty path to the .po creating function
which already accepted that path earlier, and haven't done anything
spurious.