Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 231357 - ParseConfig is an undefined subroutine
ParseConfig is an undefined subroutine
Product: Fedora
Classification: Fedora
Component: perl-Config-General (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ville Skyttä
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-03-07 15:50 EST by Emmanuel Seyman
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-07 17:38:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Emmanuel Seyman 2007-03-07 15:50:05 EST
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:

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 17:38:48 EST
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

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.