Description of problem: sudo service shorewall startCompiling... Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Config.pm line 3408. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Config.pm line 3613. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Chains.pm line 1532. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Chains.pm line 1536. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Chains.pm line 1540. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Chains.pm line 1544. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Chains.pm line 1549. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Chains.pm line 1575. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Chains.pm line 1579. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Chains.pm line 1583. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Chains.pm line 1587. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Chains.pm line 4715. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Rules.pm line 459. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Misc.pm line 1667. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Compiler.pm line 111. Use of qw(...) as parentheses is deprecated at /usr/share/shorewall/Shorewall/Compiler.pm line 119.
Priority: Normal => High
Thanks Ahmad for updating shorewall to 4.4.20.2. But the error / warning (?) reportedd remains. Is this because Mageia is ahead of shorewall providing perl's version? Is it only a warning that shorewall should soon get it's act together and harmless? or? Thanks beforehand!
(In reply to comment #1) > Thanks Ahmad for updating shorewall to 4.4.20.2. > > But the error / warning (?) reportedd remains. Is this because Mageia is ahead > of shorewall providing perl's version? Is it only a warning that shorewall > should soon get it's act together and harmless? or? > Yes, shorewall upstream will have to adapt the code. I am not sure, but I think it's harmless warning, still a bug should be filed upstream.
Priority: High => NormalSeverity: major => normal
I'll do what I can.
Posted a question to shorewall-devel, see: http://blog.gmane.org/gmane.comp.security.shorewall.devel and waiting for feedback. If no replies in a reasonable time, I'll register at shorewall.net & post a ticket on their trac.
Keywords: (none) => NEEDINFOAssignee: bugsquad => dvgevers
Created attachment 559 [details] Tom Eastep provided patch Tom's comment: ... Yes -- it is a harmless(but annoying) warning from the Perl compiler. ... Ahmad: would you please rebuild and close present? Thanks!
BTW: the patch is approved
Keywords: NEEDINFO => (none)Assignee: dvgevers => bugsquad
For the sake of good order, quoting Tom Eastep: cd /usr/share/shorewall/Shorewall patch < .../QW.patch
Keywords: (none) => PATCHSource RPM: shorewall-4.4.19.1-3.mga1 => shorewall-4.4.20.2-1.mga2
The patch has been applied. Thanks!
Status: NEW => RESOLVEDResolution: (none) => FIXED