Re: nodejs broken?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2023-03-16 at 11:19 -0400, Stephen Gallagher wrote:
> On Wed, Mar 15, 2023 at 1:16 PM Jerry James <loganjerry@xxxxxxxxx>
> wrote:
> > 
> > On Wed, Mar 15, 2023 at 11:09 AM Jerry James <loganjerry@xxxxxxxxx>
> > 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@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

-- 
Sérgio M. B.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux