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
Re: final test release of 1481
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
Re: final test release of 1481
‐‐‐ Original Message ‐‐‐ On Thursday, October 18, 2018 7:55 PM, DC* wrote: > Seems auto-update key works flawlessly. Attached relevant logs. Hooray! I was able to verify this build on my Debian Jessie box: ``` steve@debian:~/local_freenet/fred$ cat /etc/debian_version 8.11 steve@debian:~/local_freenet/fred$ uname -a Linux debian 3.16.0-7-amd64 #1 SMP Debian 3.16.59-1 (2018-10-03) x86_64 GNU/Linux steve@debian:~/local_freenet/fred$ java -version java version "1.7.0_181" OpenJDK Runtime Environment (IcedTea 2.6.14) (7u181-2.6.14-1~deb8u1) OpenJDK 64-Bit Server VM (build 24.181-b01, mixed mode) steve@debian:~/local_freenet/fred$ ./gradlew jar ... BUILD SUCCESSFUL in 11s 4 actionable tasks: 4 executed SHA-256 of freenet.jar: 5efa9c4184cc02316b9faa1c8ce32bda78f5885c3a0703f684e0a08bdf3ffc8b steve@debian:~/local_freenet/fred$ sha256sum freenet-build01481.jar 5efa9c4184cc02316b9faa1c8ce32bda78f5885c3a0703f684e0a08bdf3ffc8b freenet-build01481.jar steve@debian:~/local_freenet/fred$ cmp freenet-build01481.jar build/libs/freenet.jar steve@debian:~/local_freenet/fred$ echo $? 0 ``` I'm now running 1481. In case others want to go the same route, specifically, because I wasn't able to get the jar to fetch from the test key (RecentlyFailed), I fetched the dependency changes - upgraded Bouncy Castle, introducing jna and jna-platform: ``` > git diff build01480..build01481 -- dependencies.properties diff --git a/dependencies.properties b/dependencies.properties index 0c919f8c57..d89a1fe3f9 100644 --- a/dependencies.properties +++ b/dependencies.properties @@ -6,14 +6,30 @@ contrib.key=CHK@6xW9CyMrm9fVoHfQL4j8~O2BBNzJt0N3HywffP2O1t4,ozsCsUld9z~EUh5NFkZr contrib.size=4685193 contrib.type=CLASSPATH contrib.order=1 -bouncycastle.version=1.54.0 -bouncycastle.filename=bcprov-jdk15on-154.jar -bouncycastle.sha256=d0ae14598f9c528d2ab7bb8ed00e785a5440f692712cd362d69328aba25efb57 +bouncycastle.version=1.59.0 +bouncycastle.filename=bcprov-jdk15on-1.59.jar +bouncycastle.sha256=1c31e44e331d25e46d293b3e8ee2d07028a67db011e74cb2443285aed1d59c85 bouncycastle.filename-regex=bcprov-jdk.*.jar -bouncycastle.key=CHK@3Ra2Gbc7li7CGAKMOlZsrjC4HDkDdmyZoMb37rJq6F8,p8HhYtEegEWaCvFfTb-Heh3OIqqRq~w6wcbQrKsPShg,AAMC--8/bcprov-jdk15on-154.jar -bouncycastle.size=3277268 +bouncycastle.key=CHK@tQXPsjTMsS9Nj60y3qglLKoPzxSqU~6GvfF~d06yyoo,59eHcQAcoxtlZvempONC80Motcasm9NK9294RC8tXtE,AAMC--8/bcprov-jdk15on-1.59.jar +bouncycastle.size=4092400 bouncycastle.type=CLASSPATH bouncycastle.order=-1 +jna.version=4.2.2 +jna.filename=jna-4.2.2.jar +jna.sha256=1f38af54e06c6e6f6dbf39ba2c052b952dea5dddb4871127b34639ddeb11bdbe +jna.filename-regex=jna-*.jar +jna.key=CHK@0qI6PqVBf2aGVFt6VOFqpBkglZWg0ulrqu4ZPIsKcoA,IXD2eKM-LV81yX-kZkwQBd9~yJJO2J44hxVi87ycs74,AAMC--8/jna-4.2.2.jar +jna.size=1137286 +jna.type=CLASSPATH +jna.order=2 +jna-platform.version=4.2.2 +jna-platform.filename=jna-platform-4.2.2.jar +jna-platform.sha256=32aca873a4cb14721d939bbc8287a828919c05e8e1040b3fe8290f6128cdecca +jna-platform.filename-regex=jna-platform*.jar +jna-platform.key=CHK@7VdTmbaWq5RkqDRoTxxbRcNa4DMNSF0pENCyHPH0QHw,0on2uxMOaThYWQ~z4UnHpLtmqpFjfaDha6Fu51I3xvo,AAMC--8/jna-platform-4.2.2.jar +jna-platform.size=1856200 +jna-platform.type=CLASSPATH +jna-platform.order=3 update-sh.version=2 update-sh.filename=update.sh update-sh.type=OPTIONAL_PRELOAD ``` then updated my wrapper.properties accordingly and restarted the node. For now it's running; we'll see how it goes! Thank you for your work, both of you! :) - 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 > On 2018-10-18 19:33, Arne Babenhauserheide wrote: > > > DC* d...@riseup.net writes: > > > > > Great news, I'm testing this get I get home (I was running a node from > > > 1481 for a couple of days without issues). > > > > Thank you! > > Best wishes, > > Arne signature.asc Description: OpenPGP digital signature
Re: final test release of 1481
Seems auto-update key works flawlessly. Attached relevant logs. On 2018-10-18 19:33, Arne Babenhauserheide wrote: > DC* writes: > >> Great news, I'm testing this get I get home (I was running a node from 1481 >> for a couple of days without issues). > > Thank you! > > Best wishes, > Arne INFO | jvm 2| 2018/10/18 20:49:06 | WrapperManager Debug: Send a packet START_PENDING : 30 INFO | jvm 2| 2018/10/18 20:49:06 | WrapperManager Debug: Send a packet START_PENDING : 30 INFO | jvm 2| 2018/10/18 20:49:06 | Deleted 338 of 338 temporary files (0 non-temp files in temp directory) in 0s INFO | jvm 2| 2018/10/18 20:49:06 | Initializing USK Manager INFO | jvm 2| 2018/10/18 20:49:06 | Loading cache of request statuses... INFO | jvm 2| 2018/10/18 20:49:06 | Initializing Node Updater INFO | jvm 2| 2018/10/18 20:49:06 | FNP port created on 0.0.0.0:63601 INFO | jvm 2| 2018/10/18 20:49:06 | Initializing CHK Datastore (93891 keys) INFO | jvm 2| 2018/10/18 20:49:06 | Slot filter (./datastore/CHK-store.slotfilter) for CHK-store is loaded (new=false). INFO | jvm 2| 2018/10/18 20:49:06 | Initializing CHK Datacache (93891 keys) INFO | jvm 2| 2018/10/18 20:49:06 | Slot filter (./datastore/CHK-cache.slotfilter) for CHK-cache is loaded (new=false). INFO | jvm 2| 2018/10/18 20:49:06 | Initializing PUBKEY Datastore (93891 keys) INFO | jvm 2| 2018/10/18 20:49:06 | Slot filter (./datastore/PUBKEY-store.slotfilter) for PUBKEY-store is loaded (new=false). INFO | jvm 2| 2018/10/18 20:49:06 | Initializing PUBKEY Datacache (93891 keys) INFO | jvm 2| 2018/10/18 20:49:06 | Slot filter (./datastore/PUBKEY-cache.slotfilter) for PUBKEY-cache is loaded (new=false). INFO | jvm 2| 2018/10/18 20:49:06 | Initializing SSK Datastore (93891 keys) INFO | jvm 2| 2018/10/18 20:49:06 | Slot filter (./datastore/SSK-store.slotfilter) for SSK-store is loaded (new=false). INFO | jvm 2| 2018/10/18 20:49:06 | Initializing SSK Datacache (93891 keys) INFO | jvm 2| 2018/10/18 20:49:06 | Slot filter (./datastore/SSK-cache.slotfilter) for SSK-cache is loaded (new=false). INFO | jvm 2| 2018/10/18 20:49:06 | Initializing CHK Dataclientcache (93891 keys) INFO | jvm 2| 2018/10/18 20:49:06 | Slot filter (./datastore/CHK-clientcache.slotfilter) for CHK-clientcache is loaded (new=false). INFO | jvm 2| 2018/10/18 20:49:06 | Initializing PUBKEY Dataclientcache (93891 keys) INFO | jvm 2| 2018/10/18 20:49:06 | Slot filter (./datastore/PUBKEY-clientcache.slotfilter) for PUBKEY-clientcache is loaded (new=false). INFO | jvm 2| 2018/10/18 20:49:06 | Initializing SSK Dataclientcache (93891 keys) INFO | jvm 2| 2018/10/18 20:49:06 | Slot filter (./datastore/SSK-clientcache.slotfilter) for SSK-clientcache is loaded (new=false). INFO | jvm 2| 2018/10/18 20:49:06 | Max packet size: 1232 INFO | jvm 2| 2018/10/18 20:49:06 | Max packet size: 1232 INFO | jvm 2| 2018/10/18 20:49:06 | Initializing Plugin Manager INFO | jvm 2| 2018/10/18 20:49:06 | WrapperManager Debug: Send a packet START_PENDING : 12 DEBUG | wrapperp | 2018/10/18 20:49:06 | read a packet START_PENDING : 12 DEBUG | wrapper | 2018/10/18 20:49:06 | JVM signaled a start pending with waitHint of 12 millis. INFO | jvm 2| 2018/10/18 20:49:06 | Node constructor completed INFO | jvm 2| 2018/10/18 20:49:06 | Read 0 darknet peers from ./peers-14990 INFO | jvm 2| 2018/10/18 20:49:06 | Starting DNSRequester INFO | jvm 2| 2018/10/18 20:49:06 | Created uptime estimator, time offset is 20435 uptime at startup is 0.00 INFO | jvm 2| 2018/10/18 20:49:06 | Read 61 opennet peers from ./openpeers-63601 INFO | jvm 2| 2018/10/18 20:49:06 | Read 0 old-opennet-peers from ./openpeers-old-63601 INFO | jvm 2| 2018/10/18 20:49:07 | Not attempting immediate announcement: dark peers=0 open peers=61 old open peers=0 - will wait 1 minute... INFO | jvm 2| 2018/10/18 20:49:07 | Starting PacketSender INFO | jvm 2| 2018/10/18 20:49:07 | Starting Ticker INFO | jvm 2| 2018/10/18 20:49:07 | Using wrapper correctly: freenet.node.NodeStarter@46fb2579 INFO | jvm 2| 2018/10/18 20:49:07 | Freenet 0.7.5 Build #1481 rbuild01481 INFO | jvm 2| 2018/10/18 20:49:07 | FNP port is on 0.0.0.0:14990 INFO | jvm 2| 2018/10/18 20:49:07 | Multi-file replace: Nothing to do for wrapper-update-mac. INFO | jvm 2| 2018/10/18 20:49:07 | Will serve freenet-ext.jar for UOM INFO | jvm 2| 2018/10/18 20:49:07 | Not running multi-file replace wrapper-update-unix : File does not exist: lib/libwrapper-linux-x86-64.so INFO | jvm 2| 2018/10/18 20:49:07 | Preloading jna-platform-4.2.2.jar for the next update... INFO | jvm 2| 2018/10/18 20:49:07 | Preloading jna-platform-4.2.2.jar needed for new Freenet update 1481 INFO | jvm 2| 2018/10/18 20:49:07 | Preloading
Re: final test release of 1481
DC* writes: > Great news, I'm testing this get I get home (I was running a node from 1481 > for a couple of days without issues). Thank you! Best wishes, Arne -- Unpolitisch sein heißt politisch sein ohne es zu merken signature.asc Description: PGP signature
final test release of 1481
Hi, I’m now running Freenet 1481, and it works! But that’s just my box. It needs your testing! Please give the Installer testing! https://github.com/freenet/fred/releases/tag/build01481 https://github.com/freenet/fred/releases/download/build01481/new_installer_offline_1481.jar https://github.com/freenet/fred/releases/download/build01481/new_installer_offline_1481.jar.sig https://github.com/freenet/fred/releases/download/build01481/FreenetInstaller-1481.exe https://github.com/freenet/fred/releases/download/build01481/FreenetInstaller-1481.exe.sig (no OSX installer yet, sorry. That is being built my mrsteveman) To help test the auto-updater, please go to the auto update settings at http://127.0.0.1:/config/node.updater?fproxyAdvancedMode=2 and add the following key under "Where should Freenet look for updates?" USK@YOeUMvHNyr2RY1dQB0-4cppO2Ip-8zKf7CaszRhPqU4,OaISGGFz52FaD98m2JZo-2gQ2XErr0pb3DPkpvDkKxs,AQACAAE/jar/1480 You might have to restart Freenet to get it to detect the new release after adding the new key (I had to). Testing release notes: http://127.0.0.1:/freenet:SSK@YOeUMvHNyr2RY1dQB0-4cppO2Ip-8zKf7CaszRhPqU4,OaISGGFz52FaD98m2JZo-2gQ2XErr0pb3DPkpvDkKxs,AQACAAE/changelog-1481?type=text/plain http://127.0.0.1:/freenet:SSK@YOeUMvHNyr2RY1dQB0-4cppO2Ip-8zKf7CaszRhPqU4,OaISGGFz52FaD98m2JZo-2gQ2XErr0pb3DPkpvDkKxs,AQACAAE/fullchangelog-1481?type=text/plain If there are no new blockers, I’d like to release this to the actual update key next week. All there is to do is switching out the testing key for the real update key and running the inserter. And then we’ll finally have a release from the next branch after 18 months of work to get it ready! Thank you all for your work to get it working! Best wishes, Arne -- Unpolitisch sein heißt politisch sein ohne es zu merken signature.asc Description: PGP signature
