Hello, I'm starting to use the new Python macros in my packages. Very good job, specfiles are much more cleaner now.
One thing that doesn't change is the rpmlint error about .so files having mode 775 instead of 755
For example:
E non-standard-executable-perm /usr/lib64/python2.7/site-packages/sep.so 775
I routinely do a chmod 755 after %install, but now that I'm using %py{2.3}_install, could this step be part of the macro?
Or if the rpmlint error is inaccurate and 775 permisions are OK, fix rpmlint?
Best, Sergio
"SP" == Sergio Pascual sergio.pasra@gmail.com writes:
SP> One thing that doesn't change is the rpmlint error about .so files SP> having mode 775 instead of 755
This bugs me too. It if happens for any .so or executable in any package, just do umask 022 before calling your build tools.
This shouldn't be an issue when you build in koji; if it is, then perhaps the package does something odd. Try setting umask explicitly in the package.
- J<
On Sex, 2015-11-20 at 11:11 -0600, Jason L Tibbitts III wrote:
"SP" == Sergio Pascual sergio.pasra@gmail.com writes:
SP> One thing that doesn't change is the rpmlint error about .so files SP> having mode 775 instead of 755
This bugs me too. It if happens for any .so or executable in any package, just do umask 022 before calling your build tools.
This shouldn't be an issue when you build in koji; if it is, then perhaps the package does something odd. Try setting umask explicitly in the package.
I got this problem too , https://bugzilla.redhat.com/show_bug.cgi?id=1234654#c14
This needs further investigation I don't know if the problem is in the source. (make install script)
Best regards,
packaging@lists.fedoraproject.org
-
Jason L Tibbitts III -
Sergio Pascual -
Sérgio Basto