Bug 1883996

Summary: Inconsistent folders in pki-tools
Product: Red Hat Enterprise Linux 8 Reporter: Endi Sukma Dewata <edewata>
Component: pki-coreAssignee: Endi Sukma Dewata <edewata>
Status: CLOSED ERRATA QA Contact: PKI QE <bugzilla-pkiqe>
Severity: unspecified Docs Contact: Florian Delehaye <fdelehay>
Priority: unspecified    
Version: 8.4CC: aakkiang, fdelehay, mharmsen, prisingh
Target Milestone: rcKeywords: TestCaseProvided
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: pki-core-10.6-8040020201020223442.d4d99205 Doc Type: Bug Fix
Doc Text:
.`pki-tools` files are now in a single folder The following files from the `pki-tools` package were in separate `java-tools` and `native-tools` folders: * /usr/share/pki/java-tools/DRMTool.cfg * /usr/share/pki/java-tools/KRATool.cfg * /usr/share/pki/native-tools/setpin.conf For consistency, they are now merged into a single folder: * /usr/share/pki/tools/DRMTool.cfg * /usr/share/pki/tools/KRATool.cfg * /usr/share/pki/tools/setpin.conf
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-18 15:25:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Endi Sukma Dewata 2020-09-30 17:23:45 UTC
Currently the pki-tools package contains some files in "java-tools"
and "native-tools" folders:

$ rpm -ql pki-tools | egrep "java-tools|native-tools"

For consistency they should be moved into a single "tools" folder:

$ rpm -ql pki-tools

Comment 1 Endi Sukma Dewata 2020-09-30 18:10:51 UTC
First PR (there will be more):

Comment 8 errata-xmlrpc 2021-05-18 15:25:15 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 (Moderate: pki-core:10.6 and pki-deps:10.6 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

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