Bug 714661 - bluez-compat should depend on chkconfig
Summary: bluez-compat should depend on chkconfig
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: bluez
Version: 6.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Bastien Nocera
QA Contact: Ken Benoit
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-20 11:21 UTC by Jan Stodola
Modified: 2017-12-06 11:04 UTC (History)
0 users

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


Attachments (Terms of Use)

Description Jan Stodola 2011-06-20 11:21:32 UTC
Description of problem:
bluez-compat runs '/sbin/chkconfig' in its installation scriplets, but the
package doesn't depend on chkconfig:

[root@hp-dc5800-01 test_rpms]# rpm --nogpg -q --scripts -p rpms/bluez-compat-4.66-1.el6.x86_64.rpm 
postinstall scriptlet (using /bin/sh):
/sbin/chkconfig --add dund
/sbin/chkconfig --add pand
/sbin/chkconfig --add rfcomm
if [ "$1" -ge "1" ]; then
        /sbin/service dund condrestart >/dev/null 2>&1 || :
        /sbin/service pand condrestart >/dev/null 2>&1 || :
        /sbin/service rfcomm condrestart >/dev/null 2>&1 || :
fi
exit 0
preuninstall scriptlet (using /bin/sh):
if [ "$1" = "0" ]; then
        /sbin/service dund stop >/dev/null 2>&1 || :
        /sbin/service pand stop >/dev/null 2>&1 || :
        /sbin/service rfcomm stop >/dev/null 2>&1 || :
        /sbin/chkconfig --del dund
        /sbin/chkconfig --del pand
        /sbin/chkconfig --del rfcomm
fi

[root@hp-dc5800-01 test_rpms]# rpm --nogpg -q --requires -p rpms/bluez-compat-4.66-1.el6.x86_64.rpm | grep chkconfig
[root@hp-dc5800-01 test_rpms]#


It causes error messages in some cases:
...
  Installing : ncurses-libs-5.7-3.20090208.el6.x86_64                10/13 
  Installing : bash-4.1.2-8.el6.x86_64                               11/13 
  Installing : bluez-libs-4.66-1.el6.x86_64                          12/13 
  Installing : bluez-compat-4.66-1.el6.x86_64                        13/13 
/var/tmp/rpm-tmp.O2Ey7K: line 1: /sbin/chkconfig: No such file or directory
/var/tmp/rpm-tmp.O2Ey7K: line 2: /sbin/chkconfig: No such file or directory
/var/tmp/rpm-tmp.O2Ey7K: line 3: /sbin/chkconfig: No such file or directory


Version-Release number of selected component (if applicable):
bluez-compat-4.66-1.el6

How reproducible:
always

Steps to Reproduce:
1. yum --installroot=/root/new_install_root install bluez-compat-4.66-1.el6

Actual results:
errors during installation

Expected results:
bluez-compat depends on chkconfig, no error messages during installation

Comment 1 RHEL Program Management 2011-07-06 01:19:14 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 2 Jan Kurik 2017-12-06 11:04:30 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.