Bug 4378 - /usr/lib/libqt.so in wrong package
Summary: /usr/lib/libqt.so in wrong package
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: qt (Show other bugs)
(Show other bugs)
Version: 6.0
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Preston Brown
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-08-05 19:12 UTC by Pierre Phaneuf
Modified: 2017-05-10 05:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-18 18:04:19 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Pierre Phaneuf 1999-08-05 19:12:04 UTC 
The file /usr/lib/libqt.so is in the wrong package. This
symlink is used only during development, so it should be in
qt-devel.

Including it in the main qt package causes problem when
someone wants to have both Qt 1.x and Qt 2.x side-by-side
(which works perfectly), by installing qt-2.x.rpm instead of
upgrading. This libqt.so file should always point to the
version of the library that correspond with the header files
installed on the system.

Note that the qt RPM in contrib has the same problem, but I
didn't notice the maintainer, maybe he just used your spec
file.
Comment 1 Preston Brown 1999-08-18 18:04:59 UTC 
This will be fixed in the next release of Red Hat Linux (6.1).
Comment 2 openshift-github-bot 2017-05-10 05:47:43 UTC 
Commits pushed to master at https://github.com/openshift/openshift-docs

https://github.com/openshift/openshift-docs/commit/af8f09fa1f76ff8adca42587d963f3d52e6e2fa4
GH-Issue: 4378: Fixing custom route hostname

https://github.com/openshift/openshift-docs/commit/45bc437a7343c28ee1b4641027f417e51ef2e9ba
Merge pull request #4396 from vikram-redhat/master

GH-Issue: 4378: Fixing custom route hostname
Note You need to log in before you can comment on or make changes to this bug.