[10:56:30] heads-up oncallers - we're about to shift some rest-gateway traffic from mw-api-int to mw-api-ext. it's only about 150 rps or so usually (https://grafana.wikimedia.org/goto/AHrSjz6Hg?orgId=1) [11:39:29] done, no major impact [11:57:04] hnowlan: My desire for things to go in the right bucket is now satiated for a few days [16:34:56] something seems off in apt1002 trixie repo: checkupdate fails with "aptmethod error receiving 'https://deb.nodesource.com/node_22.x/dists/trixie/InRelease'" [16:55:28] I suspect some versions might have vanished from nodesource.com... node_20 and bookworm is still working fine [16:55:33] dhinus: that link is a 404 in the browser [16:56:03] mutante: it was added to our config 1 month ago, so I suspect it worked initially [16:56:10] but is not working anymore [16:56:34] which is also preventing me from updating unrelated repos, because reprepro just bails out [16:57:18] full context: I am trying to update the "tofu" package using "reprepro --component thirdparty/tofu checkupdate trixie-wikimedia" [16:58:46] dhinus: yea.. so.. following the link chain.. starting at https://deb.nodesource.com/ and then -> https://github.com/nodesource/distributions -> https://nodesource.com/products/distributions selecting Debian.. there is just no trixie [16:59:31] maybe it means you have to use version 24 instead of 22? [16:59:51] per https://raw.githubusercontent.com/nodejs/Release/main/schedule.svg?fm=jpg&q=80&w=770&h=440 [17:00:08] brb [17:01:07] seems weird that they say version 24/25 are "current" but at the same time there is no version above 22 in the drop-down on their distributions page [17:01:23] either way, seems like an upstream issue, not with our repi [17:01:26] reprepro [17:04:22] yep definitely upstream, still annoying... I guess I can try waiting to see if the packages magically reapper upstream [17:04:26] otherwise we'll have to update our config [17:04:35] *reappear [17:05:20] this type of issue seems like you should not be the only one to ask about it [17:05:35] maybe try searching existing upstream bugs first [17:06:23] just to figure out if this is an accident.. as a minimum we would except version 24 to be selectable?? [17:10:51] yeah I'm also surprised... I tried a quick search in https://github.com/nodesource/distributions/issues/ and google but didn't find anything [17:11:10] I filed T406623 and am going to comment out the update stanza to unblock the unrelated work this is blocking [17:11:10] T406623: nodesource node22 apt mirror is broken - https://phabricator.wikimedia.org/T406623 [17:11:31] taavi: thanks! [17:11:56] mutante: https://deb.nodesource.com/node_24.x/dists/trixie/Release is also 404, but https://deb.nodesource.com/node_24.x/dists/nodistro/Release is working [17:12:35] https://gerrit.wikimedia.org/r/c/operations/puppet/+/1194252 [17:12:52] taavi: CI failing for some reason I don't understand [17:13:02] maybe just rebase? [17:13:06] dhinus: my local puppet.git clone was out of date, fixed with a rebase [17:13:17] (see PS2) [17:13:20] ack, +1d [17:14:11] merging, want me to pull the packages now as well? [17:14:25] (the pull the tofu ones to trixie, I mean) [17:14:48] yes please [17:14:52] I'm going offline in a few mins :) [17:16:11] dhinus: #nodejs here on IRC is pretty big. maybe asking there will shed some more light on it [17:18:25] mutante: that might work... I'm away until next week though, so I'll let somebody else investigate :)