I double checked the spec file and it's not messing with the mode and the
source filed themselves are set exactly like the other 1200 files. Let me see
if I can work up a reproducable example.
--
Reply to this email directly or view it on GitHub:
That message is just a warning if the file in question is not executable, so
that has changed for whatever reason.
The mode in the message comes from the package, which may inherit it from the
disk or be spec defined. This sounds like the spec is accidentally overriding
the file mode for
I've got 4 out of almost 1200 sound files in signed-linear format that are
causing rpmbuild to fail with messages like `Recognition of file mtype
"...calls-waiting-for-rep.sln16" failed: mode 100755 (null)`. If I run `file`
on those 4, they return `Unicode text, UTF-32, big-endian` but there
