http-parser has been unmaintained for several years [1] and nodejs now uses llhttp [2]. Fedora and Arch Linux are working on removing their http-parser packages [3,4]. [1] https://github.com/nodejs/http-parser/issues/522 [2] https://github.com/nodejs/llhttp [3] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/466TNSUQW454A2WSDONN2EYKHFM2S3IK/ [4] https://archlinux.org/todo/move-to-llhttp-from-http-parser/
Hi, just wanted to bring this issue back to attention. We've recently started our first tests with Rockylinux 10 / EL10, which has removed http-parser from the repos, so Slurm's configure complains and doesn't build the slurmrestd. As llhttp is only introduced to the repos of EL10 (and EPEL for EL9) and most of our clusters are still Rockylinux 8 / 9 based, a direct replacement of http-parser with llhttp would create the opposite issue. But maybe there is a way to make the codebase accept llhttp and http-parser, depending on what's available? So far, one still gets around the issue by manually installing the http-parser / http-parser-devel RPMs from EL9 into EL10, but I would call this more of a band-aid than a fix. As always, thank you and keep up the great work. Best regards, Timon Vogt (GWDG)
