Re: final final test release of 1481
The insert is finally running. You can watch it spread in almost-realtime: http://127.0.0.1:/USK@IJtoXv08j4bpqh7IBSVtokneXPFqBhjD~IBWHJWo8KY,ttFryeQK7tkHHXcWc~6iW7WyEW8OWIxzBNHBr5Yc~MU,AQACAAE/watch-1481/-1/ The site is also available via my whitelisting inproxy (though the cache might serve outdated versions): https://d6.gnutella2.info/freenet/USK@IJtoXv08j4bpqh7IBSVtokneXPFqBhjD~IBWHJWo8KY,ttFryeQK7tkHHXcWc~6iW7WyEW8OWIxzBNHBr5Yc~MU,AQACAAE/watch-1481/-5/ Best wishes, Arne DC* writes: > Great news! I've been running 1481 without issues for weeks! > > Best regards > > On November 6, 2018 5:41:35 PM GMT-03:00, Arne Babenhauserheide > wrote: >>Hi Steve, >> >>Thank you very much! >> >>It’s finally time to insert the release! >> >>Best wishes, >>Arne >> >>Steve Dougherty writes: >> >>> I haven't tested beyond running the build that was originally tagged >>1481, (so c4b1caa16819937bc7c368f74e7deea16cc9b263 I think?) and have >>no reasons to suggest the release be further delayed. >>> >>> I was able to verify the build on an updated Debian Jessie VM, and >>set up doing the same with a Docker build, inspired by how Signal does >>it. It has to run sed to disable ECDSA or the TLS connection to >>download the Gradle wrapper will fail due to a Java bug apparently. The >>command Docker runs could be `./gradlew jar` were it not for that. The >>rest of my message is a log of doing so (the weird syntax for pwd is >>because of Fish shell): >>> >>> steve@monolith /tmp> git clone ~/Documents/Coding/freenet/fred >>> steve@monolith /tmp> cd fred >>> steve@monolith /t/fred (master)> wget >>https://gist.github.com/Thynix/f02f9ba33e296d037defd60972dd39fd/raw/55996e4ba863ba568efdc5d53d7a7bb3086a1723/build.sh >>> ... >>> steve@monolith /t/fred (master)> sudo docker run --rm --volume >>(pwd):/project --workdir "/project" openjdk:7-jdk bash build.sh >>> Downloading >>https://services.gradle.org/distributions/gradle-4.2.1-bin.zip >>>
Re: final final test release of 1481
Great news! I've been running 1481 without issues for weeks! Best regards On November 6, 2018 5:41:35 PM GMT-03:00, Arne Babenhauserheide wrote: >Hi Steve, > >Thank you very much! > >It’s finally time to insert the release! > >Best wishes, >Arne > >Steve Dougherty writes: > >> I haven't tested beyond running the build that was originally tagged >1481, (so c4b1caa16819937bc7c368f74e7deea16cc9b263 I think?) and have >no reasons to suggest the release be further delayed. >> >> I was able to verify the build on an updated Debian Jessie VM, and >set up doing the same with a Docker build, inspired by how Signal does >it. It has to run sed to disable ECDSA or the TLS connection to >download the Gradle wrapper will fail due to a Java bug apparently. The >command Docker runs could be `./gradlew jar` were it not for that. The >rest of my message is a log of doing so (the weird syntax for pwd is >because of Fish shell): >> >> steve@monolith /tmp> git clone ~/Documents/Coding/freenet/fred >> steve@monolith /tmp> cd fred >> steve@monolith /t/fred (master)> wget >https://gist.github.com/Thynix/f02f9ba33e296d037defd60972dd39fd/raw/55996e4ba863ba568efdc5d53d7a7bb3086a1723/build.sh >> ... >> steve@monolith /t/fred (master)> sudo docker run --rm --volume >(pwd):/project --workdir "/project" openjdk:7-jdk bash build.sh >> Downloading >https://services.gradle.org/distributions/gradle-4.2.1-bin.zip >> >.. >> Unzipping
Re: final final test release of 1481
Hi Steve, Thank you very much! It’s finally time to insert the release! Best wishes, Arne Steve Dougherty writes: > I haven't tested beyond running the build that was originally tagged 1481, > (so c4b1caa16819937bc7c368f74e7deea16cc9b263 I think?) and have no reasons to > suggest the release be further delayed. > > I was able to verify the build on an updated Debian Jessie VM, and set up > doing the same with a Docker build, inspired by how Signal does it. It has to > run sed to disable ECDSA or the TLS connection to download the Gradle wrapper > will fail due to a Java bug apparently. The command Docker runs could be > `./gradlew jar` were it not for that. The rest of my message is a log of > doing so (the weird syntax for pwd is because of Fish shell): > > steve@monolith /tmp> git clone ~/Documents/Coding/freenet/fred > steve@monolith /tmp> cd fred > steve@monolith /t/fred (master)> wget > https://gist.github.com/Thynix/f02f9ba33e296d037defd60972dd39fd/raw/55996e4ba863ba568efdc5d53d7a7bb3086a1723/build.sh > ... > steve@monolith /t/fred (master)> sudo docker run --rm --volume (pwd):/project > --workdir "/project" openjdk:7-jdk bash build.sh > Downloading https://services.gradle.org/distributions/gradle-4.2.1-bin.zip > .. > Unzipping > /root/.gradle/wrapper/dists/gradle-4.2.1-bin/dajvke9o8kmaxbu0kc5gcgeju/gradle-4.2.1-bin.zip > to /root/.gradle/wrapper/dists/gradle-4.2.1-bin/dajvke9o8kmaxbu0kc5gcgeju > Set
Re: final final test release of 1481
I haven't tested beyond running the build that was originally tagged 1481, (so c4b1caa16819937bc7c368f74e7deea16cc9b263 I think?) and have no reasons to suggest the release be further delayed. I was able to verify the build on an updated Debian Jessie VM, and set up doing the same with a Docker build, inspired by how Signal does it. It has to run sed to disable ECDSA or the TLS connection to download the Gradle wrapper will fail due to a Java bug apparently. The command Docker runs could be `./gradlew jar` were it not for that. The rest of my message is a log of doing so (the weird syntax for pwd is because of Fish shell): steve@monolith /tmp> git clone ~/Documents/Coding/freenet/fred steve@monolith /tmp> cd fred steve@monolith /t/fred (master)> wget https://gist.github.com/Thynix/f02f9ba33e296d037defd60972dd39fd/raw/55996e4ba863ba568efdc5d53d7a7bb3086a1723/build.sh ... steve@monolith /t/fred (master)> sudo docker run --rm --volume (pwd):/project --workdir "/project" openjdk:7-jdk bash build.sh Downloading https://services.gradle.org/distributions/gradle-4.2.1-bin.zip .. Unzipping /root/.gradle/wrapper/dists/gradle-4.2.1-bin/dajvke9o8kmaxbu0kc5gcgeju/gradle-4.2.1-bin.zip to /root/.gradle/wrapper/dists/gradle-4.2.1-bin/dajvke9o8kmaxbu0kc5gcgeju Set executable permissions for: /root/.gradle/wrapper/dists/gradle-4.2.1-bin/dajvke9o8kmaxbu0kc5gcgeju/gradle-4.2.1/bin/gradle Starting a Gradle Daemon (subsequent
Re: final final test release of 1481
(testing update key at the end) > On 2018-10-24 19:05, Arne Babenhauserheide wrote: >> Please give it some now hopefully truly final testing: >> >> https://github.com/freenet/fred/releases/tag/build01481 >> >> Installers: >> → *nix: >> https://github.com/freenet/fred/releases/download/build01481/new_installer_offline_1481.jar >> → Windows: >> https://github.com/freenet/fred/releases/download/build01481/FreenetInstaller-1481.exe >> >> (add .sig for the PGP signature, the OSX installer will follow once >> mrsteveman1 has time). The installers are updated, please test them again! >> I’m sorry that this adds another week to the release date. I’m also >> still waiting for confirmation by anonymous@6KMY4DVjZ… on FMS whether >> the breakage reported was due to missing the jna files. If that’s >> resolved, there are no more release blockers I know of. anonymous@6KMY4DVjZ… answered that the problems were indeed due to copying in the jar-file manually. When adding the libraries and and modifying wrapper.conf so that the libs are on the classpath, the update worked. >> I plan to upload this true true real final release to a new testing key >> the next days so we can do another full update cycle test (install 1480, >> change the update key, watch freenet update to 1481 over Freenet, >> celebrate). And then get this release truly fully done. Here’s the update key for the TESTING release which you can add on http://127.0.0.1:/config/node.updater?fproxyAdvancedMode=2 USK@dLxKiIFKlfhgdgkYNlHoGoSO~KWRYPTkdbWfznZyatg,OwghtrmoY5Mj~1pfUHbo308FHZyTVwXfEXNX5C2EKT8,AQACAAE/jar/1480 — ONLY FOR TESTING! REMOVE IT AFTERWARDS! Does the Java webstart installer of 1480 work for you? https://freenetproject.org/assets/jnlp/freenet.jnlp?1480 for me it currently takes ages to download the actual installer from github. With ages I mean, it takes minutes to download (with no progress) and then 5 more minutes until it shows the setup dialog. Something is broken there … (this is with icedtea-web, note that Oracle has removed webstart from Java 9, we’ll need to find out how to cope with that. Best wishes, Arne -- Unpolitisch sein heißt politisch sein ohne es zu merken signature.asc Description: PGP signature
Re: final final test release of 1481
Hey there, I'm gonna test the installers on *nix and windows and report back. Hopefully 1481 can be released soon. Best regards, On 2018-10-24 19:05, Arne Babenhauserheide wrote: > Hi, > > I had to add some more fixes to run.sh to ensure that the classpath > includes jna and jna-platform. I updated the pre-release with the new > files and added a note for those who update by copying in the jar: > >> This also means that you need jna-4.2.2.jar and jna-platform-4.2.2.jar >> in your freenet folder. The auto-updater takes care of that for you. >> If you update manually by copying in new jar-files, you need to adapt >> the classpath in wrapper.conf or in run.sh (if you do not use the wrapper). > > Please give it some now hopefully truly final testing: > > https://github.com/freenet/fred/releases/tag/build01481 > > Installers: > → *nix: > https://github.com/freenet/fred/releases/download/build01481/new_installer_offline_1481.jar > → Windows: > https://github.com/freenet/fred/releases/download/build01481/FreenetInstaller-1481.exe > > (add .sig for the PGP signature, the OSX installer will follow once > mrsteveman1 has time). > > Thanks to jamesaxl from #freenet on Freenode for finding this problem on BSD! > > > I’m sorry that this adds another week to the release date. I’m also > still waiting for confirmation by anonymous@6KMY4DVjZ… on FMS whether > the breakage reported was due to missing the jna files. If that’s > resolved, there are no more release blockers I know of. > > > I plan to upload this true true real final release to a new testing key > the next days so we can do another full update cycle test (install 1480, > change the update key, watch freenet update to 1481 over Freenet, > celebrate). And then get this release truly fully done. > > > Sidenote: the statistics site should soon work again. I switched pyProbe > from enum to enum34 to resolve a dependency conflict with the > cryptography package (that needs enum34, but user-installed enum can > override that and cause undecipherable errors). > > > Best wishes, > Arne > > > Arne Babenhauserheide writes: > >> Steve Dougherty writes: >>> Hooray! I was able to verify this build on my Debian Jessie box: >> Nice! Thank you for checking! >> >>> Thank you for your work, both of you! :) >> >> Thank you for verifying the build, and for your work on preparing the >> new keys! There’s a lot of work which finally gets released in this build. >> >>> - Steve >>> >>> PS: This is my first time trying ProtonMail's "sign message" function; >>> assuming it works my ProtonMail key fingerprint is listed here: >>> https://www.asksteved.com/?page_id=2 >> >> My mu4e tells me that your sig was verified. >> >> Best wishes, >> Arne > > > -- > Unpolitisch sein > heißt politisch sein > ohne es zu merken
final final test release of 1481
Hi, I had to add some more fixes to run.sh to ensure that the classpath includes jna and jna-platform. I updated the pre-release with the new files and added a note for those who update by copying in the jar: > This also means that you need jna-4.2.2.jar and jna-platform-4.2.2.jar > in your freenet folder. The auto-updater takes care of that for you. > If you update manually by copying in new jar-files, you need to adapt > the classpath in wrapper.conf or in run.sh (if you do not use the wrapper). Please give it some now hopefully truly final testing: https://github.com/freenet/fred/releases/tag/build01481 Installers: → *nix: https://github.com/freenet/fred/releases/download/build01481/new_installer_offline_1481.jar → Windows: https://github.com/freenet/fred/releases/download/build01481/FreenetInstaller-1481.exe (add .sig for the PGP signature, the OSX installer will follow once mrsteveman1 has time). Thanks to jamesaxl from #freenet on Freenode for finding this problem on BSD! I’m sorry that this adds another week to the release date. I’m also still waiting for confirmation by anonymous@6KMY4DVjZ… on FMS whether the breakage reported was due to missing the jna files. If that’s resolved, there are no more release blockers I know of. I plan to upload this true true real final release to a new testing key the next days so we can do another full update cycle test (install 1480, change the update key, watch freenet update to 1481 over Freenet, celebrate). And then get this release truly fully done. Sidenote: the statistics site should soon work again. I switched pyProbe from enum to enum34 to resolve a dependency conflict with the cryptography package (that needs enum34, but user-installed enum can override that and cause undecipherable errors). Best wishes, Arne Arne Babenhauserheide writes: > Steve Dougherty writes: >> Hooray! I was able to verify this build on my Debian Jessie box: > Nice! Thank you for checking! > >> Thank you for your work, both of you! :) > > Thank you for verifying the build, and for your work on preparing the > new keys! There’s a lot of work which finally gets released in this build. > >> - Steve >> >> PS: This is my first time trying ProtonMail's "sign message" function; >> assuming it works my ProtonMail key fingerprint is listed here: >> https://www.asksteved.com/?page_id=2 > > My mu4e tells me that your sig was verified. > > Best wishes, > Arne -- Unpolitisch sein heißt politisch sein ohne es zu merken signature.asc Description: PGP signature
