FS#74278 - [apm] Force me to be stuck in Node v16 instead of latest
Attached to Project:
Community Packages
Opened by Axel Navarro (navarroaxel) - Wednesday, 30 March 2022, 11:46 GMT
Last edited by Caleb Maclennan (alerque) - Monday, 22 August 2022, 11:13 GMT
Opened by Axel Navarro (navarroaxel) - Wednesday, 30 March 2022, 11:46 GMT
Last edited by Caleb Maclennan (alerque) - Monday, 22 August 2022, 11:13 GMT
|
Details
Description:
In this change https://github.com/archlinux/svntogit-community/commit/c4849b77116e0637c9282af18567c428507374eb depends=('nodejs>=10') was replaced with depends=(nodejs-lts-gallium) This force the users to use a specific nodejs package. Additional info: * package version(s) apm 2.6.5-1 or latert * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: In a clean Arch Linux installation - Install nodejs package via pacman. - Install atom package, the apm 2.6.5-2 will be installed as a dependency. - Pacman prompt to confirm replacing nodejs with nodejs-lts-gallium because it's in conflict. |
This task depends upon
Closed by Caleb Maclennan (alerque)
Monday, 22 August 2022, 11:13 GMT
Reason for closing: Won't fix
Additional comments about closing: Package dropped to AUR.
Monday, 22 August 2022, 11:13 GMT
Reason for closing: Won't fix
Additional comments about closing: Package dropped to AUR.
Now that the bump to Electron 11 is past it might be easier to work out how to patch for Nodejs 17+, but I don't have more time to sink into this right now. Again patches welcome!
If it would help anybody I think I could also do with with depends=('nodejs<17') so that older node-lts packages could be used as well. I only locked it to gallium because that was the newest one I could get to work. If being able to use old ones is useful let me know.
BTW, checking the GitHub repo for apm, only v12 and v14 is officially supported in the CI workflow.
However I can't say the same for atom itself. My attempts to build this worked fine for the cli package manager, but trying to compile atom using atm when built with a newer nodejs failed. That's the deal breaker right now as for as I know. Happy to be proven wrong or see patch that makes it work.
The culprit seems to be the fs-admin module, but I honestly don't have time to debug this right now. For my purposes using the LTS release isn't the end of the world and I have a 3 day old daughter to care for in my "spare" time.
Again I'm happy to accept patches if anybody can make apm+atom both build and cooperate.