Bug 1247351 - [debuginfo package] libcdio ships executable source files
[debuginfo package] libcdio ships executable source files
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: libcdio (Show other bugs)
22
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Adrian Reber
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-07-27 15:39 EDT by Christian Stadelmann
Modified: 2015-07-28 12:29 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-28 12:29:42 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Christian Stadelmann 2015-07-27 15:39:35 EDT
Description of problem:
These source files from libcdio-debuginfo are executable:
lib/driver/MSWindows/win32.c
lib/driver/image/bincue.c
lib/driver/image/cdrdao.c
lib/driver/sector.c
lib/driver/util.c

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

How reproducible:
always (see rpm package)
Comment 1 Adrian Reber 2015-07-27 16:30:40 EDT
Thanks for the bug report, but are you sure that really is a problem. This is how we get the source code from upstream. This sounds like something which should be discussed with upstream.

I can change the files in the build process to be not executable but I do not really see the benefit. I would recommend contacting the upstream authors of libcdio so that they can fix it in git.
Comment 2 Christian Stadelmann 2015-07-27 18:20:34 EDT
In theory, yes (if the file started with something like a crunchbang, e.g. !#/bin/sh). But yes, I think upstream git fixes would be the best.
Comment 3 Adrian Reber 2015-07-28 12:29:42 EDT
Resolved in the upstream repository:

http://git.savannah.gnu.org/gitweb/?p=libcdio.git;a=commit;h=8a8bca964108b7a8c70fa503932160e98eb5af1e

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