New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compiling nuvolaplayer-3.1.2 with Fedora's own waf 1.9.7 version fails #327
Comments
Of course it fails, waf 1.7 → 1.9 is a huge step.
Thanks for the patch, but it is not acceptable as the only thing that
That's because you have removed the I'm closing this issue as the wscript is supposed to be used with the bundled waf. I plan to port wsript to waf 1.9.10 in following weeks though. |
FYI, wscript has been ported and the changes are not trivial. I recommend waiting for 3.1.3 snapshot (hopefully this weekend) instead of using your hacky patch. |
Many thanks for your information, i will wait until 3.1.3 will appear. |
I tried it again with diorite-0.3.4 and waf-1.9.10 on Fedora 25, but this fails again: installed diorite version:
I have already install waf-1.9.10 from koji, in the next days waf-1.9.10 will be in the fedora stable repo.
I compile nuvolaplayer with the following rpm spec file:
|
Use Python 3 to run waf |
ok, solved it by removing "rm branding/default.json" |
I must say I'm fascinated by the way you "solve" issues. Workarounds and hacks rather then proper solutions. The changelog explicitly says "All Python scripts require Python >= 3.4." but you still insist on running the build script with Python 2. |
I changed the build requirement to %{_bindir}/waf-3 in the spec file now, so that will execute waf by python3. https://bugzilla.redhat.com/show_bug.cgi?id=1447231 |
That's the proper solution 👍 |
compiling with this spec file fails:
https://martinkg.fedorapeople.org/Packages/nuvolaplayer/nuvolaplayer.spec
with the following patch nuvolaplayer compiles
https://martinkg.fedorapeople.org/Packages/nuvolaplayer/nuvolaplayer-wscript.patch
but now i get this error message:
The text was updated successfully, but these errors were encountered: