Bug 21868 - ls -l /usr/share/doc/cdparanoia : Permission denied
Summary: ls -l /usr/share/doc/cdparanoia : Permission denied
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-15 00:33 CEST by Bit Twister
Modified: 2018-09-03 09:16 CEST (History)
2 users (show)

See Also:
Source RPM: cdparanoia-10.2-15.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Bit Twister 2017-10-15 00:33:49 CEST
Description of problem: mga7

ls: cannot access '/usr/share/doc/cdparanoia/README': Permission denied

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


How reproducible:  Always

Steps to Reproduce:
1. ls -l /usr/share/doc/cdparanoia

Workaround:  chmod +x /usr/share/doc/cdparanoia
Comment 1 Marja Van Waes 2017-10-15 09:36:53 CEST
confirming the issue

[marja@localhost ~]$ ls -al /usr/share/doc | grep "drw-r--r--" | grep "root root"
drw-r--r--    2 root root  4096 okt 29  2016 abattis-cantarell-fonts/
drw-r--r--    2 root root  4096 okt 29  2016 bobobot/
==> drw-r--r--    2 root root  4096 okt 29  2016 cdparanoia/ <==
drw-r--r--    2 root root  4096 dec  3  2016 dmsetup/
drw-r--r--    8 root root  4096 jan  1  2017 fortune-mod/
drw-r--r--    2 root root  4096 dec  3  2016 lvm2/
drw-r--r--    2 root root  4096 okt 29  2016 stix-fonts/
drw-r--r--    2 root root  4096 dec  6  2016 tcsh/
[marja@localhost ~]$

Assigning to all packagers collectively, since there is no registered maintainer for this package.

Ever confirmed: 0 => 1
Status: UNCONFIRMED => NEW
CC: (none) => marja11
Assignee: bugsquad => pkg-bugs

Comment 2 David GEIGER 2017-10-18 07:11:03 CEST
Fixed for Cauldron, and commit svn done for mga6!

CC: (none) => geiger.david68210

Comment 3 Bit Twister 2018-09-03 09:16:21 CEST
closing bug

Resolution: (none) => FIXED
Status: NEW => RESOLVED


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