Bug 1013896

Summary:	logconv warning - Use of comma-less variable list is deprecated at /usr/bin/logconv.pl line 630
Product:	Red Hat Enterprise Linux 7	Reporter:	Nathan Kinder <nkinder>
Component:	389-ds-base	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Sankar Ramalingam <sramling>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	jgalipea, mreynolds, nkinder, rmeggins
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.3.1.6-5.el7	Doc Type:	Bug Fix
Doc Text:	Cause: logconv.pl uses comma-less print formatting Consequence: In newer version of Perl this is deprecated. Fix: Use commas in print formatting. Result: logconv.pl runs without warnings, and is compliant with the latest standard.	Story Points:	---
Clone Of:	1013162	Environment:
Last Closed:	2014-06-13 09:17:31 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1013162
Bug Blocks:

Description Nathan Kinder 2013-10-01 02:18:04 UTC

+++ This bug was initially created as a clone of Bug #1013162 +++

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47461

Use of comma-less variable list is deprecated at /usr/bin/logconv.pl line 630

Comment 2 Sankar Ramalingam 2014-01-18 01:20:09 UTC

Request you to provide steps to verify bugzilla.

Comment 3 mreynolds 2014-01-20 15:10:35 UTC

(In reply to Sankar Ramalingam from comment #2)
> Request you to provide steps to verify bugzilla.

This was actually just a coding style change.  It has no impact on the output or script functionality.  There is nothing to verify for this one.

Comment 4 Sankar Ramalingam 2014-01-30 09:58:26 UTC

Marking it as Verified as per Mark's comment.

Comment 5 Ludek Smid 2014-06-13 09:17:31 UTC

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.