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 <arne_...@web.de> writes: > Steve Dougherty <st...@asksteved.com> 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
