Re: We need a fix for update.cmd

2017-12-09 Thread Arne Babenhauserheide
Florent Daigniere writes: > On Sat, 2017-12-09 at 19:24 +0100, Arne Babenhauserheide wrote: >> Florent Daigniere writes: >> > Months later he is asking for help supporting the windows version of >> > the >> > legacy script that has now

Re: We need a fix for update.cmd

2017-12-09 Thread Florent Daigniere
On Sat, 2017-12-09 at 19:24 +0100, Arne Babenhauserheide wrote: > Florent Daigniere 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)...

Re: We need a fix for update.cmd

2017-12-09 Thread Arne Babenhauserheide
Florent Daigniere writes: > On Sat, 2017-12-09 at 12:33 +, 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

Re: We need a fix for update.cmd

2017-12-09 Thread Florent Daigniere
On Sat, 2017-12-09 at 12:33 +, 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

Re: We need a fix for update.cmd

2017-12-09 Thread Matthew Toseland
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