Bug 413351
Summary: | yum package for postgresql-libs.x86_64 needs symlink | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chad <chad> |
Component: | postgresql | Assignee: | Tom Lane <tgl> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | hhorak |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-04-25 04:54:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chad
2007-12-06 03:14:09 UTC
That symlink does exist, in the postgresql-devel package, which is where it belongs per longstanding conventions. I think the real problem here is that the slony package you're using fails to BuildRequire postgresql-devel. Please confirm ... grep BuildRequires postgresql-slony1.spec BuildRequires: postgresql-devel, postgresql-server, initscripts Hmm ... well, mere inspection proves that the x86_64 postgresql-devel RPM does contain lrwxrwxrwx 1 root root 12 Feb 14 2007 ./usr/lib64/libpq.so -> libpq.so.5.0 so what I am wondering now is if you have the i386 postgresql-devel RPM installed, but not the other one. If so, seems like this would be an RPM bug or misfeature to accept the wrong-width RPM as satisfying the BuildRequires. toor@lnx1[postgresql-slony1-1.2.12] yum list installed postgresql-devel Installed Packages postgresql-devel.x86_64 8.2.5-1.fc7 installed postgresql-devel.i386 8.2.5-1.fc7 installed toor@lnx1[postgresql-slony1-1.2.12] You should most certainly have /usr/lib64/libpq.so then. What does rpm -V say about those two packages? The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there have not been any updates to the report since thirty (30) days or more since we requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance. Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9. |