Yes, it is some server problem but it is still unsolved. It would be nice that existing users are warned of future versions. In fact if the fix also affects 4.1.5 and 4.1.6 it would warn users of the 4.1.7 release.
> On September 4, 2019 at 2:07 AM Peter Kovacs <[email protected]> wrote: > > Wasn't this some sort of server side issue? > > On 04.09.19 00:32, Pedro Lino wrote: > > > > Maybe someone can take another shot at fixing the failed Check for Updates? > > https://bz.apache.org/ooo/show_bug.cgi?id=127789 > > I'm available for testing. > > > > Best regards, > > Pedro > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
