Recently I got this error: !!! The ebuild selected to satisfy "app-text/xournalpp" has unmet requirements. - app-text/xournalpp-1.1.3-r1::gentoo USE="" ABI_X86="(64)" LUA_SINGLE_TARGET="-lua5-3 -lua5-4" The following REQUIRED_USE flag constraints are unsatisfied: exactly-one-of ( lua_single_target_lua5-3 lua_single_target_lua5-4 ) (dependency required by "@selected" [set]) (dependency required by "@world" [argument]) And I was surprised about me needing to manually set a value for every system I maintain... I think it should be handled as PYTHON_SINGLE_TARGET, that sets a default value that gets updates when maintainers think newer versions are stable enough Thanks
Mmm... it seems it is not like python case as I see many different packages needing a different single target :S In that case maybe each package should default to a preferred lua version using +USE syntax :/
I am pretty sure that DO set the default of LUA_SINGLE_TARGET - to the target which at least at the time of us having done it provided the greatest package coverage, i.e. lua5-1. Welcome to the Lua world, where in spite of having been EOLed upstream ages ago 5.1 simply will not die.
The way targets are set is the same: profiles/base/make.defaults currently contains: PYTHON_TARGETS="python3_10" PYTHON_SINGLE_TARGET="python3_10" LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1"
Some solution might be: 1. Set LUA_SINGLE_TARGET="lua5-4" LUA_TARGETS="lua5-4" in make.defaults. 2. Add appropriate per-package lua_single_target_lua5-1 and/or lua_targets_lua5-1 entries in package.use. Currently the inverse was done, but very incompletely: In profiles/base/package.use: >=app-editors/vis-0.7-r1 lua_single_target_lua5-4 >=sys-cluster/ceph-17.2.0 lua_single_target_lua5-4 >=app-arch/rpm-4.17.0 lua_single_target_lua5-4 media-video/wireplumber lua_single_target_lua5-4 Instead of having ever-growing list of ..._lua5-4 entries, I suggest to have initially bigger, gradually shrinking list of ..._lua5-1 entries in package.use.
(In reply to Arfrever Frehtes Taifersar Arahesis from comment #4) > Some solution might be: > > 1. Set LUA_SINGLE_TARGET="lua5-4" LUA_TARGETS="lua5-4" in make.defaults. I tried that... but then I realized many other lua-single packages need other lua versions and does not work :/ > > 2. Add appropriate per-package lua_single_target_lua5-1 and/or > lua_targets_lua5-1 entries in package.use. > > > Currently the inverse was done, but very incompletely: > In profiles/base/package.use: > > >=app-editors/vis-0.7-r1 lua_single_target_lua5-4 > >=sys-cluster/ceph-17.2.0 lua_single_target_lua5-4 > >=app-arch/rpm-4.17.0 lua_single_target_lua5-4 > media-video/wireplumber lua_single_target_lua5-4 Ah... I guess then that xournalpp was forgotten there > > Instead of having ever-growing list of ..._lua5-4 entries, I suggest to have > initially bigger, gradually shrinking list of ..._lua5-1 entries in > package.use. Yeah.. if more packages move to newer versions that would make sense :/
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4312ac55afc6750aaf12f3462c32bdcf78a902c0 commit 4312ac55afc6750aaf12f3462c32bdcf78a902c0 Author: Pacho Ramos <pacho@gentoo.org> AuthorDate: 2023-04-19 12:54:39 +0000 Commit: Pacho Ramos <pacho@gentoo.org> CommitDate: 2023-04-19 12:54:39 +0000 profiles/base: latest xournalpp needs lua >= 5.3 Bug: https://bugs.gentoo.org/904517 Signed-off-by: Pacho Ramos <pacho@gentoo.org> profiles/base/package.use | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
This also affects Wireshark now, if attempting to build with Lua: !!! The ebuild selected to satisfy "net-analyzer/wireshark" has unmet requirements. - net-analyzer/wireshark-4.4.1::gentoo USE="androiddump capinfos captype dftest dumpcap editcap filecaps gui ilbc lua mergecap minizip netlink pcap plugins randpkt randpktdump reordercap sharkd smi ssl text2pcap tshark udpdump wifi zlib zstd -bcg729 -brotli -ciscodump -doc -dpauxmon -http2 -http3 -kerberos -libxml2 -lz4 -maxminddb -opus -sbc -sdjournal (-selinux) -snappy -spandsp -sshdump -test -tfshark -verify-sig" ABI_X86="(64)" LUA_SINGLE_TARGET="-lua5-3 -lua5-4" The following REQUIRED_USE flag constraints are unsatisfied: lua? ( exactly-one-of ( lua_single_target_lua5-3 lua_single_target_lua5-4 ) ) Wasn't a problem with 4.2.8 at least that I have installed now. What's the real fix for this? I can of course try defining the LUA_SINGLE_TARGET for wireshark only.
(In reply to Antti Mäkelä from comment #7) > This also affects Wireshark now, if attempting to build with Lua: > > !!! The ebuild selected to satisfy "net-analyzer/wireshark" has unmet > requirements. > - net-analyzer/wireshark-4.4.1::gentoo USE="androiddump capinfos captype > dftest dumpcap editcap filecaps gui ilbc lua mergecap minizip netlink pcap > plugins randpkt randpktdump reordercap sharkd smi ssl text2pcap tshark > udpdump wifi zlib zstd -bcg729 -brotli -ciscodump -doc -dpauxmon -http2 > -http3 -kerberos -libxml2 -lz4 -maxminddb -opus -sbc -sdjournal (-selinux) > -snappy -spandsp -sshdump -test -tfshark -verify-sig" ABI_X86="(64)" > LUA_SINGLE_TARGET="-lua5-3 -lua5-4" > > The following REQUIRED_USE flag constraints are unsatisfied: > lua? ( exactly-one-of ( lua_single_target_lua5-3 > lua_single_target_lua5-4 ) ) > > Wasn't a problem with 4.2.8 at least that I have installed now. > > What's the real fix for this? I can of course try defining the > LUA_SINGLE_TARGET for wireshark only. +1, though I will mask Wireshark at 4.2.8 until this problem is resolved.
Perhaps the eclass should do what llvm-r1.eclass does and make sure there's always a default one, not sure. The status quo is bad, at least. This was just exposed by new Wireshark dropping Lua 5.1 support.
I should say, if you're hitting this with Wireshark: you can do USE=-lua if you don't care about Lua.
(In reply to Sam James from comment #10) > I should say, if you're hitting this with Wireshark: you can do USE=-lua if > you don't care about Lua. Problem is that I care about LUA, I'm using a couple of LUA-based plugins.
(In reply to Antti Mäkelä from comment #11) That's fine, I'm just pointing out the obvious workaround for those who don't. If you do care about Lua, you'll just have to set LUA_SINGLE_TARGET via package.use for Wireshark for now in package.use.
