@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+T3s|4
+cumlord
+dr|z3d
+eche|off
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb
Chrono
Conserje
Daddy
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest40164
Irc2PGuest74352
Irc2PGuest83356
Onn4l7h
Over1
Rogueone
Sisyphus
Sleepy
SlippyJoe_
Teeed
aargh
ac9f_
acetone_
b3t4f4c3__
bak83
combed_tree328
dr4wd3
duanin2
duck
eyedeekay_bnc
john231
makoto
marek22k
nilbog
not_bob_afk
ntty
orignal_
poriori
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657_
uop23ip
vivid_re1
w8rabbit
x74a6
xHarr
eyedeekay
Better late than never: geti2p.net/en/blog/post/2025/10/16/new-i2p-routers
eyedeekay
also sam3 and goSam are officially retired, users of sam3 should migrate to go-sam-go which should be pretty seamless, the API's are almost identical, goSam users will get a compatibility tool soon which will forward from goSam API calls to go-sam-go Primary Session calls
zzz
nice post eyedeekay 10/10 no notes
eyedeekay
Thanks worked hard on it
zzz
eche|off, eche|on, eyedeekay I just got the first email about 39C3 vouchers, I asked for 10 as usual
eyedeekay
Same, I've set my alarm clock for voucher redemption day
eyedeekay
I'm going to do a workshop on embedded routers this year at CDC
eyedeekay
Last year's was *packed*
eyedeekay
And it was last-minute
eyedeekay
About readiness/planning session for PRs do you want to do that here or DMs
zzz
lets do it here, maybe there's other stuff to talk about elsewhere at some point
zzz
you got a voucher mail too? do we have two batches?
eyedeekay
OK sounds good to me
eyedeekay
I was pinged by ech, I don't think we got 2 batches
zzz
ok. I assume ech is in charge again, so when I get the voucher email I'll send it to him
zzz
so, what's the PR status? I see you merged the SAM one. Is the PR GUI still broken?
eyedeekay
Yes PR GUI still broken, I am doing review locally for the time being
zzz
ok. when I mention branch xxx you call it zzz-xxx and sometimes I see it that way in the gui, not sure if you're doing the renaming or that's some artifact of the brokenness?
eyedeekay
I was satisfied with the jetty12 code I read but did not understand the config issues involved so I need to re-review that one briefly before merging it, I have it next
eyedeekay
I think that particular phenomenon is because I pull in your branch which prefixes it with the remote name, push it back to mine, and reopen the PR to test the broken PR view, so an artifact but a known one
zzz
ok, so harmless
eyedeekay
So if I name your fork `zzz` in my git config your branch becomes `zzz-jetty12`
zzz
so on jetty 12. The rebased and current branch is jetty12-rb
zzz
it's ready to merge, if you're ok with the list of things that still don't work, posted at zzz.i2p/topics/3704
eyedeekay
Yeah
zzz
deb packages, https jetty, cgi-bin jetty, zzzot, snark standalone
zzz
there's no going back, and I'd say an early december release is still questionable
zzz
depends on what turns up in the testing
eyedeekay
I don't want to do it from Europe so I am beginning to think January, or Dec 14-21 at the earliest
zzz
I'll probably fix the deb packages first, post-merge, then snark standalone, then zzzot
zzz
I'll also need you to review/test your plugins for any jetty-stuff, not sure if you have any?
zzz
I'm not giving up on early Dec. yet, let's keep aiming for that, but knowing that it's probably 50/50
zzz
agreed if we miss early Dec. it probably slips all the way to mid-Jan
zzz
you should coordinate with orignal_ because if we expect to miss early Dec. they may want to do a release without us
eyedeekay
I don't have any jetty stuff in mine IIRC, just DTG and ShellService, but I will double check
eyedeekay
deb seems important to fix early, after merge is fine
eyedeekay
I think I can live with all that re: still doesn't work
zzz
re: deb I assume that without it some CI and docker is temporarily broken
zzz
it's just a question of creating the new builds and options. trixie is the only one that has jetty 12 in it. I though Ubuntu Questing had it also? but it's gone now, or I mis-remembered
zzz
even trixie jetty 12 doesn't have all we need, they omitted some things from the package, so it's messy
zzz
I'm also going to add a dependency on bcprov (bouncycastle) which we're bundling onw
eyedeekay
Docker should live but the CI might squawk
zzz
so there's going to be quite a shakeup of the combinations
zzz
where are you with the mlkem-precalc PR (originally 519). It's tiny. I re-pushed the branch a couple days ago at dr|z3d suggestion, not sure if that did anything
zzz
you may wish to merge that one before jetty 12, or not, doesn't really matter
eyedeekay
My instinct was to do the bigger one first and front-load the potential disruptions
zzz
that's fine. I'm kinda stuck until jetty12 is merged because I've updated most of my routers while testing the migration
eyedeekay
Conflicts etc
zzz
while all my other WIP is in a different workspace
zzz
as long as you do updaterWithJetty you can go back and forth between 9 and 12, but any jetty eepsites won't work
zzz
you can just disable them on /configclients to stop the complaining
zzz
so what's the ETA for the jetty12-rb merge?
eyedeekay
Thanks mine runs on jetty so I'll have to be careful
zzz
better to test on routers without a jetty eepsite first. It will still do the migration even if not running, or unused
eyedeekay
Let's call it tomorrow morning, all other things being equal. I want to look at it again and run it a while again
eyedeekay
But I don't forsee any reason not to merge it in the next 24 hours
zzz
ok. I bumped to -1 yesterday on top of the SAM merge, so give it a -2. Most importantly, tell us when you do it, and I'll do a post on zzz.i2p
zzz
I did checkin the jetty 12 jars and remove the jetty 9 jars, so it should just build without downloading anything
eyedeekay
Excellent thanks
dr|z3d
anyways, pushing that branch to git fixed the merge issue, zzz.
dr|z3d
"This pull request can be merged automatically."