V Thu, Dec 04, 2025 at 12:33:54PM +0100, Jan Stanek napsal(a): > Hi all, > in the process of polishing the upgrade path > for the nodejs metapackage proposal [1], > I've created a COPR [2] to ensure we can cleanly upgrade > from the current nodejs packages (that currently ship NodeJS v22.x) > to the versioned package names (nodejs22) and meta-package (nodejs) > combination. > However, dnf keeps behaving differently than I would expect, > and I'm at the end of ideas of what might be wrong. > > What I would expect: `dnf install nodejs` will select nodejs metapackage > for install, which pulls nodejs22 as a dependency. > > What happens: `dnf install nodejs` installs nodejs22 directly. > I confirm it behaves like that. A workaround is asking for a package name "nodejs.noarch". It maybe has something to do with how DNF5 distinguishes arguments as package names, provides, file names, etc. There is a heavy historical baggage how it should be done and it's quite possible you found an unwanted side effect of it.
I think it's a bug, so feel free to report a bug report. In upstream are greater experts than me. -- Petr
signature.asc
Description: PGP signature
-- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
