11:34 a.m.
Hi,
RStudio (which depends on nodejs-devel) is FTBFS since the latest
nodejs update. I see this in F37 and F38:
Error: Transaction test error:
file /usr/lib64/libv8.so.10 conflicts between attempted installs of
nodejs-libs-1:18.14.2-5.fc37.x86_64 and
nodejs20-libs-1:19.7.0-13.fc37.x86_64
file /usr/lib64/libv8_libbase.so.10 conflicts between attempted
installs of nodejs-libs-1:18.14.2-5.fc37.x86_64 and
nodejs20-libs-1:19.7.0-13.fc37.x86_64
file /usr/lib64/libv8_libplatform.so.10 conflicts between attempted
installs of nodejs-libs-1:18.14.2-5.fc37.x86_64 and
nodejs20-libs-1:19.7.0-13.fc37.x86_64
Best,
--
Iñaki Úcar
12:09 p.m.
I see the same with a couple of my packages. A look at
https://src.fedoraproject.org/rpms/nodejs suggests that we shouldn't
be using BuildRequires: nodejs-devel anymore, but rather
nodejsXX-devel for an appropriate value of XX. It looks like "20" is
the only currently appropriate value for XX. I am unsure how that is
supposed to work going forward.
On Wed, Mar 15, 2023 at 10:35 AM Iñaki Ucar <iucar(a)fedoraproject.org> wrote:
Hi,
RStudio (which depends on nodejs-devel) is FTBFS since the latest
nodejs update. I see this in F37 and F38:
Error: Transaction test error:
file /usr/lib64/libv8.so.10 conflicts between attempted installs of
nodejs-libs-1:18.14.2-5.fc37.x86_64 and
nodejs20-libs-1:19.7.0-13.fc37.x86_64
file /usr/lib64/libv8_libbase.so.10 conflicts between attempted
installs of nodejs-libs-1:18.14.2-5.fc37.x86_64 and
nodejs20-libs-1:19.7.0-13.fc37.x86_64
file /usr/lib64/libv8_libplatform.so.10 conflicts between attempted
installs of nodejs-libs-1:18.14.2-5.fc37.x86_64 and
nodejs20-libs-1:19.7.0-13.fc37.x86_64
Best,
--
Iñaki Úcar
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
Jerry James
http://www.jamezone.org/
12:15 p.m.
On Wed, Mar 15, 2023 at 11:09 AM Jerry James <loganjerry(a)gmail.com> wrote:
I see the same with a couple of my packages. A look at
https://src.fedoraproject.org/rpms/nodejs suggests that we shouldn't
be using BuildRequires: nodejs-devel anymore, but rather
nodejsXX-devel for an appropriate value of XX. It looks like "20" is
the only currently appropriate value for XX. I am unsure how that is
supposed to work going forward.
Unfortunately, that doesn't fix the 2 cases I am looking at, because
they use yarnpkg, and installing yarnpkg pulls nodejs and nodejs-libs
into the buildroot, not nodejs20 and nodejs20-libs.
--
Jerry James
http://www.jamezone.org/
10:19 a.m.
On Wed, Mar 15, 2023 at 1:16 PM Jerry James <loganjerry(a)gmail.com> wrote:
On Wed, Mar 15, 2023 at 11:09 AM Jerry James <loganjerry(a)gmail.com> wrote:
> I see the same with a couple of my packages. A look at
> https://src.fedoraproject.org/rpms/nodejs suggests that we shouldn't
> be using BuildRequires: nodejs-devel anymore, but rather
> nodejsXX-devel for an appropriate value of XX. It looks like "20" is
> the only currently appropriate value for XX. I am unsure how that is
> supposed to work going forward.
Unfortunately, that doesn't fix the 2 cases I am looking at, because
they use yarnpkg, and installing yarnpkg pulls nodejs and nodejs-libs
into the buildroot, not nodejs20 and nodejs20-libs.
nodejs20-* should definitely not be getting pulled in. I probably have
a bug there (something I missed when forking it from nodejs18)
I suspect that's the root cause: your existing nodejs-devel BR should
continue to work. You don't need to specify `BuildRequires:
nodejsXX-devel` unless you need to guarantee a specific version which
isn't (necessarily) the default one for that release.
Please open a BZ to track this problem; I'll start looking into it.
Sorry for the disruption!
10:46 a.m.
Reported here: https://bugzilla.redhat.com/show_bug.cgi?id=2179086
On Thu, 16 Mar 2023 at 16:21, Stephen Gallagher <sgallagh(a)redhat.com> wrote:
On Wed, Mar 15, 2023 at 1:16 PM Jerry James <loganjerry(a)gmail.com> wrote:
>
> On Wed, Mar 15, 2023 at 11:09 AM Jerry James <loganjerry(a)gmail.com> wrote:
> > I see the same with a couple of my packages. A look at
> > https://src.fedoraproject.org/rpms/nodejs suggests that we shouldn't
> > be using BuildRequires: nodejs-devel anymore, but rather
> > nodejsXX-devel for an appropriate value of XX. It looks like "20"
is
> > the only currently appropriate value for XX. I am unsure how that is
> > supposed to work going forward.
>
> Unfortunately, that doesn't fix the 2 cases I am looking at, because
> they use yarnpkg, and installing yarnpkg pulls nodejs and nodejs-libs
> into the buildroot, not nodejs20 and nodejs20-libs.
nodejs20-* should definitely not be getting pulled in. I probably have
a bug there (something I missed when forking it from nodejs18)
I suspect that's the root cause: your existing nodejs-devel BR should
continue to work. You don't need to specify `BuildRequires:
nodejsXX-devel` unless you need to guarantee a specific version which
isn't (necessarily) the default one for that release.
Please open a BZ to track this problem; I'll start looking into it.
Sorry for the disruption!
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
Iñaki Úcar
8:45 a.m.
On Thu, 2023-03-16 at 11:19 -0400, Stephen Gallagher wrote:
On Wed, Mar 15, 2023 at 1:16 PM Jerry James
<loganjerry(a)gmail.com>
wrote:
>
> On Wed, Mar 15, 2023 at 11:09 AM Jerry James <loganjerry(a)gmail.com>
> wrote:
> > I see the same with a couple of my packages. A look at
> > https://src.fedoraproject.org/rpms/nodejs suggests that we
> > shouldn't
> > be using BuildRequires: nodejs-devel anymore, but rather
> > nodejsXX-devel for an appropriate value of XX. It looks like
> > "20" is
> > the only currently appropriate value for XX. I am unsure how
> > that is
> > supposed to work going forward.
>
> Unfortunately, that doesn't fix the 2 cases I am looking at,
> because
> they use yarnpkg, and installing yarnpkg pulls nodejs and nodejs-
> libs
> into the buildroot, not nodejs20 and nodejs20-libs.
nodejs20-* should definitely not be getting pulled in. I probably
have
a bug there (something I missed when forking it from nodejs18)
I found a problem related with yarnpkg rpm, the macro % __find_requires
finds that yarn scripts uses and needs /usr/bin/node , which is added
to the requires of rpm [1] and this makes yarnpkg pull nodejs (18) even
when nodejs20 is installed .
To avoid this rpm automatic requires, we may add to yarnpkg.spec [2]
[2]
%global __script_requires %{nil}
[1]
dnf repoquery yarnpkg --available --requires -q
/usr/bin/bash
/usr/bin/node
/usr/bin/sh
I suspect that's the root cause: your existing nodejs-devel BR
should
continue to work. You don't need to specify `BuildRequires:
nodejsXX-devel` unless you need to guarantee a specific version which
isn't (necessarily) the default one for that release.
Please open a BZ to track this problem; I'll start looking into it.
Sorry for the disruption!
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
Sérgio M. B.
9:23 a.m.
On Tue, Apr 4, 2023 at 9:45 AM Sérgio Basto <sergio(a)serjux.com> wrote:
On Thu, 2023-03-16 at 11:19 -0400, Stephen Gallagher wrote:
> On Wed, Mar 15, 2023 at 1:16 PM Jerry James <loganjerry(a)gmail.com>
...
I found a problem related with yarnpkg rpm, the macro %
__find_requires
finds that yarn scripts uses and needs /usr/bin/node , which is added
to the requires of rpm [1] and this makes yarnpkg pull nodejs (18) even
when nodejs20 is installed .
To avoid this rpm automatic requires, we may add to yarnpkg.spec [2]
[2]
%global __script_requires %{nil}
[1]
dnf repoquery yarnpkg --available --requires -q
/usr/bin/bash
/usr/bin/node
/usr/bin/sh
I'm not sure what you think is a bug here? Do you think `yarnpkg`
should use *any* nodejs version that's installed? The whole point of
the way this is broken down is that we have a default version (18, in
this case) with the option to install 16 and 20 in parallel, but you
have to do extra work if you want to *use* those non-default versions
(such as patching shebang lines).
9:57 a.m.
On Tue, 2023-04-04 at 10:23 -0400, Stephen Gallagher wrote:
On Tue, Apr 4, 2023 at 9:45 AM Sérgio Basto
<sergio(a)serjux.com>
wrote:
>
> On Thu, 2023-03-16 at 11:19 -0400, Stephen Gallagher wrote:
> > On Wed, Mar 15, 2023 at 1:16 PM Jerry James
> > <loganjerry(a)gmail.com>
...
> I found a problem related with yarnpkg rpm, the macro %
> __find_requires
> finds that yarn scripts uses and needs /usr/bin/node , which is
> added
> to the requires of rpm [1] and this makes yarnpkg pull nodejs (18)
> even
> when nodejs20 is installed .
> To avoid this rpm automatic requires, we may add to yarnpkg.spec
> [2]
>
> [2]
> %global __script_requires %{nil}
>
> [1]
> dnf repoquery yarnpkg --available --requires -q
> /usr/bin/bash
> /usr/bin/node
> /usr/bin/sh
>
I'm not sure what you think is a bug here? Do you think `yarnpkg`
should use *any* nodejs version that's installed?
yes
The whole point of
the way this is broken down is that we have a default version (18, in
this case) with the option to install 16 and 20 in parallel, but you
have to do extra work if you want to *use* those non-default versions
(such as patching shebang lines).
ok
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
Sérgio M. B.
4:24 a.m.
On Tue, 4 Apr 2023 at 16:23, Stephen Gallagher <sgallagh(a)redhat.com> wrote:
On Tue, Apr 4, 2023 at 9:45 AM Sérgio Basto <sergio(a)serjux.com> wrote:
>
> On Thu, 2023-03-16 at 11:19 -0400, Stephen Gallagher wrote:
> > On Wed, Mar 15, 2023 at 1:16 PM Jerry James <loganjerry(a)gmail.com>
...
> I found a problem related with yarnpkg rpm, the macro % __find_requires
> finds that yarn scripts uses and needs /usr/bin/node , which is added
> to the requires of rpm [1] and this makes yarnpkg pull nodejs (18) even
> when nodejs20 is installed .
> To avoid this rpm automatic requires, we may add to yarnpkg.spec [2]
>
> [2]
> %global __script_requires %{nil}
>
> [1]
> dnf repoquery yarnpkg --available --requires -q
> /usr/bin/bash
> /usr/bin/node
> /usr/bin/sh
>
I'm not sure what you think is a bug here? Do you think `yarnpkg`
should use *any* nodejs version that's installed? The whole point of
the way this is broken down is that we have a default version (18, in
this case) with the option to install 16 and 20 in parallel, but you
have to do extra work if you want to *use* those non-default versions
(such as patching shebang lines).
This is broken again in rawhide:
$ dnf -qy install yarnpkg
$ ll /usr/bin/node*
lrwxrwxrwx. 1 root root 7 Apr 28 00:00 /usr/bin/node -> node-20
-rwxr-xr-x. 1 root root 28272 Apr 28 00:00 /usr/bin/node-20
lrwxrwxrwx. 1 root root 39 Mar 21 00:00 /usr/bin/nodejs-yarn ->
../lib/node_modules_19/yarn/bin/yarn.js
If yarn should be pinned to a node version, please rebuild yarn when
there's a major version change. And it would be nice if there's a
mechanism to detect such a breakage. I.e. a nodejs(abi) version or
something like that.
--
Iñaki Úcar
4:27 a.m.
On 02.05.23 11:24, Iñaki Ucar wrote:
On Tue, 4 Apr 2023 at 16:23, Stephen
Gallagher<sgallagh(a)redhat.com> wrote:
> On Tue, Apr 4, 2023 at 9:45 AM Sérgio Basto<sergio(a)serjux.com> wrote:
>> On Thu, 2023-03-16 at 11:19 -0400, Stephen Gallagher wrote:
>>> On Wed, Mar 15, 2023 at 1:16 PM Jerry James<loganjerry(a)gmail.com>
> ...
>> I found a problem related with yarnpkg rpm, the macro % __find_requires
>> finds that yarn scripts uses and needs /usr/bin/node , which is added
>> to the requires of rpm [1] and this makes yarnpkg pull nodejs (18) even
>> when nodejs20 is installed .
>> To avoid this rpm automatic requires, we may add to yarnpkg.spec [2]
>>
>> [2]
>> %global __script_requires %{nil}
>>
>> [1]
>> dnf repoquery yarnpkg --available --requires -q
>> /usr/bin/bash
>> /usr/bin/node
>> /usr/bin/sh
>>
> I'm not sure what you think is a bug here? Do you think `yarnpkg`
> should use *any* nodejs version that's installed? The whole point of
> the way this is broken down is that we have a default version (18, in
> this case) with the option to install 16 and 20 in parallel, but you
> have to do extra work if you want to *use* those non-default versions
> (such as patching shebang lines).
This is broken again in rawhide:
$ dnf -qy install yarnpkg
$ ll /usr/bin/node*
lrwxrwxrwx. 1 root root 7 Apr 28 00:00 /usr/bin/node -> node-20
-rwxr-xr-x. 1 root root 28272 Apr 28 00:00 /usr/bin/node-20
lrwxrwxrwx. 1 root root 39 Mar 21 00:00 /usr/bin/nodejs-yarn ->
../lib/node_modules_19/yarn/bin/yarn.js
If yarn should be pinned to a node version, please rebuild yarn when
there's a major version change. And it would be nice if there's a
mechanism to detect such a breakage. I.e. a nodejs(abi) version or
something like that.
AFAICS nodejs is generally broken in rawhide (both nodejs20 and
nodejs18), i.e. just
$ node
<type random chars and press backspace a couple of times>
Segmentation fault (core dumped)
gdb:
Thread 3 "node" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff2ffe6c0 (LWP 1565850)]
0x00007ffff57db195in
v8::internal::compiler::SpecialRPONumberer::ComputeAndInsertSpecialRPO(v8::internal::compiler::BasicBlock*,
v8::internal::compiler::BasicBlock*)() from /lib64/libnode.so.115
Sandro
4:48 a.m.
On Tue, 2 May 2023 at 11:27, Sandro Mani <manisandro(a)gmail.com> wrote:
On 02.05.23 11:24, Iñaki Ucar wrote:
On Tue, 4 Apr 2023 at 16:23, Stephen Gallagher <sgallagh(a)redhat.com> wrote:
On Tue, Apr 4, 2023 at 9:45 AM Sérgio Basto <sergio(a)serjux.com> wrote:
On Thu, 2023-03-16 at 11:19 -0400, Stephen Gallagher wrote:
On Wed, Mar 15, 2023 at 1:16 PM Jerry James <loganjerry(a)gmail.com>
...
I found a problem related with yarnpkg rpm, the macro % __find_requires
finds that yarn scripts uses and needs /usr/bin/node , which is added
to the requires of rpm [1] and this makes yarnpkg pull nodejs (18) even
when nodejs20 is installed .
To avoid this rpm automatic requires, we may add to yarnpkg.spec [2]
[2]
%global __script_requires %{nil}
[1]
dnf repoquery yarnpkg --available --requires -q
/usr/bin/bash
/usr/bin/node
/usr/bin/sh
I'm not sure what you think is a bug here? Do you think `yarnpkg`
should use *any* nodejs version that's installed? The whole point of
the way this is broken down is that we have a default version (18, in
this case) with the option to install 16 and 20 in parallel, but you
have to do extra work if you want to *use* those non-default versions
(such as patching shebang lines).
This is broken again in rawhide:
$ dnf -qy install yarnpkg
$ ll /usr/bin/node*
lrwxrwxrwx. 1 root root 7 Apr 28 00:00 /usr/bin/node -> node-20
-rwxr-xr-x. 1 root root 28272 Apr 28 00:00 /usr/bin/node-20
lrwxrwxrwx. 1 root root 39 Mar 21 00:00 /usr/bin/nodejs-yarn ->
../lib/node_modules_19/yarn/bin/yarn.js
If yarn should be pinned to a node version, please rebuild yarn when
there's a major version change. And it would be nice if there's a
mechanism to detect such a breakage. I.e. a nodejs(abi) version or
something like that.
AFAICS nodejs is generally broken in rawhide (both nodejs20 and nodejs18), i.e. just
$ node
> <type random chars and press backspace a couple of times>
Segmentation fault (core dumped)
gdb:
Thread 3 "node" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff2ffe6c0 (LWP 1565850)]
0x00007ffff57db195 in
v8::internal::compiler::SpecialRPONumberer::ComputeAndInsertSpecialRPO(v8::internal::compiler::BasicBlock*,
v8::internal::compiler::BasicBlock*) () from /lib64/libnode.so.115
Sandro
True! But I only see this with nodejs20, not with 18. And this happens
also in the updates for F37 and F38.
Another weird thing about current packaging is that the default nodejs
does not provide the versioned package. I mean:
- When 18 is the default version, you can install nodejs16, nodejs,
and nodejs20, but not nodejs18.
- When 20 is the default version, you can install nodejs16, nodejs18,
and nodejs, but not nodejs20.
This seems wrong to me. And it makes it difficult to pin some software
to a particular nodejs version across Fedora releases, which I
understood was the purpose. And, per my last message, it seems you
can't do this anyway if yarn is required...
--
Iñaki Úcar
5:33 a.m.
We're seeing the same with anaconda webui - any invocation of node leads to
segmentation fault - npm, npx... nothing works.
On Tue, May 2, 2023 at 11:28 AM Sandro Mani <manisandro(a)gmail.com> wrote:
On 02.05.23 11:24, Iñaki Ucar wrote:
On Tue, 4 Apr 2023 at 16:23, Stephen Gallagher <sgallagh(a)redhat.com>
<sgallagh(a)redhat.com> wrote:
On Tue, Apr 4, 2023 at 9:45 AM Sérgio Basto <sergio(a)serjux.com>
<sergio(a)serjux.com> wrote:
On Thu, 2023-03-16 at 11:19 -0400, Stephen Gallagher wrote:
On Wed, Mar 15, 2023 at 1:16 PM Jerry James <loganjerry(a)gmail.com>
<loganjerry(a)gmail.com>
...
I found a problem related with yarnpkg rpm, the macro % __find_requires
finds that yarn scripts uses and needs /usr/bin/node , which is added
to the requires of rpm [1] and this makes yarnpkg pull nodejs (18) even
when nodejs20 is installed .
To avoid this rpm automatic requires, we may add to yarnpkg.spec [2]
[2]
%global __script_requires %{nil}
[1]
dnf repoquery yarnpkg --available --requires -q
/usr/bin/bash
/usr/bin/node
/usr/bin/sh
I'm not sure what you think is a bug here? Do you think `yarnpkg`
should use *any* nodejs version that's installed? The whole point of
the way this is broken down is that we have a default version (18, in
this case) with the option to install 16 and 20 in parallel, but you
have to do extra work if you want to *use* those non-default versions
(such as patching shebang lines).
This is broken again in rawhide:
$ dnf -qy install yarnpkg
$ ll /usr/bin/node*
lrwxrwxrwx. 1 root root 7 Apr 28 00:00 /usr/bin/node -> node-20
-rwxr-xr-x. 1 root root 28272 Apr 28 00:00 /usr/bin/node-20
lrwxrwxrwx. 1 root root 39 Mar 21 00:00 /usr/bin/nodejs-yarn ->
../lib/node_modules_19/yarn/bin/yarn.js
If yarn should be pinned to a node version, please rebuild yarn when
there's a major version change. And it would be nice if there's a
mechanism to detect such a breakage. I.e. a nodejs(abi) version or
something like that.
AFAICS nodejs is generally broken in rawhide (both nodejs20 and nodejs18),
i.e. just
$ node
> <type random chars and press backspace a couple of times>
Segmentation fault (core dumped)
gdb:
Thread 3 "node" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff2ffe6c0 (LWP 1565850)]
0x00007ffff57db195 in
v8::internal::compiler::SpecialRPONumberer::ComputeAndInsertSpecialRPO(v8::internal::compiler::BasicBlock*,
v8::internal::compiler::BasicBlock*) () from /lib64/libnode.so.115
Sandro
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
Vladimír Slávik <vslavik(a)redhat.com>
Software Engineer, Platform Engineering
Red Hat Czech, s.r.o.
5:42 a.m.
I’ll look into this today. In the meanwhile, can you force the use of
node-18?
On Tue, May 2, 2023 at 6:34 AM Vladimir Slavik <vslavik(a)redhat.com> wrote:
We're seeing the same with anaconda webui - any invocation of
node leads
to segmentation fault - npm, npx... nothing works.
On Tue, May 2, 2023 at 11:28 AM Sandro Mani <manisandro(a)gmail.com> wrote:
>
> On 02.05.23 11:24, Iñaki Ucar wrote:
>
> On Tue, 4 Apr 2023 at 16:23, Stephen Gallagher <sgallagh(a)redhat.com>
<sgallagh(a)redhat.com> wrote:
>
> On Tue, Apr 4, 2023 at 9:45 AM Sérgio Basto <sergio(a)serjux.com>
<sergio(a)serjux.com> wrote:
>
> On Thu, 2023-03-16 at 11:19 -0400, Stephen Gallagher wrote:
>
> On Wed, Mar 15, 2023 at 1:16 PM Jerry James <loganjerry(a)gmail.com>
<loganjerry(a)gmail.com>
>
> ...
>
> I found a problem related with yarnpkg rpm, the macro % __find_requires
> finds that yarn scripts uses and needs /usr/bin/node , which is added
> to the requires of rpm [1] and this makes yarnpkg pull nodejs (18) even
> when nodejs20 is installed .
> To avoid this rpm automatic requires, we may add to yarnpkg.spec [2]
>
> [2]
> %global __script_requires %{nil}
>
> [1]
> dnf repoquery yarnpkg --available --requires -q
> /usr/bin/bash
> /usr/bin/node
> /usr/bin/sh
>
>
> I'm not sure what you think is a bug here? Do you think `yarnpkg`
> should use *any* nodejs version that's installed? The whole point of
> the way this is broken down is that we have a default version (18, in
> this case) with the option to install 16 and 20 in parallel, but you
> have to do extra work if you want to *use* those non-default versions
> (such as patching shebang lines).
>
> This is broken again in rawhide:
>
> $ dnf -qy install yarnpkg
> $ ll /usr/bin/node*
> lrwxrwxrwx. 1 root root 7 Apr 28 00:00 /usr/bin/node -> node-20
> -rwxr-xr-x. 1 root root 28272 Apr 28 00:00 /usr/bin/node-20
> lrwxrwxrwx. 1 root root 39 Mar 21 00:00 /usr/bin/nodejs-yarn ->
> ../lib/node_modules_19/yarn/bin/yarn.js
>
> If yarn should be pinned to a node version, please rebuild yarn when
> there's a major version change. And it would be nice if there's a
> mechanism to detect such a breakage. I.e. a nodejs(abi) version or
> something like that.
>
> AFAICS nodejs is generally broken in rawhide (both nodejs20 and
> nodejs18), i.e. just
>
> $ node
> > <type random chars and press backspace a couple of times>
> Segmentation fault (core dumped)
>
> gdb:
>
> Thread 3 "node" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7ffff2ffe6c0 (LWP 1565850)]
> 0x00007ffff57db195 in
v8::internal::compiler::SpecialRPONumberer::ComputeAndInsertSpecialRPO(v8::internal::compiler::BasicBlock*,
> v8::internal::compiler::BasicBlock*) () from /lib64/libnode.so.115
>
> Sandro
>
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
--
Vladimír Slávik <vslavik(a)redhat.com>
Software Engineer, Platform Engineering
Red Hat Czech, s.r.o.
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
4:40 p.m.
On Tue, May 2, 2023 at 5:27 AM Sandro Mani <manisandro(a)gmail.com> wrote:
AFAICS nodejs is generally broken in rawhide (both nodejs20 and
nodejs18), i.e. just
$ node
> <type random chars and press backspace a couple of times>
Segmentation fault (core dumped)
gdb:
Thread 3 "node" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff2ffe6c0 (LWP 1565850)]
0x00007ffff57db195 in
v8::internal::compiler::SpecialRPONumberer::ComputeAndInsertSpecialRPO(v8::internal::compiler::BasicBlock*,
v8::internal::compiler::BasicBlock*) () from /lib64/libnode.so.115
It looks like this is an optimization bug in the compiler. The
segfault disappears when compiled with -O1, but occurs at -O2 and
higher. I'm going to try to track down the specific optimization
that's breaking it tomorrow, but as a stopgap measure I have Node.js
20 building in Rawhide with -O1.
2:02 p.m.
On Tue, May 2, 2023 at 5:40 PM Stephen Gallagher <sgallagh(a)redhat.com> wrote:
On Tue, May 2, 2023 at 5:27 AM Sandro Mani <manisandro(a)gmail.com> wrote:
> AFAICS nodejs is generally broken in rawhide (both nodejs20 and nodejs18), i.e.
just
>
> $ node
> > <type random chars and press backspace a couple of times>
> Segmentation fault (core dumped)
>
> gdb:
>
> Thread 3 "node" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7ffff2ffe6c0 (LWP 1565850)]
> 0x00007ffff57db195 in
v8::internal::compiler::SpecialRPONumberer::ComputeAndInsertSpecialRPO(v8::internal::compiler::BasicBlock*,
v8::internal::compiler::BasicBlock*) () from /lib64/libnode.so.115
>
It looks like this is an optimization bug in the compiler. The
segfault disappears when compiled with -O1, but occurs at -O2 and
higher. I'm going to try to track down the specific optimization
that's breaking it tomorrow, but as a stopgap measure I have Node.js
20 building in Rawhide with -O1.
Well, narrowing that down was a real pain:
https://github.com/nodejs/node/issues/47865
I'll build without the offending optimizations for the time being.
6:24 a.m.
On Tue, May 2, 2023 at 5:24 AM Iñaki Ucar <iucar(a)fedoraproject.org> wrote:
On Tue, 4 Apr 2023 at 16:23, Stephen Gallagher <sgallagh(a)redhat.com> wrote:
>
> On Tue, Apr 4, 2023 at 9:45 AM Sérgio Basto <sergio(a)serjux.com> wrote:
> >
> > On Thu, 2023-03-16 at 11:19 -0400, Stephen Gallagher wrote:
> > > On Wed, Mar 15, 2023 at 1:16 PM Jerry James <loganjerry(a)gmail.com>
> ...
> > I found a problem related with yarnpkg rpm, the macro % __find_requires
> > finds that yarn scripts uses and needs /usr/bin/node , which is added
> > to the requires of rpm [1] and this makes yarnpkg pull nodejs (18) even
> > when nodejs20 is installed .
> > To avoid this rpm automatic requires, we may add to yarnpkg.spec [2]
> >
> > [2]
> > %global __script_requires %{nil}
> >
> > [1]
> > dnf repoquery yarnpkg --available --requires -q
> > /usr/bin/bash
> > /usr/bin/node
> > /usr/bin/sh
> >
>
> I'm not sure what you think is a bug here? Do you think `yarnpkg`
> should use *any* nodejs version that's installed? The whole point of
> the way this is broken down is that we have a default version (18, in
> this case) with the option to install 16 and 20 in parallel, but you
> have to do extra work if you want to *use* those non-default versions
> (such as patching shebang lines).
This is broken again in rawhide:
$ dnf -qy install yarnpkg
$ ll /usr/bin/node*
lrwxrwxrwx. 1 root root 7 Apr 28 00:00 /usr/bin/node -> node-20
-rwxr-xr-x. 1 root root 28272 Apr 28 00:00 /usr/bin/node-20
lrwxrwxrwx. 1 root root 39 Mar 21 00:00 /usr/bin/nodejs-yarn ->
../lib/node_modules_19/yarn/bin/yarn.js
This is a bug in nodejs-packaging; it should always have been
installing to node_modules_20, but the %nodejs_sitearch variable is
wrong. I'll get that fixed.
If yarn should be pinned to a node version, please rebuild yarn when
there's a major version change. And it would be nice if there's a
mechanism to detect such a breakage. I.e. a nodejs(abi) version or
something like that.
We have exactly that. The version of nodejs(abi) matches the output of
`/usr/bin/node -p process.versions.modules` (which is also the version
suffix of libnode)
That being said, you are correct that it should be rebuilt when we do
a major version change (i.e. 18->20). If yarnpkg had been using
`Requires:
--
Iñaki Úcar
358
days inactive
408
days old
15 comments
6 participants
participants (6)
-
Iñaki Ucar -
Jerry James -
Sandro Mani -
Stephen Gallagher -
Sérgio Basto -
Vladimir Slavik