Description of problem: One of the new features in darktable 1.4 is Lua scripting support. http://www.darktable.org/2013/09/using-lua-with-darktable/ It isn't in the Fedora build because the dependencies aren't in place at build time. Version-Release number of selected component (if applicable): darktable-1.4-1 Expected results: Lua scripting is available in the 1.4 build. Additional info: For Fedora 20 adding the deps to the spec file enable this feature BuildRequires: lua-devel >= 5.2 BuildRequires: GraphicsMagick-devel In Fedora 19 Lua is still at 5.1 so the build doesn't work. I'm not sure if darktable really needs 5.2 but until further investigation can be done it may be best to leave the deps out. Note: darktable does bundle Lua 5.2 in the release tarball and passing "-DDONT_USE_INTERNAL_LUA=Off" to the cmake command does work for enabling the feature in Fedora 19. This violates the packaging guidelines with regards to bundling and probably shouldn't be used. We may need to also remove 'src/lua' from the tarball created for srpm but I'm not sure if that's required or if simply making sure the build only uses the system Lua (default behavior) is enough to satisfy the guidelines.
Created attachment 886227 [details] Enable lua support on F-20+ 'git am'able fix attached, build tested on Rawhide only.
I talked with Darktable developers, and I am going to fix it in 1.6.2. I will push it in testing repositories as soon as possible
Darktable 1.6 works only with LUA 5.2 On Fedora 20 and 21 we ship it, but in Fedora 22 there is LUA 5.3 that is not compatible. We cannot break build tree enabling LUA only in F20 and F21. Darktable developers have not yet planned a further support for LUA 5.3 Package compat-lua could be a workaround, but actually it is for LUA 5.1 version. I contacted the mantainer to get infos but I have not yet received a reply.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
*** This bug has been marked as a duplicate of bug 1398489 ***