RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

[Dummy bug per pkis request so each change in RHEL7.x has a bug]
Description of problem:
RFE: Do a minor spec file cleanup and sync with recent Fedora 22/23 changes. This was mainly done because Fedora 22+23 and RHEL7.2 all were rebased to krb5 1.13.2 so common obsolete constructs were first applied to Fedora and then to RHEL7.2 as part of the rebase
Misc changes include:
- Removal/replacement of obsolete or dangerous shell constructs (e.g. `foo`-->$(foo), rm -R -- "$var" instead of rm -Rf $var, use of correct POSIX shell arithmetric, e.g. [ "$1" -ge 1 ] should be (( $1 >= 1 )) etc etc.)
- use of pax(1) because tar(1) was sometimes producing different md5 hashes for the same directory content (no clue why and the use of pax(1) is harmless because GNU tar(1) can handle POSIX pax/ustar archive formats, too). In the long run we will just stop producing the temporary PDF archive and just rebuild the docs each time during build
- use of printf(1) instead of echo(1) (echo is depreciated by POSIX since years)
- use of shell arithmetic instead of expr(1) (expr(1) in this case is an overkill) 
- removal of obsolete sections

QA should be sanity only.

Fix checked in (krb5-1.13.2-4.el7) ...

... marking bug as MODIFIED.

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.

https://rhn.redhat.com/errata/RHSA-2015-2154.html