Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 231357 - ParseConfig is an undefined subroutine
Summary: ParseConfig is an undefined subroutine
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Config-General
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ville Skyttä
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-03-07 20:50 UTC by Emmanuel Seyman
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-03-07 22:38:48 UTC


Attachments (Terms of Use)

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.


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