Description of problem: k3d use yafray, but yafray was renamed with name YafaRay. Version-Release number of selected component (if applicable): k3d-0.8.0.2-24 How reproducible: always Steps to Reproduce: 1. run k3d 2. no yafray executable Additional info: k3dsdk/ngui/render.cpp: if(k3d::system::find_executable("yafray").empty()) Debian has yafray_0.0.9, but it's time to use YafaRay. Please add patch or build yafray-0.0.9.
Thanks for the report. (In reply to AlexL from comment #0) > k3dsdk/ngui/render.cpp: if(k3d::system::find_executable("yafray").empty()) > Debian has yafray_0.0.9, but it's time to use YafaRay. Agreed, packaging yafray-0.0.9 at this point in time, probably isn't useful. > Please add patch or build yafray-0.0.9. I am leaning towards this. Unfortunately, I am not sufficiently familiar with yafray/YafaRay and compatibility between these to be sure this can easily be done. That said, I'd ask you to try an experiment: Could you please add a symlink /usr/bin/yafray -> /usr/bin/yafaray-xml to your system (ln -s /usr/bin/yafaray-xml /usr/bin/yafray) and check if k3d behaves as you expect it? If so, a patch would be easy. Otherwise, I guess, I will have to resort to disabling yafray-support in k3d.
Ralf, thank you for fast reply. Tested, k3d works with any executable, but symlink is not good fix. Better to fix code of k3b: for executable: s/yafray/yafaray-xml/ for strings in program: s/yafray/yafaray/ s/Yafray/Yafaray/
(In reply to AlexL from comment #2) > Ralf, thank you for fast reply. > > Tested, k3d works with any executable, but symlink is not good fix. Sure. That's why I said "experiment". My plan is to patch the sources, but before doing so, I just wanted to verify if replacing the binaries works. Thanks.
It's time to update new version: https://github.com/K-3D/k3d/releases/tag/k3d-0.8.0.3 , which uses yafray.
(In reply to AlexL from comment #4) > It's time to update new version: > https://github.com/K-3D/k3d/releases/tag/k3d-0.8.0.3 , which uses yafray. Would you mind to explain what the problem is? AFAIR, the k3d-0.8.0.2 in Fedora already uses yafray. Also, I am also aware Debian ships a k3d-0.8.0.3 from github, but this version has proven to be problematic. Also, k-3d.org has not been updated for k3d-0.8.0.3 nor has their been any official release announcement ;)
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
k3d-0.8.0.5-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-6a5c98ecd9
k3d-0.8.0.5-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-afac462fa7
k3d-0.8.0.5-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update k3d' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-afac462fa7
k3d-0.8.0.5-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update k3d' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-6a5c98ecd9
k3d-0.8.0.5-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
k3d-0.8.0.5-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.