Hi,
Squeeze is already released and this Debian bug just prevents luajit
from entering into testing (wheezy). Thus bug name ("unsuitable for
squeeze") is a bit misleading.
I'm a maintainer of uwsgi source package [1], which builds up several
dozen binary packages -- and just one of them (uwsgi-plugin-luajit) is
build-depending on libluajit-5.1-dev. This dependency blocks all of
uWSGI binary packages from entering into testing.
So I'm curious when this release-critical bug of luajit package will
be resolved? When "-beta" suffix will be dropped by upstream or earlier?
I've looked for upstream point of view and found following notes:
* paragraph on Status page of official website [2]
> LuaJIT 2.0 is the currently active development branch. It has Beta
> Test status and is still undergoing substantial changes. It has much
> better performance than LuaJIT 1.x. It's maturing quickly, so you
> should definitely start to evaluate it for new projects right now.
* excerpt from LuaJIT Roadmap 2011 [3]
> LuaJIT 2.0.0-beta5 has proven to be quite stable. Thus I've held back
> on releasing new betas in the past five months and worked on various
> new features and improvements.
>
> [...]
>
> LuaJIT 2.0 has been in beta for more than a year now. Not that this
> is unheard of in the industry. :-) The main reason is not a lack of
> stability -- in fact the beta releases are successfully used in
> production environments.
>
> But the "beta" label gives me the ability to freely add features and
> to just go ahead with bigger redesigns of the code base.
So upstream doesn't mark beta versions as "unstable", but rather as
"rapidly evolving". Could these statements be used as a reason for
resolving this release-critical Debian bug?
[1] http://packages.debian.org/source/sid/uwsgi
[2] http://luajit.org/status.html
[3] http://lua-users.org/lists/lua-l/2011-01/msg01238.html
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
