<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">Le mar. 9 sept. 2025 à 13:19, Santiago Vila <<a href="mailto:sanvila@debian.org">sanvila@debian.org</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Sep 09, 2025 at 10:22:26AM +0200, Jérémy Lal wrote:<br>
<br>
> So in any case, one must rebuild all reverse build-dependencies of nodejs<br>
> before anything,<br>
> and I currently don't have a solution to do that (my pc is old, and I broke<br>
> salsa once already in the last month).<br>
> But that doesn't stop me from preparing an update to nodejs, so I'll<br>
> propose one this week.<br>
<br>
Great. Please let me know when such update is ready. Maybe I could<br>
check how many reverse build-dependencies will be broken in advance,<br>
so that they are also fixed at least in the same point release.<br></blockquote><div><br></div><div>Will do.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
(There is also debusine, but there are 1800 packages potentially<br>
affected, and I still don't know what are the terms of use).<br></blockquote><div><br></div><div>I didn't have the time yet to find out how to make debusine rebuild</div><div>all reverse dependencies.</div><div>However, they do have a workflow for running autopkgtests, which I will use to get a first idea.</div><div><br></div></div></div>