Bug 235991 - no postgresql-libs.i386 dependency
no postgresql-libs.i386 dependency
Product: Fedora
Classification: Fedora
Component: subversion (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
Depends On:
  Show dependency treegraph
Reported: 2007-04-11 06:53 EDT by Enrico Scantamburlo
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-11 10:41:04 EDT
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 Enrico Scantamburlo 2007-04-11 06:53:22 EDT
Description of problem:
Subversion depends on postgresql-libs.i386 but this dependency is not in the rpm 

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

How reproducible:
remove postgresql-libs.i386 and run subversion

Steps to Reproduce:
1. rpm -e postgresql-libs.i386 
2. svn status -u
Actual results:
svn: error while loading shared libraries: libpq.so.4: cannot open shared object
 file: No such file or directory

Expected results:
Alla revisione 3575

Additional info:
Comment 1 Joe Orton 2007-04-11 09:22:38 EDT
The dependency is from apr-util; did you use --nodeps with any erase operation?
This should not be possible otherwise.

# rpm --erase postgresql-libs
error: Failed dependencies:
        libpq.so.4 is needed by (installed) apr-util-1.2.7-3.i386

What is the output of:

# rpm -V apr-util subversion
# rpm -q --whatprovides libpq.so.4
# rpm -q --whatrequires libpq.so.4

Comment 2 Enrico Scantamburlo 2007-04-11 10:37:45 EDT
I used yum to remove postgresql-libs.i386 

[root@scantamburlo enrico]# rpm -V apr-util subversion
[root@scantamburlo enrico]# rpm -q --whatprovides libpq.so.4
[root@scantamburlo enrico]# rpm -q --whatrequires libpq.so.4
Comment 3 Enrico Scantamburlo 2007-04-11 10:41:04 EDT
Sorry I think it'a a problem with the latest Yum. 

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