im just back from a vacation of 1 month and went to update my packages by using yay but it fails anyone know how to fix
#update failed
dark herald
somber cloak
So the error you have are?
nodejs-lts-jod-22.18.0-1.1 and nodejs-lts-iron-20.19.4-1.1 are in conflict
I mean, nodejs are really crap but you can't have both of those packages installed at the same time.
What prevents you from remove nodejs-lts-iron (which are the older one)?
dark herald
idk how they are there i didnt install them
somber cloak
idk how they are there i didnt install them
Ok, could you try remove the one I suggests?
dark herald
which one
dark herald
ok thx
dark herald
https://discord.com/channels/399812551963049995/1406597551393865738/140659843659...
:: removing nodejs-lts-iron breaks dependency 'nodejs' required by asar
:: removing nodejs-lts-iron breaks dependency 'nodejs' required by gemini-cli
:: removing nodejs-lts-iron breaks dependency 'nodejs' required by node-gyp
:: removing nodejs-lts-iron breaks dependency 'nodejs' required by nodejs-nopt
:: removing nodejs-lts-iron breaks dependency 'nodejs>=20.17.0' required by npm
:: removing nodejs-lts-iron breaks dependency 'nodejs' required by semver
:: removing nodejs-lts-iron breaks dependency 'nodejs' required by typescript
:: removing nodejs-lts-iron breaks dependency 'nodejs' required by yarn
:: removing nodejs-lts-iron breaks dependency 'nodejs>=18' required by zed
somber cloak
Yeah, it is because nodejs-lts-jod have not been installed which would replace those needs
@dark herald What error do you get if you do: pacman -S nodejs-lts-jod
I would guess it would complain about iron being in conflict but does it suggest removing iron?
west ocean
idk how they are there i didnt install them
pacman -Sii <package> to see reverse dependencies. That will tell you what has pulled it
although that pacman log also tells you
somber cloak
`pacman -Sii <package>` to see reverse dependencies. That will tell you what has...
Well. I have a guess: zed
dark herald
west ocean
`pacman -Sii <package>` to see reverse dependencies. That will tell you what has...
I made this 😊
pacman -Qq $(paru -Sii nodejs-lts-jod | awk '/Required/' | cut -d ":" -f 2) 2>/dev/null
``` gets the reverse deps of a package and checks them against what you have installed
west ocean
im just back from a vacation of 1 month and went to update my packages by using ...
Would it be possible to get this again, but run through ansifilter first?
It's very hard to parse
https://termbin.com/y0i6 I did it myself
Righty, so what appears to be happening here is that heroic-games-launcher is pulling nodejs-lts-jod-22.18.0-1.1 as a build dep
But that clashes with the iron version that zed wants
There are a few ways around this that I can imagine
- remove nodejs-lts-iron entirely ignoring the warnings with -Rdd, then installing jod should be fine. zed does not depend on a specific nodejs-lts version, just >=nodejs18 which 22.18.0 definitely is
- remove zed temporarily. The zed/iron interdependency is the issue, so getting rid of zed should allow the upgrade to complete. Then you can reinstall zed
The core cause of this issue is that you cannot have two versions of nodejs around on arch at one time
Something wants -jod, but -iron already exists
Pacman can't install multiple versions, so it suggests removing the conflict
somber cloak
The core cause of this issue is that you cannot have two versions of nodejs arou...
It is a common problem. I don't know if pacman have some operator for replacing a package
west ocean
However, that would break zed, so pacman stops and you have to intervene
somber cloak
In theory, if there are no conflicts, it should suggest replacement if you do: pacman -S nodejs-lts-jod
@dark herald Did you try it and can you tell which error you are getting?
west ocean
I like that idea, digging out this conflict from the mass update might allow it to fix itself
Worth trying before my far hackier suggestions :D
somber cloak
Yeah, I would do the hacky solution myself. But that is also because I have an understanding what I am doing and can revert back again. So I am not keen to guide others to do that kind of thing. Perhaps less risky would just be uninstall zed and the problematic packages and then reinstall them after new nodejs
But I guess we lost @dark herald for now. 🙂
dark herald
In theory, if there are no conflicts, it should suggest replacement if you do: `...
thanks that works
stray marlinBOT
julemand101 received a thank you cookie!
dark herald
now ill continue the update and see if theres more
west ocean
Does the explanation make sense?
dark herald
no but it doesnt need to
west ocean
as long as compooter compoot then 👍
dark herald
why is gcc exploding my pc
zealous wraith
compiling gcc basically is like a spoiled brat child, it uses every single drop of cpu usage lol
zealous wraith
if you're updating the base gcc package, it does need to compile to update
just a con whenever gcc appears during your regular system upgrades 😔
dark herald
isnt there like gcc bin
zealous wraith
gcc9-bin exists ig, not sure about the latest release
