awstats produces regex warnings in version 7.4 with Perl 5.22 on Ubuntu 16.04 LTS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
awstats (Debian) |
Fix Released
|
Unknown
|
|||
awstats (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
The main awstats script triggers the Perl deprecation warnings about unescaped braces in regexes, every time the script is run (which, by default is every 10 minutes, via cron, sending out an email with these).
[Test Case]
1. apt install awstats
2. run '/usr/share/
You should get an error because of a missing config parameter, but if this bug is present, you also get six "Unescaped left brace in regex is deprecated, ..." messages before that.
[Regression Potential]
I don't see any way this could go wrong. The patch is trivial, and is already included upstream and in yakkety.
[Original Description]
> Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\"%{ <-- HERE Referer}i\"/ at /usr/lib/
> Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\"%{ <-- HERE User-Agent}i\"/ at /usr/lib/
> Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/%{ <-- HERE mod_gzip_
> Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/%{ <-- HERE mod_gzip_
> Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/%{ <-- HERE mod_gzip_
> Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\(%{ <-- HERE ratio}n\)/ at /usr/lib/
Those warnings occur whenever we execute awstats and they can easily be fixed by escaping the "{" and "}" at the mentioned lines. In fact awstats 7.5 fixed those lines already itself:
> AWStats Changelog
> -----------------
>
> ***** 7.5 *****
>
> - Compatibility with Perl 5.22
Please consider backporting those fixes, because awstats is most likely executed by cron or such and this produces unnecessary mails with those warnings. Disabling mails on warnings/errors is of course no solution, because one would miss real configuration errors or such this way.
description: | updated |
Changed in awstats (Ubuntu): | |
importance: | Undecided → High |
tags: | added: server-next |
Changed in awstats (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in awstats (Ubuntu Xenial): | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in awstats (Debian): | |
status: | Unknown → Confirmed |
no longer affects: | awstats (Ubuntu Yakkety) |
tags: | removed: server-next |
Changed in awstats (Debian): | |
status: | Confirmed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.