Bug 92107 - Missing file in postgresql-libs
Summary: Missing file in postgresql-libs
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: postgresql
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Andrew Overholt
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-02 19:08 UTC by John Gorman
Modified: 2007-04-18 16:54 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-06-02 20:00:29 UTC
Embargoed:


Attachments (Terms of Use)

Description John Gorman 2003-06-02 19:08:40 UTC
Description of problem:

Missing file /usr/lib/libpq.so.2.0 from postgresql-libs package.

Version-Release number of selected component (if applicable):

postgresql-libs-7.3.2-3.i386.rpm

How reproducible:

Easy

Steps to Reproduce:

1. rpm -i postgresql-libs-7.3.2-3.i386.rpm
2. rpm -V postgresql-libs
    
Actual results:

missing    /usr/lib/libpq.so.2.0

Expected results:


Additional info:

Comment 1 Andrew Overholt 2003-06-02 20:00:29 UTC
libpq.so.2 is for PostgreSQL <= 7.2.  PostgreSQL >= 7.3 uses libpq.so.3
(provided with the 7.3 packages).  If you need the older library, install
postgresql72-libs (available via up2date).

Comment 2 Damian Menscher 2003-08-04 02:00:50 UTC
Maybe I'm dumb, but why does the RPM think it has the file, when it doesn't?  I 
can understand having a different RPM provide the file, but having postsql-libs 
*think* it provides it when it doesn't seems wrong.

Comment 3 Andrew Overholt 2003-08-05 19:28:19 UTC
I don't understand what you're asking.

Comment 4 Damian Menscher 2003-08-07 05:34:08 UTC
The RPM tells the database that it is installing /usr/lib/libpq.so.2.0, but it
doesn't install that file.  Therefore when checking that installed files match
what's in the database, it comes up as missing.

We're not complaining that the file is NOT installed, since that's the correct
behavior (since it's provided by another package).  The bug is that the database
thinks the file HAS been installed.

Hopefully this is more clear?


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