itstool 2.0.7 vs [packages/mate-utils] up to 1.26.1

[Jan Palus]

On 10.05.2023 17:58, Jakub Bogusz wrote:
> On Wed, May 10, 2023 at 10:07:32AM +0200, atler wrote:
> > commit 8aa16867d2911b7b77adf7d0041e2b455f560fc9
> > Author: Jan Palus <atler at pld-linux.org>
> > Date:   Wed May 10 10:07:19 2023 +0200
> > 
> >     up to 1.26.1
> > 
> >  mate-utils.spec | 4 ++--
> 
> It (usually) fails for me with itstool 2.0.7. With itstool 2.0.6 it succeeded.
> 
> 
> ```
> if ! test -d "pt/"; then mkdir "pt/"; fi
> if test -d "C"; then d="../"; else d="/home/comp/rpm/BUILD/mate-utils-1.26.1/gsearchtool/help/"; fi; \
> mo="pt/pt.mo"; \
> if test -f "${mo}"; then mo="../${mo}"; else mo="/home/comp/rpm/BUILD/mate-utils-1.26.1/gsearchtool/help/${mo}"; fi; \
> (cd "pt/" && itstool -m "${mo}" ${d}/C/index.docbook ${d}/C/legal.xml) && \
> touch "pt/pt.stamp"
> Memory fault
> ```
> 
> or
> 
> ```
> if ! test -d "pt/"; then mkdir "pt/"; fi
> if test -d "C"; then d="../"; else d="/home/comp/rpm/BUILD/mate-utils-1.26.1/gsearchtool/help/"; fi; \
> mo="pt/pt.mo"; \
> if test -f "${mo}"; then mo="../${mo}"; else mo="/home/comp/rpm/BUILD/mate-utils-1.26.1/gsearchtool/help/${mo}"; fi; \
> (cd "pt/" && itstool -m "${mo}" ${d}/C/index.docbook ${d}/C/legal.xml) && \
> touch "pt/pt.stamp"
> Traceback (most recent call last):
>   File "/usr/bin/itstool", line 1647, in <module>
>     doc.merge_translations(translations, opts.lang, strict=opts.strict)
>   File "/usr/bin/itstool", line 1016, in merge_translations
>     lcnode.setProp(attr, origlang)
>   File "/usr/lib/python3.10/site-packages/libxml2.py", line 3640, in setProp
>     if ret is None:raise treeError('xmlSetProp() failed')
> libxml2.treeError: xmlSetProp() failed
> ```
> 
> (sometimes it succeeds)

Actually I was seeing the same with itstool 2.0.6 and found multiple
reports about the very issue with main one being (with root cause
somewhat identified dating back to 2.0.4):

https://github.com/itstool/itstool/issues/36

Upgraded to 2.0.7 only because noticed there is a newer version and
sadly none of the changes between 2.0.6 and 2.0.7 seems to either
improve or regress memory issues.