Florent Daigniere <nextg...@freenetproject.org> writes: > On Sat, 2017-12-09 at 12:33 +0000, Matthew Toseland wrote: >> On 08/12/17 21:04, Arne Babenhauserheide wrote: >> > Hi, >> > >> > The new windows installer is prepared, I can release any day, but >> > there's still one critical piece missing: we need update.cmd fixed >> > to at >> > least download freenet-stable-latest.jar from github instead of >> > trying >> > to use the defunct downloads.freenetproject.org. >> > >> > This is the file: >> > https://github.com/freenet/wininstaller-innosetup/blob/master/instal >> > l_node/updater/update.cmd >> > >> > We need this updated to download from github releases, similar to >> > what >> > update.sh now does: >> > https://github.com/freenet/java_installer/blob/next/scripts/update.s >> > h#L271 >> > >> > But if I were to do that myself, it would be idiotic: I have almost >> > no >> > Windows experience (I never used a Windows computer as my home >> > system) >> > and most certainly do not know about intricacies of Windows systems. >> > >> > Therefore we need you to step up and go and get update.cmd to work >> > again: >> > >> > - Access https://github.com/freenet/fred/releases/latest >> > - Get the forwarding URL to grab the LATEST_TAG parameter. >> > - download https://github.com/freenet/fred/releases/download/${LATES >> > T_TAG}/freenet-${LATEST_TAG}.jar" >> > >> > If we can at least get the newest freenet jar-file, we can go and >> > fix >> > other things from there, if the switch to gradle creates unexpected >> > problems. >> > >> > So if you have some experience with Windows command line shell, >> > please >> > step up and fix update.cmd. This is the last real blocker before we >> > can >> > go forward towards releasing next. >> > >> > Best wishes, >> > Arne >> >> I still think this is going to break badly whenever you have an >> incompatible change to the dependencies.
Yes, but this is currently completely broken and I want it unbroken enough that we can at least ask people to run the updater for getting a new fred, if the switch to next breaks our networking layer. >> update.cmd should be auto-generated from dependencies.properties. > > update\.(sh|cmd) shouldn't exist anymore. The long term plan is to > migrate to a platform-independent wrapper for last-resort recovery... > Probably something python based based on TUF > https://theupdateframework.github.io/ > > But Arne said that he doesn't want to do that because "it's too > complicated" (despite having a POC provided to him showcasing how it > would work)... and would take too much time... I said "there are many things which could break and I first want to get next released while having a failover method to deploy updates." A proof of concept is not a working, debugged, ship-ready implementation, as the more-than-one-year effort to get reliable releases with gradle working clearly shows. Florent Daigniere <nextg...@freenetproject.org> writes: > Months later he is asking for help supporting the windows version of the > legacy script that has now been broken for years (we're past the one > year mark now)... Let one point not be forgotten: You broke that script this spring when you disabled downloads.freenetproject.org without first checking which parts of our tools depended on it. This was a throwback of more than half a year on the way to finally getting next released. And you did that when I had just finished my setup to get reliable releases again. Despite me voicing concerns. Best wishes, Arne -- Unpolitisch sein heißt politisch sein ohne es zu merken
signature.asc
Description: PGP signature
