Re: Please help doing the three more checks required for releasing 1493!
"Dr. Arne Babenhauserheide" writes: 1. [X] auto update on windows — thanks David and brick! ✓ 2. [X] auto update on GNU/Linux — thanks to Nicole Jones! ✓ 3. [X] installer on windows — thanks to HornyCow! ✓ 4. [X] installer on GNU/Linux — thanks David! ✓ Thanks to Nicole Jones from Sone it’s all tested now! Thank you! Proceeding to release. Best wishes, Arne -- Unpolitisch sein heißt politisch sein, ohne es zu merken. draketo.de signature.asc Description: PGP signature
Re: Please help doing the three more checks required for releasing 1493!
"David Dernoncourt" writes: >>> 1. [ ] auto update on windows > > I tested auto-update on one of my Windows nodes (with Java 11) and it > successfully auto-updated to 1493. Thank you! With your report we’re just one check away from releasing: >>> 1. [X] auto update on windows — thanks David! ✓ >>> 2. [ ] auto update on GNU/Linux >>> 3. [X] installer on windows — thanks to HornyCow! ✓ >>> 4. [X] installer on GNU/Linux — thanks David! ✓ > Another of my Windows nodes, running 1492 and on which I didn't touch > the update key, received an update notice too: was the update released > already? (this node is on manual update and I didn't apply it yet) Did it update? If you have a darknet connection between them, it will get the information that a new version is available, but should not accept it, because the update keys do not match. Best wishes, Arne -- Unpolitisch sein heißt politisch sein, ohne es zu merken. draketo.de signature.asc Description: PGP signature
Re: Please help doing the three more checks required for releasing 1493!
Hi, >> 1. [ ] auto update on windows I tested auto-update on one of my Windows nodes (with Java 11) and it successfully auto-updated to 1493. Another of my Windows nodes, running 1492 and on which I didn't touch the update key, received an update notice too: was the update released already? (this node is on manual update and I didn't apply it yet) On Mon, Apr 4, 2022, at 21:19, Dr. Arne Babenhauserheide wrote: > Hi, > > > after fixing a bug that turned up in testing (wrong CHK in > dependencies.properties that got aborted because it did not match the > correct sha256 — I’m glad we double-check!), we need *three more tests* > not done by me to be able to finally push 1493 to the website and to > auto-update (because you seriously don’t want me to be the only one who > tests this). > > > Please help get the release out! > > > Required tests: > >> 1. [ ] auto update on windows >> 2. [ ] auto update on GNU/Linux >> 3. [ ] installer on windows >> 4. [X] installer on GNU/Linux — thanks David! ✓ > > > Practically this means: > > 1. If you have a windows node, go to >http://127.0.0.1:/config/node.updater?fproxyAdvancedMode=2 >then put the new testing key into the field that says >"Where should Freenet look for updates?" > > USK@BrNh~RNzsl3zQueAH0Ed8bgF88kZHa4AH64RNKjsCU4,~hvYp2qtiUUXk4r2AuwMbiNvLiBcPhl9Nt4lsrvaYn8,AQACAAE/jar/1492 >Then restart your node. >It should update to 1493. Please report if you run into trouble! >Also please report if it works! > > 2. Do the same on GNU/Linux. Yes, I did it, but if I’m the only one who >does it, how should you trust Freenet to actually work? > > 3. Download the installer on Windows, run it, start the installed >Freenet, and report errors you see — or that it works. >The installer: > > CHK@07dc2TkhlpuQBJV2WEK1z2SAycEiv07zbtZC9A4keQs,34RYMOAnxxIkGAyLIfC8qNoSNuZpPRjWtvS68aZ5rbQ,AAMC--8/FreenetInstaller-1493.exe >or > > https://github.com/freenet/fred/releases/download/build01493/FreenetInstaller-1493.exe > > > Once these three checks are done (and worked), I can finally push the > update. > > > … and once I pushed it, please run verify-build to ensure that what I > released is actually what’s in the sources! > > - https://github.com/freenet/scripts/blob/master/verify-build > > > Let’s get this release out together! > > > Best wishes, > Arne > -- > Unpolitisch sein > heißt politisch sein, > ohne es zu merken. > draketo.de > > Attachments: > * signature.asc
Please help doing the three more checks required for releasing 1493!
Hi, after fixing a bug that turned up in testing (wrong CHK in dependencies.properties that got aborted because it did not match the correct sha256 — I’m glad we double-check!), we need *three more tests* not done by me to be able to finally push 1493 to the website and to auto-update (because you seriously don’t want me to be the only one who tests this). Please help get the release out! Required tests: > 1. [ ] auto update on windows > 2. [ ] auto update on GNU/Linux > 3. [ ] installer on windows > 4. [X] installer on GNU/Linux — thanks David! ✓ Practically this means: 1. If you have a windows node, go to http://127.0.0.1:/config/node.updater?fproxyAdvancedMode=2 then put the new testing key into the field that says "Where should Freenet look for updates?" USK@BrNh~RNzsl3zQueAH0Ed8bgF88kZHa4AH64RNKjsCU4,~hvYp2qtiUUXk4r2AuwMbiNvLiBcPhl9Nt4lsrvaYn8,AQACAAE/jar/1492 Then restart your node. It should update to 1493. Please report if you run into trouble! Also please report if it works! 2. Do the same on GNU/Linux. Yes, I did it, but if I’m the only one who does it, how should you trust Freenet to actually work? 3. Download the installer on Windows, run it, start the installed Freenet, and report errors you see — or that it works. The installer: CHK@07dc2TkhlpuQBJV2WEK1z2SAycEiv07zbtZC9A4keQs,34RYMOAnxxIkGAyLIfC8qNoSNuZpPRjWtvS68aZ5rbQ,AAMC--8/FreenetInstaller-1493.exe or https://github.com/freenet/fred/releases/download/build01493/FreenetInstaller-1493.exe Once these three checks are done (and worked), I can finally push the update. … and once I pushed it, please run verify-build to ensure that what I released is actually what’s in the sources! - https://github.com/freenet/scripts/blob/master/verify-build Let’s get this release out together! Best wishes, Arne -- Unpolitisch sein heißt politisch sein, ohne es zu merken. draketo.de signature.asc Description: PGP signature
