Pretty sure this problem existed before 3.18.6 as this has been reported upstream already for 3.11.3.
I think it now pops up again because net-libs/nodejs introduced this symlink in a recent version.
Pretty sure this problem existed before 3.18.6 as this has been reported upstream already for 3.11.3.
I think it now pops up again because net-libs/nodejs introduced this symlink in a recent version.