openstack i18n

a warning of "awk" for generatepot jobs

Bug #2035226 reported by Ian Y. Choi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack i18n
Confirmed
Undecided
Unassigned

Bug Description

Currently, it shows a warning message for pot generation jobs.

For example, result of "$ tox -e generatepot" for openstack/i18n repository is like:

+ msgcat --use-first --sort-by-file doc/build/gettext/about.pot doc/build/gettext/atc-stats.pot doc/build/gettext/bug_report.pot doc/build/gettext/check_translation.pot doc/build/gettext/contributing.pot doc/build/gettext/glossary.pot doc/build/gettext/handling_bugs.pot doc/build/gettext/i18n_team_meeting.pot doc/build/gettext/index.pot doc/build/gettext/infra-debug.pot doc/build/gettext/infra.pot doc/build/gettext/lang_team.pot doc/build/gettext/official_translator.pot doc/build/gettext/project_setup.pot doc/build/gettext/ptl.pot doc/build/gettext/release_management.pot doc/build/gettext/reviewing-translation-import.pot doc/build/gettext/tools.pot doc/build/gettext/translation_stats.pot doc/build/gettext/translation_tips.pot
+ awk '$0 !~ /^\# [a-z0-9]+$/'
awk: cmd. line:1: warning: regexp escape sequence `\#' is not a known regexp operator

More information: https://review.opendev.org/c/openstack/i18n/+/894512

Ian Y. Choi (ianychoi)
Changed in openstack-i18n:
status: New → Confirmed
Revision history for this message
Akihiro Motoki (amotoki) wrote :

Ubuntu 20.04 or later hits this. Ubuntu 18.04 used in upstream-translation-update job does not hit this.

The detail is quoted from https://review.opendev.org/c/openstack/i18n/+/894512
---
(g)awk in Ubuntu 20.04 or later (perhaps gawk >=5.0) has more strict
regexp check and the regexp passed to awk in generatepot.sh cannot
pass the regexp check. This means our script does not work on
Ubuntu 20.04 or later.
---

Revision history for this message
Akihiro Motoki (amotoki) wrote :

More details is found in Ian and my comments in the i18n review [0]. I will add the summary here.

After checking the history of the UUID filtering, it was introduced in [1] when our CI uses sphinx <1.3 and was copied to the related scripts. sphinx >=1.3 no longer adds UUID per string by default (in gettext_uuid option [2]) and our CI does not enable this option, so we can safely drop the UUID filtering.

[0] https://review.opendev.org/c/openstack/i18n/+/894512
[1] https://opendev.org/openstack/openstack-manuals/commit/993647f316fbe33a513baffb5cc4ad156355da8a
[2] https://www.sphinx-doc.org/en/master/usage/configuration.html#confval-gettext_uuid

Revision history for this message
Akihiro Motoki (amotoki) wrote :

I proposed patches to drop UUID filtering to the related repositories.
You can find them with a topic named as "bug/2035226".

https://review.opendev.org/q/topic:bug%252F2035226

- openstack-manuals
- security-guides
- training-guides
- openstack-zuul-jobs

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.