Bug 231357

Summary:	ParseConfig is an undefined subroutine
Product:	[Fedora] Fedora	Reporter:	Emmanuel Seyman <emmanuel>
Component:	perl-Config-General	Assignee:	Ville Skyttä <ville.skytta>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6	CC:	perl-devel
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-03-07 22:38:48 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:

Description Emmanuel Seyman 2007-03-07 20:50:05 UTC

Description of problem:

When using the Config::Genral module, ParseConfig() cannot be used and the
script dies with the message :

Undefined subroutine &main::ParseConfig called at pc line 2.

Version-Release number of selected component (if applicable):
2.32-1.fc6 (Fedora 6 with all updates)

How reproducible:
Always

Steps to Reproduce:
1. Create an empty rcfile
2. Run the command : perl -MConfig::General -e 'ParseConfig("rcfile")'

Actual results:
Undefined subroutine &main::ParseConfig called at -e line 1.

Expected results:
Perl should run the command and return to the shell prompt

Comment 1 Ville Skyttä 2007-03-07 22:38:48 UTC

From upstream ChangeLog:

          o the functions ParseConfig SaveConfig SaveConfigString must
            now imported implicitly. This might break existing code, but
            is easily to fix.

So with 2.32, one needs to do something like "use Config::General
qw(ParseConfig) ; ParseConfig(...)", or perl -MConfig::General=ParseConfig -e
'ParseConfig(...)'.  

In retrospect, maybe it was a mistake to push this update to older releases than
the current development repository, but it's in now and like the changelog says,
it's an easy one to fix - sorry if it caused problems.  FWIW, I looked through
the dependent Fedora packages and didn't see anything affected before pushing
the update.