Bug #1490906 “intltool-update spits warnings with Perl 5.22 (whi...” : Bugs : intltool (original) (raw)

The issue has been identified while building gramps 4.20, with perl 5.22 installed

The build log yields:
[ 30s] Traceback (most recent call last):
[ 30s] File "setup.py", line 545, in
[ 30s] "Classifier: Topic :: Sociology :: Genealogy",
[ 30s] File "/usr/lib64/python3.4/distutils/core.py", line 148, in setup
[ 30s] dist.run_commands()
[ 30s] File "/usr/lib64/python3.4/distutils/dist.py", line 955, in run_commands
[ 30s] self.run_command(cmd)
[ 30s] File "/usr/lib64/python3.4/distutils/dist.py", line 974, in run_command
[ 30s] cmd_obj.run()
[ 30s] File "setup.py", line 248, in run
[ 30s] build_intl(self)
[ 30s] File "setup.py", line 189, in build_intl
[ 30s] if intltool_version() < (0, 25, 0):
[ 30s] File "setup.py", line 98, in intltool_version
[ 30s] return tuple([int(num) for num in version_str.split('.')])
[ 30s] File "setup.py", line 98, in
[ 30s] return tuple([int(num) for num in version_str.split('.')])
[ 30s] ValueError: invalid literal for int() with base 10: 'Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/^('
[ 30s] error: Bad exit status from /var/tmp/rpm-tmp.B8qgMp (%build)

The issue here is that gramps' setup.py uses the output of intltool-updates directly (in a non-safe way)... but the underlying issue is actually that intltool-update uses deprecated perl regex syntax.

I'm just preparing a patch for this issue as well - so simply lean back and wait :)