@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+dr|z3d
+goose2_
+hagen
+orignal
+postman
+weko
An0nm0n
Arch
Danny
DeltaOreo
DiCEy1904
FreefallHeavens
Irc2PGuest11229
Irc2PGuest48909
Irc2PGuest6753
Leopold
Nausicaa
Onn4l7h
PenguinDriver
SoniEx2
Teeed
acetone_
anon2
b3t4f4c3__
bak83
boonst
dr4wd3
eyedeekay_bnc
goose2
hk
itsjustme_
j6
no
not_bob_afk
numberwang
onon_
pisslord
poriori
profetikla
qend-irc2p
rapidash
shiver_
u5657
w8rabbit
x74a6
zzz
arm builds finished after 18 hours; the x390x backlog was twice as long as arm, so maybe by the end of today
zzz
eyedeekay, how did it go with the bundle?
zzz
and am I doing the website or are you?
eyedeekay
Smoothly once I got to that part, took about an hour all told
eyedeekay
I was going to undraft and update it this morning(like the next 30min), to try and get it on socials during our daytime
zzz
ok great. I just added the checksums to the blog draft
eyedeekay
Maven, Android, and mirrors are ready too
zzz
yay
zzz
I project the s390x build won't be done before I'm out for the day, so realistically tomorrow for PPA/deb
eyedeekay
Site should update in about half an hour
zzz
ppc64el 50 2366 jobs (7 hours)
zzz
riscv64 83 14806 jobs (5 days)
zzz
s390x 40 17010 jobs (2 days)
eyedeekay
Holy moley about risc64
eyedeekay
I'll make sure some of the regulars know about that timeline
zzz
we don't have riscv64 enabled
eyedeekay
Oh good
eyedeekay
So just 2 days
zzz
all in all it's a usual timeline, ppa 1-2 days after release, yes
zzz
but only because I jumped right on it yesterday
zzz
backlog is probably because somebody over there pushed the oracular button
zzz
we should be about halfway thru the s390x queue, I predict about 12-18 more hours
zzz
didn't want to try a partial copy, don't know if that works and copy is glitchy af anyway
zzz
eyedeekay, i2p.android.base does not have 2.5.1 or 2.5.2 checkins or tags, and no translation updates in 6 months. Are you doing that? Does android checklist need updating?
eyedeekay
look for i2p-android-2.5.2 it should be there, maybe I forgot to push the tag
zzz
last checkin 5/5
zzz
are you pulling and checking in translations each release?
zzz
because I just did tx pull and got 4 files
eyedeekay
I didn't do this one because there's a broken resource directory I need to fix, es_AR, it won't compile when I update that one
eyedeekay
Re: translations
zzz
then just keep that one out?
zzz
I don't see any translations updated since December
zzz
let's ensure we're taking the results of translator's efforts whenever possible
zzz
tx pull --use-git-timestamps
eyedeekay
Ack, updated the checklist
zzz
shall I go ahead and check in the 4 thranslations? none are es_AR
zzz
still no 2.5.1 tag
eyedeekay
Go ahead with the translations, I'll get the tag
dr|z3d
I nuked es_AT fwiw.
dr|z3d
*es_AR
dr|z3d
didn't appear to add much value beyond ES
zzz
eyedeekay, I see you're pulling i2p.i2p translations again on release day, that can gum things up if there's errors or malice, better to just do it at checkin deadline and let it stand
zzz
same can happen w/ android ofc
eyedeekay
OK
zzz
because some things are caught in 'ant release' which is a little late and annoying
zzz
which is really 'ant testscripts' which I always run after pulling. had to do one fixup this week
eyedeekay
GPlay update just went live
zzz
if it weren't for launchpad this would have been our fastest release in a while
zzz
quick dechunk bug postmortem:
zzz
- misread spec, wrote unit test based on misreading, tested extensively with it and it was perfect
zzz
- real world testing was mostly fine, didn't specifically try to test against nginx server
zzz
- transient errors may have been masked by onging attacks
zzz
- lenient parser meant it mostly worked anyway
zzz
- difficulty testing before the release because people didn't have the server-side support yet
zzz
- servers I control didn't run nginx or do chunking of static content
zzz
lessons: get the spec right, test better
zzz
(maybe) don't write parsers to be so lenient, at least for initial testing
dr|z3d
and have an nginx server to hand :)
zzz
incoming email:
zzz
Hello
zzz
I added the project repo to my machine and got a warning about the weak 1024 RSA key, heck, 2048 is weak too, I recommend upgrading to 4096
zzz
W: ppa.launchpadcontent.net/i2p-maintainers/i2p/ubuntu/dists/noble/InRelease: Signature by key 474BC46576FAE76E97C1A1A1AB9660B9EB2CC88B uses weak algorithm (rsa1024)
zzz
I checked, mine and idk's are 4096 but the maintainer one is indeed 1024
eyedeekay
Yeah I just got that one too
zzz
no idea how to update or if that would break everything
eyedeekay
There must be some path we can provide
zzz
I didn't set up the ppa to begin with, it was welterde
zzz
in 2009
zzz
not something to mess with right now ))
zzz
looks like we don't have to do anything
zzz
shall I reply to the guy or are you?
eyedeekay
I can handle it
zzz
ok thanks. seems like the warning is new and it's ubuntu's issue to fix, out of our hands
zzz
"no action is needed (or possible) from PPA owners"
zzz
ppc64el is finished, down to s390x
eyedeekay
Gitlab was down for about 45 seconds just now. It's back.
eyedeekay
disk issue