Ariel Constenla-Haile wrote:
On Wed, Sep 21, 2016 at 12:10:29AM +0200, Andrea Pescetti wrote:
(the way it is now; I haven't checked
https://bz.apache.org/ooo/show_bug.cgi?id=127120 yet) it uses only packages
from CentOS and EPEL repositories, plus custom Ant and Perl as the versions
shipping
On Wed, Sep 21, 2016 at 12:10:29AM +0200, Andrea Pescetti wrote:
> On 04/09/2016 Andrea Pescetti wrote:
> >https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5
> >Ideally, this would become a semi-scriptable recipe for preparing a
> >"standard" CentOS 5 VM for
On 04/09/2016 Andrea Pescetti wrote:
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5
Ideally, this would become a semi-scriptable recipe for preparing a
"standard" CentOS 5 VM for building OpenOffice releases, at least for
the 4.1.x series
The recipe has
On 29/08/2016 Kay Schenk wrote:
​Thanks for all this work. I suggest trying builds on /trunk and I would
bet the Perl problems go away. The new Java downloader is super!
Seeing the situation, I would still prefer to be able to build 4.1.2
correctly (which works now, but JUnit and Perl modules
On Mon, Aug 29, 2016 at 12:02 AM, Andrea Pescetti
wrote:
> On 21/08/2016 Kay Schenk wrote:
>
>> We REALLY REALLY NEED the CentOS5 32-bit and 64-bit VMS regardless of
>> what we do for Windows.
>>
>
> I now have a repeatable process to create a CentOS 5 VM from scratch and
>
On 21/08/2016 Kay Schenk wrote:
We REALLY REALLY NEED the CentOS5 32-bit and 64-bit VMS regardless of
what we do for Windows.
I now have a repeatable process to create a CentOS 5 VM from scratch and
building OpenOffice with it, meaning that I've successfully built 4.1.2
on it. I also have a
On 08/19/2016 10:37 AM, Dennis E. Hamilton wrote:
>
>
>> -Original Message-
>> From: Kay Schenk [mailto:kay.sch...@gmail.com]
>> Sent: Friday, August 19, 2016 09:09
>> To: dev@openoffice.apache.org
>> Subject: Re: Ready to setup release build machi
On 08/21/2016 10:46 AM, Andrea Pescetti wrote:
> On 19/08/2016 Dennis E. Hamilton wrote:
>> I thought that the basic requirement is that the release manager(s) do
>> any builds on a machine under their [exclusive] individual control.
>
> This way one would need to rely on individual volunteers
> -Original Message-
> From: Kay Schenk [mailto:kay.sch...@gmail.com]
> Sent: Friday, August 19, 2016 09:09
> To: dev@openoffice.apache.org
> Subject: Re: Ready to setup release build machines?
>
>
>
> On 08/12/2016 12:22 PM, Dennis E. Hamilton wrote:
&
On 08/12/2016 12:22 PM, Dennis E. Hamilton wrote:
> I thought that the basic requirement is that the release manager(s) do any
> builds on a machine under their [exclusive] individual control. That also
> means satisfying baseline requirements for release builds though. That
> pretty much
I thought that the basic requirement is that the release manager(s) do any
builds on a machine under their [exclusive] individual control. That also
means satisfying baseline requirements for release builds though. That pretty
much requires use of a VM if the main development system of a
On Tue, Aug 9, 2016 at 10:28 AM, Andrea Pescetti
wrote:
> Seeing the issue from a purely technical point of view (i.e., imagining
> for a while that there is no cost associated and no Infra around), how far
> are we from having an "Apache OpenOffice build farm" where we can
12 matches
Mail list logo