IMHO that is a less critical issue. But "often" for other reasons. An advantage of this patch is that it just fixes the existing approach to work in more situations. That would cause "successful" RPM builds which doesn't include all the files distutil installed. If you want another approach: Why use a filelist at all? For 2. For example it works for logilab. I agree. I had another complaint about that patch, though, which is the addition of an option for not including.
I still like to see addition of this option reverted. But preventing invocation of brp-python-bytecompile is IMHO not a solution. What reason specifically are you referring to? That it creates and packages.
FWIW I think it is a bit of an ugly hack and would prefer another solution. Chris Maes Add a comment. Active Oldest Votes. Improve this answer. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.
Post as a guest Name. Also added Dave Malcolm as the Fedora Python package maintainer. Applying to get the full failing command line sounds worthwhile, but shouldn't be related, since the RHEL buildbot definitely has rpmbuild available.
However, my guess is that it's not using the correct version of python when invoking "compileall", which would explain why it's using the pre-PEP location for the. Can you run "file" on the. So if it is indeed using the wrong python executable to do the bytecompiling, the above ought to fix it. Since I'm seeing the same fault on my Fedora system, I'll start poking around there instead not sure when I'll get to it though.
I don't know why this wouldn't work on RHEL6 then I tweaked Ross's patch slightly to: 1. Use self. Also default self. Active Oldest Votes. Improve this answer. Sign up or log in Sign up using Google. Sign up using Facebook.
Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.
0コメント