Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#66295 - [awstats] Syntax error in mime.pm
Attached to Project:
Community Packages
Opened by Olivier Boudeville (Wondersye) - Saturday, 18 April 2020, 15:00 GMT
Last edited by Sergej Pupykin (sergej) - Saturday, 18 April 2020, 19:55 GMT
Opened by Olivier Boudeville (Wondersye) - Saturday, 18 April 2020, 15:00 GMT
Last edited by Sergej Pupykin (sergej) - Saturday, 18 April 2020, 19:55 GMT
|
DetailsHi,
With the current newer version of AWstats in Arch (7.8-1), using awstats.pl results in a (blocking) syntax error: $ /usr/share/webapps/awstats/cgi-bin/awstats.pl -config=foo.bar.org -output String found where operator expected at /usr/share/webapps/awstats/cgi-bin/lib/mime.pm line 60, near "'ebook'" (Missing semicolon on previous line?) syntax error at /usr/share/webapps/awstats/cgi-bin/lib/mime.pm line 60, near "'ebook'" Compilation failed in require at /usr/share/webapps/awstats/cgi-bin/awstats.pl line 2239. whereas downgrading to previous Arch version 7.7-1 generates a correct HTML report. |
This task depends upon
I tried awstats 7.8 (build 20200416); the previous error seems to have disappeared, at least I could not reproduce it with this new version.
I noticed a change of behaviour: we used to be able to specify the configuration file as a path (rather than as a name), like in:
/usr/share/webapps/awstats/cgi-bin/awstats.pl -config=/var/local/foobar.conf -output -staticlinks
It used to work (although with a few errors in the generated links in the report page) but now the command generates an error page ("Couldn't open config file").
I guess it is an upstream change so I think we can close the current issue.
Thanks for your kind update!
Best regards,
Olivier.