Bug 770278 - rhel6/vnc-server depends includes kernel
Summary: rhel6/vnc-server depends includes kernel
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libdrm
Version: 6.4
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Dave Airlie
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-25 14:20 UTC by gregrwm
Modified: 2017-12-06 10:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:20:19 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description gregrwm 2011-12-25 14:20:10 UTC
Description of problem:
rhel6/vnc-server has a dependency chain which is linked all the way to the kernel.  this makes it unwieldy for a chroot.  this wasn't a problem with rhel5/vnc-server.  so this is another issue keeping us using rhel5.

Version-Release number of selected component (if applicable):
tigervnc-server-1.0.90-0.17.20110314svn4359.el6.x86_64

Steps to Reproduce:
1.  use yum --installroot to install vnc-server in a chroot.
2.  you get kernel too
3.  doesn't happen in rhel5

Comment 2 Adam Tkac 2012-01-02 11:30:43 UTC
tigervnc-server doesn't depend on kernel. However it depends on mesa-dri-drivers which depends on libdrm which depends on kernel.

Reassigning to libdrm for further inspection.

Comment 3 Dave Airlie 2012-01-03 10:47:19 UTC
We can probably drop the libdrm kernel requirement in RHEL6.3, so we should propose this for it.

Comment 5 Suzanne Logcher 2012-02-14 23:25:36 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 6 Dave Airlie 2012-02-15 10:22:36 UTC
this is a trivial fix to the spec file, I'm suggesting it for fast track, not 100% sure this is correct way to do that.

Comment 7 Vadym Chepkov 2012-03-04 18:35:20 UTC
libdrm specfile has 

Requires: kernel >= 2.6.29.1-52.fc11

I think it should be changed to

Conflicts: kernel < 2.6.29.1-52.fc11

Logic is preserved, but unnecessary components are not pulled during build process either.

Comment 9 RHEL Program Management 2012-07-10 08:55:00 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 10 RHEL Program Management 2012-07-11 00:00:55 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 15 gregrwm 2012-11-29 12:40:03 UTC
vadym's suggestion seems sound and worthwhile, or indeed even dropping the kernel requirement

Comment 16 Dave Airlie 2012-11-29 22:08:20 UTC
its already dropped in the 6.4 builds

Comment 17 gregrwm 2012-11-30 07:07:16 UTC
ty!

Comment 18 RHEL Program Management 2012-12-14 08:52:18 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 21 Jan Kurik 2017-12-06 10:20:19 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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