Red Hat Bugzilla – Bug 164468
unable to support lsb-celestia and lsb-xpaint
Last modified: 2014-03-25 20:52:33 EDT
Description of problem:
We have experienced the following error (see additional info) while trying to
test lsb-celestia. Confirmed on both ia64 and x86_64 arch.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
See additional info
[root@superman lsb3]# rpm -Uvh lsb-celestia-1.3.2-1.lsb3.x86_64.rpm
warning: lsb-celestia-1.3.2-1.lsb3.x86_64.rpm: V3 DSA signature: NOKEY, key ID
error: Failed dependencies:
lsb-graphics-amd64 >= 3.0 is needed by lsb-celestia-1.3.2-1.lsb3.x86_64
http://www.linuxbase.org/LSBWiki/ReleaseNotes3 under the Package Manager Section
The packaging system on an LSB 3 conforming system must supply four version
dependencies which packages may require. There are two architecture neutral
ones, lsb-core-noarch and lsb-graphics-noarch, as well as two
architecture-specific ones, lsb-core-arch and lsb-graphics-arch. These must be
providing the value 3.0.
In addition, the Release Note also mentioned that lsb_release command under
redhat-lsb should achieve the following:
The lsb_release command on an LSB 3 conforming system must supply four version
dependencies which may be checked by shell commands (calling lsb_release -v).
There are two architecture neutral ones, core-3.0-noarch and
graphics-3.0-noarch, as well as two architecture-specific ones, core-3.0-arch
An example output will be:
$ lsb_release -v
LSB Version: core-3.0-ia64:core-3.0-noarch:graphics-3.0-ia64:graphics-3.0-noarch
Actual Result on our system:
# lsb_release -v
LSB Version: 3.0
Moving this to RHEL4U2Proposed. This is needed for LSB3 conformance. Devel ack
Tested with redhat-lsb-3.0-5.EL.x86_64.rpm against lsb-celestia. Confirmed bug
has been fixed.
Change back to ASSIGNED to get ack.
Latest redhat-lsb-3.0-6.EL has the fix.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.