Bug 112278 - perl-DBD-Pg install in wrong directory
perl-DBD-Pg install in wrong directory
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: perl-DBD-Pg (Show other bugs)
1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Chip Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-12-16 18:39 EST by Stephen Walton
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-12-16 18:43:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stephen Walton 2003-12-16 18:39:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
The Fedora perl-DBD-Pg installs Pg.pm in
/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/DBD/ but perl
5.8.1 doesn't look there for its files.

Version-Release number of selected component (if applicable):
perl-DBD-Pg-1.22-1

How reproducible:
Always

Steps to Reproduce:
1. Create a one-line file t.pl containing:

require "Pg.pm";

2.  Type "perl t.pl" at a shell prompt.

    

Actual Results:  Can't locate Pg.pm in @INC (@INC contains:
/usr/lib/perl5/5.8.1/i386-linux-thread-multi /usr/lib/perl5/5.8.1
/usr/lib/perl5/site_perl/5.8.1/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.1
/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl
/usr/lib/perl5/5.8.1/i386-linux-thread-multi /usr/lib/perl5/5.8.1 .)
at t.pl line 1.


Expected Results:  Pg.pm should have been found.

Additional info:
Comment 1 Stephen Walton 2003-12-16 18:43:33 EST
OK, never mind, the interface has changed.  Time to rewrite some code,
sigh.

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