<PurpleSym>Yeah, smells like alot of manual work – at least without using the “binary” NPM importer. <PurpleSym>Do you want to move the affected packages to guix-science? <rekado>I don’t know if it’s a good idea to add a package to guix-science that has a slightly older version in guix proper. <rekado>but maybe that’s what I’ll end up doing <rekado>which of the npm importers out there did you use for the rstudio javascript? <PurpleSym>It’s commit c795137b3ab57a2150c2414c6e1c427aaf127ded. <PurpleSym>But you’re right wrt having the same package in Guix proper and guix-science. It only works well for leaf packages, with no dependents. Otherwise you’ll get nasty profile conflicts. *rekado prepares a new iteration of the r-updates branch ***Server sets mode: +nt
<civodul>rekado: tip of the day: if you send the patch series to debbugs, qa.guix will pick it up and build it :-) <rekado>it’s 200+ patches. Still a good idea to send it to debbugs? <rekado>(I’ve been building this kind of thing “manually” on ci.) ***Noisytoot_ is now known as Noisytoot