Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bugzilla DB migration completed. Please report issues to Infra team via email via infra@gentoo.org or IRC
Bug 407091 (lua-5.2) - [TRACKER] >=dev-lang/lua-5.2.0 introduced breakage
Summary: [TRACKER] >=dev-lang/lua-5.2.0 introduced breakage
Status: CONFIRMED
Alias: lua-5.2
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal with 7 votes (vote)
Assignee: William Hubbs
URL:
Whiteboard: Status: masked in profiles/package.ma...
Keywords: Tracker
Depends on: 407079 434240 508222 ag-ops:dev-lua 406985 407015 407071 407075 407089 407093 407095 407109 407113 407115 407243 407483 434216 434236 434238 434242 464498 482800 490556 498124 524460
Blocks: 253269 618104
  Show dependency tree
 
Reported: 2012-03-06 10:52 UTC by Samuli Suominen
Modified: 2020-09-01 17:42 UTC (History)
14 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Samuli Suominen gentoo-dev 2012-03-06 10:52:05 UTC
No talking here. If you have a package filing, file a new bug and make it block this one.
Comment 1 Julian Ospald 2013-10-23 17:59:26 UTC
this is over 1 year old... I feel it should be exposed to ~arch
Comment 2 Rafael Martins gentoo-dev 2013-10-23 23:25:38 UTC
(In reply to Julian Ospald (hasufell) from comment #1)
> this is over 1 year old... I feel it should be exposed to ~arch

Maybe... I'll review the open bugs this weekend.
Comment 3 Samuli Suominen gentoo-dev 2014-02-06 13:52:34 UTC
i'd unmask at this point despite of remaining broken packages, they'll have to be dealt with, maybe with more radical hand, stupid for our lua to be behind like this
anyways, the decision should come from lua maintainers, not me
Comment 4 Rafael Martins gentoo-dev 2014-02-06 14:03:18 UTC
Most of the breakages happened because we decided to go in a way that isn't supported by upstream (build lua dynamically), so most upstreams don't care about our breakage, and I'd say that they are correct, despite all our "policies" wrt not build things statically, etc. I'm planning on suggest removing that patch and just build lua in the way that upstream supports, so we get a better experience, and better support from upstream.

But I agree with Samuli, let's unmask the beast.
Comment 5 Julian Ospald 2014-02-06 14:13:59 UTC
(In reply to Rafael G. Martins from comment #4)
> Most of the breakages happened because we decided to go in a way that isn't
> supported by upstream (build lua dynamically), so most upstreams don't care
> about our breakage, and I'd say that they are correct, despite all our
> "policies" wrt not build things statically, etc. I'm planning on suggest
> removing that patch and just build lua in the way that upstream supports, so
> we get a better experience, and better support from upstream.
> 

I have heard that before as well from some upstreams like games-action/minetest which uses lua, but I am not sure if I understand the details. One reason was that they built lua with a flag that we did not have. But that was simply fixed by adding the "deprecated" USE flag to dev-lang/lua. I'd say we should discuss this with QA.
Comment 6 Rafael Martins gentoo-dev 2014-02-06 15:36:34 UTC
(In reply to Julian Ospald (hasufell) from comment #5)
> (In reply to Rafael G. Martins from comment #4)
> > Most of the breakages happened because we decided to go in a way that isn't
> > supported by upstream (build lua dynamically), so most upstreams don't care
> > about our breakage, and I'd say that they are correct, despite all our
> > "policies" wrt not build things statically, etc. I'm planning on suggest
> > removing that patch and just build lua in the way that upstream supports, so
> > we get a better experience, and better support from upstream.
> > 
> 
> I have heard that before as well from some upstreams like
> games-action/minetest which uses lua, but I am not sure if I understand the
> details. One reason was that they built lua with a flag that we did not
> have. But that was simply fixed by adding the "deprecated" USE flag to
> dev-lang/lua. I'd say we should discuss this with QA.

+1 on discuss with QA.
Comment 7 Sergey Popov gentoo-dev 2014-12-30 13:03:45 UTC
CCing qa@

Guys, what's the progress here? I understand that there is some work that needs to be done here, but can we please discuss generic direction about what should we do here?

Maybe some help needed?
Comment 8 C W Rose 2016-10-17 11:29:34 UTC
5.2.x has a number of advantages for embedded Lua.  What work needs to be done to get it unmasked?

Thanks - Will
Comment 9 schmittlauch 2017-05-11 21:24:19 UTC
Having looked through the comments of all dependent bugs, almost all of them are resolvable through updating to current upstream releases or restricting dependencies.
The only one still being open after that will be prosody-0.9, as lua-5.2 support will be introduced only in 0.10 which is the current development version.
So we have to consider whether we want to keep all lua packages back only because of prosody or whether we can consider lua-5.1 as a prosody-runtime component then.
Comment 10 Simon 2018-02-25 13:39:51 UTC
Is anyone actively working on this? Lua 5.2 is currently 6+ years old, can this (along with 5.3) please be stabilized? If there are still packages that don't work it probably makes sense to either drop them or make sure they depend on an older lua version.
Comment 11 urcindalo 2018-04-29 10:31:10 UTC
(In reply to Simon from comment #10)
> Is anyone actively working on this? Lua 5.2 is currently 6+ years old, can
> this (along with 5.3) please be stabilized? If there are still packages that
> don't work it probably makes sense to either drop them or make sure they
> depend on an older lua version.

Although this is a tracker, and thus "no talking here", I second the cited comment. Six whole years have already passed since the OP, lua is now at v5.3 but Gentoo only has ONE version unmasked: 5.1.5-r4.

Why is that? As a regular user I cannot understand the situation.