LOL :)
> On Aug 31, 2018, at 1:42 PM, Matthias Seidel
> wrote:
>
> Am 31.08.2018 um 19:40 schrieb Jim Jagielski:
>> Not if they aren't using the exact same setup as the community builds :)
>>
>> The buildbots are Ubuntu, iirc. The community build servers are CentOS5 (for
>> 4.1.x)
>
> I
Hi Marcus,
Am 31.08.2018 um 22:41 schrieb Marcus:
> Am 31.08.2018 um 16:06 schrieb Matthias Seidel:
>> Am 28.08.2018 um 22:25 schrieb Marcus:
>>> Am 28.08.2018 um 16:50 schrieb Matthias Seidel:
Can someone please add the flags for 4.1.6 (Target Milestone, Last
Confirmation) to Bugzilla?
Am 31.08.2018 um 16:06 schrieb Matthias Seidel:
Am 28.08.2018 um 22:25 schrieb Marcus:
Am 28.08.2018 um 16:50 schrieb Matthias Seidel:
Can someone please add the flags for 4.1.6 (Target Milestone, Last
Confirmation) to Bugzilla?
I was only able to add Release Blocker.
Either I am not able to
Am 31.08.2018 um 19:40 schrieb Jim Jagielski:
> Not if they aren't using the exact same setup as the community builds :)
>
> The buildbots are Ubuntu, iirc. The community build servers are CentOS5 (for
> 4.1.x)
I know. Ubuntu 14.04 and Windows 10 to be exact.
Should we delete the buildbots now?
Not if they aren't using the exact same setup as the community builds :)
The buildbots are Ubuntu, iirc. The community build servers are CentOS5 (for
4.1.x)
> On Aug 31, 2018, at 1:37 PM, Matthias Seidel
> wrote:
>
> Am 31.08.2018 um 19:35 schrieb Jim Jagielski:
>> But the buildbots are not
Am 31.08.2018 um 19:35 schrieb Jim Jagielski:
> But the buildbots are not the platforms used to create the community builds...
I know.
But they are the first ones to discover a broken build.
>
>> On Aug 31, 2018, at 12:31 PM, Matthias Seidel
>> wrote:
>>
>> FWIW,
>>
>> the buildbots already
But the buildbots are not the platforms used to create the community builds...
> On Aug 31, 2018, at 12:31 PM, Matthias Seidel
> wrote:
>
> FWIW,
>
> the buildbots already produce 4.1.6 builds:
> https://www.openoffice.org/download/devbuilds.html
>
> Unfortunately the page is not updated
FWIW,
the buildbots already produce 4.1.6 builds:
https://www.openoffice.org/download/devbuilds.html
Unfortunately the page is not updated because our CMS is broken (again).
Regards,
Matthias
Am 31.08.2018 um 18:26 schrieb Jim Jagielski:
> Confirmed that with a somewhat newer Perl (I'm
Confirmed that with a somewhat newer Perl (I'm using 5.14.3) and openssl
1.0.2p, the downloads go off w/o a hitch.
Build progressing as we speak.
> On Aug 31, 2018, at 11:55 AM, Jim Jagielski wrote:
>
> CentOS5 has a VERY old perl. The problem is that sometime between the release
> of AOO
CentOS5 has a VERY old perl. The problem is that sometime between the release
of AOO 4.1.5 and 4.1.6, Sourceforge has, from what I can see, moved to using
LetsEncrypt and the download perl script now fails whenever it tries to
download ext sources:
downloading to
Hi Peter,
Am 31.08.2018 um 16:17 schrieb Peter kovacs:
> Hi all,
>
> I agree that the "TM" displacement should be fixed. However I do not see that
> we have to change something to the design.
> So is it possible to change the original with something that would enhance
> the situation without
Hi all,
I agree that the "TM" displacement should be fixed. However I do not see that
we have to change something to the design.
So is it possible to change the original with something that would enhance the
situation without changing other attributes?
All the best
Peter
Am 31. August 2018
Hi Marcus,
Am 28.08.2018 um 22:25 schrieb Marcus:
> Am 28.08.2018 um 16:50 schrieb Matthias Seidel:
>> Can someone please add the flags for 4.1.6 (Target Milestone, Last
>> Confirmation) to Bugzilla?
>> I was only able to add Release Blocker.
>>
>> Either I am not able to find it or my rights are
Hi Pedro,
Am 31.08.2018 um 01:09 schrieb Pedro Lino:
> Hi Dave, all
>
>> On August 30, 2018 at 11:17 PM Dave Fisher wrote:
>> You can ask for Lazy Consensus on this and give 72 hours for anyone to
>> object.
> Thanks!
>
> As suggested, I'm asking for Lazy Consensus on the adoption of file
>
14 matches
Mail list logo
