Matthias Seidel wrote:
There is already an (empty) update feed for 4.1.6. AOO 4.1.6 should just
report it is "up to date" (like 4.2.0 does).
Yes, but unless we can monitor it on the server side this is only
partial information: I mean, if 4.1.6-RC1 was set, by some mistake, to
use the same
Am 09.11.18 um 01:07 schrieb Andrea Pescetti:
> On 29/10/2018 Matthias Seidel wrote:
>> Am 28.10.18 um 22:53 schrieb Andrea Pescetti:
>>> https://bz.apache.org/ooo/show_bug.cgi?id=127789 ...
>>> As I wrote in the issue, this could be an issue just with the ASF
>>> network configuration and it may
On 29/10/2018 Matthias Seidel wrote:
Am 28.10.18 um 22:53 schrieb Andrea Pescetti:
https://bz.apache.org/ooo/show_bug.cgi?id=127789 ...
As I wrote in the issue, this could be an issue just with the ASF
network configuration and it may not require a fix at all.
This is also my guess.
Just
Hi Pedro,
just to be clear. We should solve this issue with or before 4.1.6. Thats
why I have linked it to the release.
There is no other reason for the link. We just need some pressure (which
is not bad) it seems in order to get this done.
All the best
Peter
On 29.10.18 00:15, Pedro Lino
Hi Andrea,
Am 28.10.18 um 22:53 schrieb Andrea Pescetti:
> I've taken a look at the few 4.1.6 accepted blockers that are still
> open. Don already discussed the ones affecting libraries.
>
> I'm especially interested in this one (server error when looking for
> updates)
>
Hi Andrea, all
This is clearly a server side error (and an intermitent one)
I rolled back to 4.1.4 (which was correctly reporting an update available last
week) but today all versions I tested (4.1.6, 4.1.5 and 4.1.4) all report
"Checking for an update failed."
This is not a 4.1.6 problem.
I've taken a look at the few 4.1.6 accepted blockers that are still
open. Don already discussed the ones affecting libraries.
I'm especially interested in this one (server error when looking for
updates)
https://bz.apache.org/ooo/show_bug.cgi?id=127789
that should be investigated properly
