I recently packaged gpick to version 0.2.4 but cannot update it to 0.2.5 due to dependency of lua 5.2.x (a year old of bug report). Upstream has provided a bundle of lua and would like an exception to include the internal library until lua get updated. I am aware about bundling policy but, as a distribution that should be close to upstream as possible, it is unacceptable such crucial package lacked update for years.
Bug report: gpick: https://bugzilla.redhat.com/show_bug.cgi?id=959032 lua: https://bugzilla.redhat.com/show_bug.cgi?id=815263
What is the rationale for bundling lua in gpick? I thought at first the claim was that gpick was essential enough that it should be allowed to update even though this would require a bundled lua but that doesn't seem to be the case (it's just a color picker).
We have a bunch of standard questions that if answered help to clarify whether there's a reason to allow the bundling: https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries#Standard_questions
Lua external cpp LuaExt.cpp
Lua external header LuaExt.h
Replying to [comment:1 toshio]:
Bundling lua in gpick is a temporarily workaround about the lack of latest lua library inside Fedora repository. It is needed to convert custom palettes i.e. imported gimp, inkscape palettes. Once lua is updated to latest version, the bundled lua will be dropped.
''Has the library behaviour been modified? If so, how has it been modified?'' Yes, see http://code.google.com/p/gpick/issues/detail?id=90
''Have the changes been proposed to the Fedora package maintainer for the library?'' Yes, changes are already applied to the maintainer which is unresponsive. https://bugzilla.redhat.com/show_bug.cgi?id=815263 Opensuse already included lua 5.2 and rebase older versions
https://build.opensuse.org/package/show?package=lua&project=openSUSE%3AFactory https://build.opensuse.org/package/show?package=lua51&project=openSUSE%3AFactory
I contacted upstream gpick to see if it is possible to build without lua.
Changes to the build scripts don't really count for bundling. We change build scripts to allow building of rpm packages so it's not something that maintainers should be unfamiliar with.
If the lua maintainer is unresponsive, it might be time to do the AWOL maintainer process for them and someone else take over lua. Or, if the maintainer simply doesn't have time to kep lua up-to-date, it might be better to start a conversation with the maintainer and fesco about getting some other people added as comaintainers asap so that this can be pushed to rawhide soon.
Good to know. It will be nice that lua bug gets resolved asap.
Bundling exception denied, spot is going to update lua in rawhide (+1:0, 0:0, -1:6)
Thank you, spot.
Login to comment on this ticket.