On Wed, Aug 10, 2022 at 10:04 AM Josh Boyer jwboyer@redhat.com wrote:
On Wed, Aug 10, 2022 at 9:34 AM Ewoud Kohl van Wijngaarden ewoud+centos@kohlvanwijngaarden.nl wrote:
On Wed, Aug 10, 2022 at 07:30:34AM -0400, Josh Boyer wrote:
On Wed, Aug 10, 2022 at 6:31 AM Leon Fauster via CentOS-devel centos-devel@centos.org wrote:
C8 has
nodejs-10.24.0-1.module_el8.3.0+717+fa496f1d.x86_64
CS8 has
nodejs-10.23.1-1.module_el8.4.0+645+9ce14ba2
should CentOS Stream 8's package version not be at least == C8?
The nodejs:10 Application Stream was retired in April 2021 per https://access.redhat.com/support/policy/updates/rhel-app-streams-life-cycle
As CentOS Stream is the development space for the next minor release of RHEL, this ran into an awkward timing scenario. The nodejs-10.24.0-1.module_el8.3.0+717+fa496f1d.x86_64 build is from an errata after the RHEL 8.3 release, but the release of RHEL 8.4 was in May 2021 which fell after the end of support for the nodejs:10 module. Nothing was ever intended to ship in RHEL 8.4 for nodejs:10, therefore CentOS Stream 8 has no newer builds to work with.
In all cases, I would recommend migrating to a supported version of nodejs.
The awkward bit is that nodejs:10 is still marked as the default module in CS8, even though it's unsupported. This is not the only example since the same can be said for the redis:5 and maybe more.
Yes, that is indeed awkward, but it is also by design. This is one of the things we learned and adjusted in RHEL 9/CentOS Stream 9.
Unfortunately, in the case of both nodejs and nginx, this is still a problem on CentOS Stream 9.
Personally, I would have preferred there to be no default streams for these given the lifecycle setup for it. Alas...
-- 真実はいつも一つ！/ Always, there's only one truth!