Bug 771779 - Numerous Use of qw(...) as parentheses is deprecated messages
Summary: Numerous Use of qw(...) as parentheses is deprecated messages
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: psad
Version: 16
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Peter Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-04 22:50 UTC by Frank Crawford
Modified: 2013-02-14 03:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-14 03:03:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Frank Crawford 2012-01-04 22:50:00 UTC
Description of problem:
Due to a change in perl syntax for Perl 5.14 and onwards, the use of qw(...) in specific contexts is now disallowed.  This generates lots of messages of the form:
Use of qw(...) as parentheses is deprecated at /usr/sbin/psad line 4264.

Version-Release number of selected component (if applicable):
psad-2.1.7-2.fc15.x86_64
perl-5.14.2-191.fc16.x86_64

How reproducible:
100% of time

Steps to Reproduce:
1. Run "psad --help" or any other psad options.
2.
3.
  
Actual results:
Numerous messages about deprecated feature.

Expected results:
No deprecated messages

Additional info:
Reading some of the perl list this only occurs in statements of the form:
for my $var qw(...) { ... }
and is fixed by the addition of "()", i.e.
for my $var (qw(...)) { ... }

Comment 1 Šimon Lukašík 2012-02-07 11:36:16 UTC
This has been fixed in upstream e013ca6230a6210ac6e405da08df370fb4818831.

It might be included in the upcoming psad-3.0 release.

Comment 2 Fedora Update System 2012-02-13 10:05:29 UTC
psad-2.1.7-5.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/psad-2.1.7-5.fc16

Comment 3 Fedora Update System 2012-02-14 09:07:09 UTC
Package psad-2.1.7-5.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing psad-2.1.7-5.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-1625/psad-2.1.7-5.fc16
then log in and leave karma (feedback).

Comment 4 Fedora End Of Life 2013-01-17 02:13:39 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-14 03:03:24 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.