On Mon, 4 Jan 2021 at 13:15, Bertram Scharpf <[email protected]> wrote: > # grep -rnHi lua /etc/portage > /etc/portage/make.conf:40:LUA_SINGLE_TARGET="lua5-1" # luajit > /etc/portage/package.use/zz-autouse:3:>=dev-lua/lpeg-1.0.1 luajit > /etc/portage/package.use/zz-autouse:6:>=dev-lua/mpack-1.0.4 luajit > /etc/portage/package.use/zz-autouse:10:>=dev-lua/luv-1.30.1.1 luajit > /etc/portage/package.accept_keywords/local:26:<dev-lang/lua-5.2 > ~amd64 > > Here's another time how emerge complains: > > - app-editors/neovim-0.4.4-r100::gentoo (Change USE: > -lua_single_target_lua5-1, this change violates use flag constraints defined > by app-editors/neovim-0.4.4-r100: 'exactly-one-of ( lua_single_target_luajit > lua_single_target_lua5-1 lua_single_target_lua5-2 )') > > As far as I understand this, emerge tells me to remove the > use flag "lua_single_target_lua5-1" because the use flag > "lua_single_target_lua5-1" is required.
As far as I understand it, this is saying that your emerge command is about to remove that USE flag from neovim, which breaks the constraint. So basically some other package is stopping your update. Your original mail mentioned that this was because of dev-lua/luv. You have in your /etc/portage/package.use/zz-autouse set the luajit flag on this package. Might this be the problem? I'm not that familiar with lua, but as far as I understand the output, app-editors/neovim and dev-lua/luv needs the same LUA_SINGLE_TARGET, and setting that USE flag on dev-lua/luv might trip up this. Reading the latest ebuild, this flag has been removed in the ~amd64 package, so might as well remove it now and see if that fixes your problem. Regards, Arve
