You are not logged in.
Hello,
I tried upgrading and I got this:
resolving dependencies...
looking for conflicting packages...
:: nodejs-23.8.0-4 and nodejs-lts-gallium-16.20.2-1 are in conflict. Remove nodejs-lts-gallium? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: nodejs-23.8.0-4 and nodejs-lts-gallium-16.20.2-1 are in conflict
I answered NO to the prompt if I want to remove nodejs-lts-gallium and it failed.
Then I tried answer YES, and it failed too.
:: nodejs-23.8.0-4 and nodejs-lts-gallium-16.20.2-1 are in conflict. Remove nodejs-lts-gallium? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing nodejs-lts-gallium breaks dependency 'nodejs-lts-gallium' required by apm
I searched the package on Arch website but it doesn't exist. And the apm is not an existing package neither.
I tried removing nodejs-lts-gallium but I got this:
user@ArchPC ~ $ sudo pacman -Rs nodejs-lts-gallium
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing nodejs-lts-gallium breaks dependency 'nodejs-lts-gallium' required by apm
:: removing nodejs-lts-gallium breaks dependency 'nodejs' required by node-gyp
:: removing nodejs-lts-gallium breaks dependency 'nodejs' required by nodejs-nopt
:: removing nodejs-lts-gallium breaks dependency 'nodejs' required by npm
:: removing nodejs-lts-gallium breaks dependency 'nodejs' required by semver
I don't know, I don't even use nodejs, the system must have installed all those packages as dependencies at some point.
Has anyone any idea about this? How can I upgrade without failing?
Thanks everyone!
Last edited by Businek (2025-02-23 15:58:52)
Offline
There is no package called 'apm' in either the repos or in the AUR. Do you need it?
Online
There is no package called 'apm' in either the repos or in the AUR. Do you need it?
No I don't need it, I have it and I can't remove it.
Offline
Why can't you remove it?
Online
Wow, nevermind. I just made it. Weeks of this issue and now I resolved just after posting this. Sorry guys. Resolved!
I had Atom still installed and it had apm package as dependency. The apm package was the problem because it's not in the repositories anymore.
Last edited by Businek (2025-02-22 14:00:44)
Offline
If you're statisifed with the outcome, please prepend [Solved] to the thread title (edit first post)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline