Bug 1283902 - Remove krb5-server dependency on initscripts unless it is needed
Summary: Remove krb5-server dependency on initscripts unless it is needed
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: krb5
Version: 7.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Robbie Harwood
QA Contact: Patrik Kis
Depends On:
Blocks: 1283777
TreeView+ depends on / blocked
Reported: 2015-11-20 08:24 UTC by Jan Pazdziora
Modified: 2016-11-03 20:23 UTC (History)
3 users (show)

Fixed In Version: krb5-1.14.1-3.el7
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2016-11-03 20:23:16 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2591 0 normal SHIPPED_LIVE Low: krb5 security, bug fix, and enhancement update 2016-11-03 12:10:29 UTC

Description Jan Pazdziora 2015-11-20 08:24:50 UTC
Description of problem:

When installing krb5-server in minimal environment like a Docker container, initscripts are pulled in via rpm dependencies, plus another 4.5+ MB worth of dependencies.

It seems to be needed because of the

[ -x /etc/rc.d/init.d/krb5server ] && /sbin/chkconfig --del krb5server

in the postinstall scriptlet. But that part should no longer be needed on RHEL 7 installations.

Unless there is a strong reason to keep it, it'd be helpful to remove the dependency.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. docker run -ti rhel7.2 yum install krb5-server

Actual results:

--> Processing Dependency: initscripts >= 8.99-1 for package: krb5-server-1.13.2-10.el7.x86_64

and initscripts added to the transaction.

Expected results:

initscripts not pulled into the transaction.

Additional info:

Comment 8 errata-xmlrpc 2016-11-03 20:23:16 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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