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)
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.
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.
Resolved in the upstream repository: http://git.savannah.gnu.org/gitweb/?p=libcdio.git;a=commit;h=8a8bca964108b7a8c70fa503932160e98eb5af1e