Bug 1485891 - Bogus permissions on /usr/share/doc/liblayout
Summary: Bogus permissions on /usr/share/doc/liblayout
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: liblayout
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-28 11:23 UTC by Ralf Corsepius
Modified: 2017-11-06 23:33 UTC (History)
1 user (show)

Fixed In Version: liblayout-0.2.10-14.fc26
Clone Of:
Environment:
Last Closed: 2017-11-06 23:33:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ralf Corsepius 2017-08-28 11:23:27 UTC
Description of problem:

The directory /usr/share/doc/liblayout should carry executable permissions:

# rpm -qlvf /usr/share/doc/liblayout/
drw-r--r--    2 root    root                        0 Feb 11  2017 /usr/share/doc/liblayout
-rw-r--r--    1 root    root                     4376 Feb 11  2017 /usr/share/doc/liblayout/ChangeLog.txt
-rw-r--r--    1 root    root                     2013 Feb 11  2017 /usr/share/doc/liblayout/README.txt
-rw-r--r--    1 root    root                    26430 Feb 11  2017 /usr/share/doc/liblayout/licence-LGPL.txt


Version-Release number of selected component (if applicable):
liblayout-0.2.10-13.fc26.noarch

Comment 1 Fedora Update System 2017-09-01 11:53:27 UTC
liblayout-0.2.10-14.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e6fdd92816

Comment 2 Fedora Update System 2017-11-06 23:33:33 UTC
liblayout-0.2.10-14.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.


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