Bug 1272129 - [libXaw] error: Installed (but unpackaged) file(s) found
Summary: [libXaw] error: Installed (but unpackaged) file(s) found
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libXaw
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Benjamin Tissoires
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-15 14:30 UTC by Tomas Pelka
Modified: 2017-08-01 16:00 UTC (History)
0 users

Fixed In Version: libXaw-1.0.13-4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 16:00:03 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1865 0 normal SHIPPED_LIVE Moderate: X.org X11 libraries security, bug fix and enhancement update 2017-08-01 17:50:43 UTC

Description Tomas Pelka 2015-10-15 14:30:02 UTC 
Description of problem:
error: Installed (but unpackaged) file(s) found:
   /usr/share/doc/libXaw-1.0.12/libXaw.html
   /usr/share/doc/libXaw-1.0.12/libXaw.html.db
   /usr/share/doc/libXaw-1.0.12/libXaw.pdf
   /usr/share/doc/libXaw-1.0.12/libXaw.pdf.db
   /usr/share/doc/libXaw-1.0.12/libXaw.ps
   /usr/share/doc/libXaw-1.0.12/libXaw.txt


Version-Release number of selected component (if applicable):
libXaw-1.0.12-5.el7

How reproducible:
100%

Steps to Reproduce:
1. rebuild libXaw (not in brew)
2.
3.

Actual results:


Expected results:


Additional info:
Comment 5 errata-xmlrpc 2017-08-01 16:00:03 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.

https://access.redhat.com/errata/RHSA-2017:1865
Note You need to log in before you can comment on or make changes to this bug.