Bug 81411 - perl-5.8.0-82 RPM doesn't know that it provides libperl.so
perl-5.8.0-82 RPM doesn't know that it provides libperl.so
Status: CLOSED RAWHIDE
Product: Red Hat Raw Hide
Classification: Retired
Component: perl (Show other bugs)
1.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chip Turner
David Lawrence
:
Depends On:
Blocks: 79578
  Show dependency treegraph
 
Reported: 2003-01-09 00:38 EST by Jonathan Kamens
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-02-10 09:41:50 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 Jonathan Kamens 2003-01-09 00:38:49 EST
jik:/usr/src/packages/new!351> rpm -Uvh --test *
...
        libperl.so is needed by inn-2.3.3-10
        libperl.so is needed by mod_perl-1.99_07-2
        libperl.so is needed by perl-5.8.0-82
...
    Suggested resolutions:
...
        perl-5.8.0-73.i386.rpm
Comment 1 Nicolas Mailhot 2003-01-10 06:36:51 EST
Same here :

[root@ulysse RPMS]# rpm -Fvh *rpm
warning: 4Suite-0.11.1-11.i386.rpm: V3 DSA signature: NOKEY, key ID 897da07a
error: Failed dependencies:
        libperl.so is needed by perl-5.8.0-82
        libperl.so is needed by (installed) mod_perl-1.99_07-2
        libperl.so is needed by (installed) vim-enhanced-6.1-22
        libperl.so is needed by (installed) vim-X11-6.1-22
        libperl.so is needed by (installed) xchat-1.8.11-2
Comment 2 Sammy 2003-01-10 09:17:52 EST
I can confirm this as well as some other rpms which are giving the same kind 
of error! 
Comment 3 Chip Turner 2003-02-08 16:12:39 EST
-85 should now properly provide libperl.so; this was a transient build issue and
has been repaired
Comment 4 Jay Turner 2003-02-10 09:41:50 EST
perl-5.8.0-85 does indeed provide libperl.so now.  Closing out.

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