Some library files have unnecessary executable file flag set
Although this is harmless (you will either get errors or the script does nothing if you try running them) it might make problems if you run some security scanner on the system.
Coverage: 97.757%. Remained the same when pulling 56fa164c80e53d9d4a51145bb45f098800f94f5a on exec_flags_SP5 into a3a9728d786790da2c04a3458f61be68f99ac560 on SLE-15-SP5.
Problem
Notes
It turned out that the executable flags were added by Rubocop when it found a shebang (
#!/usr/bin/env ruby
) at the beginning of the file. See https://github.com/yast/yast-storage-ng/commit/381b52516e3425dc4ad1107b16c4abada2a485e6#diff-6fd7d4d70024d603ba6a0d36f66051086247b4c3a1845dff08420dc5e1c1f5c4. Later the shebang has been removed, but the executable flag stayed untouched.Solution