Re: 4.1.3 building

Jim Jagielski wrote: Once built and tested, how does one upload? I'm assuming the prepare-download-tree.sh in aoo-devtools?? All builds have already been uploaded by Ariel for this RC. No need to upload anything else. I did upload a full set of Linux-64 builds to

Re: 4.1.3 building

> On Sep 27, 2016, at 11:03 PM, Ariel Constenla-Haile > wrote: > > > IMO providing different builds for same arch will make it difficult to > QA, so I will go on with the Linux 64-bit builds. If someone wants to > build on CentOS 5 32 bit and upload the binaries, please

Re: 4.1.3 building

Once built and tested, how does one upload? I'm assuming the prepare-download-tree.sh in aoo-devtools?? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail:

Re: 4.1.3 building

Am 09/29/2016 09:04 PM, schrieb Andrea Pescetti: Marcus wrote: Am 09/29/2016 03:26 AM, schrieb Andrea Pescetti: RAT is a tool that we might even not want to use. The important thing is sometimes I really don't know why someone is coming to such a statement. This is one of this moments. Why

Re: 4.1.3 building

Marcus wrote: Am 09/29/2016 03:26 AM, schrieb Andrea Pescetti: RAT is a tool that we might even not want to use. The important thing is sometimes I really don't know why someone is coming to such a statement. This is one of this moments. Why shouldn't we use the RAT scan? Do you want to search

Re: 4.1.3 building

Am 09/29/2016 03:26 AM, schrieb Andrea Pescetti: Marcus wrote: Am 09/27/2016 11:13 PM, schrieb Andrea Pescetti: Possibly. But those files are generated during the build anyway, so the fact that RAT does not know about them is irrelevant. Sure, but the report is not green. But IMHO it should

Re: 4.1.3 building

On Wed, Sep 28, 2016 at 12:45:02PM +0200, Andrea Pescetti wrote: > Ariel Constenla-Haile wrote: > >IMO providing different builds for same arch will make it difficult to > >QA, so I will go on with the Linux 64-bit builds. > > Yes, if you already started uploading Linux-64 I agree this is the

Re: 4.1.3 building

Marcus wrote: Am 09/27/2016 11:13 PM, schrieb Andrea Pescetti: Possibly. But those files are generated during the build anyway, so the fact that RAT does not know about them is irrelevant. Sure, but the report is not green. But IMHO it should be green when we want to look at 4.1.3 as official

Re: 4.1.3 building

Am 09/27/2016 11:13 PM, schrieb Andrea Pescetti: On 25/09/2016 Marcus wrote: Finally I got a AOO 4.1.3 with release options - but only en-US. I used the following varaible + value in the build script: ... LANG="de en-US fr pt ja" the language option seems to be a problem with the build script:

Re: 4.1.3 building

Ariel Constenla-Haile wrote: IMO providing different builds for same arch will make it difficult to QA, so I will go on with the Linux 64-bit builds. Yes, if you already started uploading Linux-64 I agree this is the best solution. If someone wants to build on CentOS 5 32 bit and upload

Re: 4.1.3 building

On Wed, Sep 28, 2016 at 03:43:40AM +0200, Andrea Pescetti wrote: > On 23/09/2016 Ariel Constenla-Haile wrote: > >it might be time to start building it ;) > >I'll start doing so on Windows, as Jim and Andrea seem to cover the > >other platforms. > > Sorry for the miscommunication, Yes, as I saw

Re: 4.1.3 building

On 23/09/2016 Ariel Constenla-Haile wrote: it might be time to start building it ;) I'll start doing so on Windows, as Jim and Andrea seem to cover the other platforms. Sorry for the miscommunication, I see that the message where I was saying that

Re: 4.1.3 building

Am 09/25/2016 12:03 AM, schrieb Marcus: Am 09/24/2016 03:51 PM, schrieb Marcus: Am 09/23/2016 10:18 PM, schrieb Marcus: Am 09/23/2016 10:12 PM, schrieb Patricia Shanahan: On 9/23/2016 1:00 PM, Marcus wrote: Am 09/23/2016 09:26 PM, schrieb Ariel Constenla-Haile: On Thu, Sep 22, 2016 at

Re: 4.1.3 building

Am 09/24/2016 03:51 PM, schrieb Marcus: Am 09/23/2016 10:18 PM, schrieb Marcus: Am 09/23/2016 10:12 PM, schrieb Patricia Shanahan: On 9/23/2016 1:00 PM, Marcus wrote: Am 09/23/2016 09:26 PM, schrieb Ariel Constenla-Haile: On Thu, Sep 22, 2016 at 12:25:19AM +0200, Andrea Pescetti wrote: -

Re: 4.1.3 building

Am 09/23/2016 10:18 PM, schrieb Marcus: Am 09/23/2016 10:12 PM, schrieb Patricia Shanahan: On 9/23/2016 1:00 PM, Marcus wrote: Am 09/23/2016 09:26 PM, schrieb Ariel Constenla-Haile: On Thu, Sep 22, 2016 at 12:25:19AM +0200, Andrea Pescetti wrote: - Source revision r1761818 Isn't this time

Re: 4.1.3 building

On Thu, Sep 22, 2016 at 12:25:19AM +0200, Andrea Pescetti wrote: > - Source revision r1761818 Isn't this time to agree that this revision will be the one we release? Haven't seen any call from the RM, but it might be time to start building it ;) I'll start doing so on Windows, as Jim and Andrea

Re: 4.1.3 building

2. I would like to get a list of environments in which 4.1.3 has been successfully built. I'll announce time to build a release candidate when it builds in the required environments. aoo413 product build with revision 1761976 on win7 successful finished. btw.: "activex" module also builds

Re: 4.1.3 building

Hi, 2. I would like to get a list of environments in which 4.1.3 has been successfully built. I'll announce time to build a release candidate when it builds in the required environments. just finished an aoo413 debug build with revision 1761976 on win7. no build breaks so far ;-) will try

Re: 4.1.3 building

Andrea Pescetti wrote: Sample builds (English, German, Italian) from a few hours ago -but not from my latest build- are at http://home.apache.org/~pescetti/openoffice-4.1.3-dev-r1761683/ Latest builds for all languages are now uploading (I'll do it in small batches, not as a whole) to

Re: 4.1.3 building

Am 09/21/2016 10:49 PM, schrieb Patricia Shanahan: 1. My current policy for release blocker is to grant it immediately if it seems obvious to me that a fix is needed to build 4.1.3. I will also do so based on prior security@ discussion. Otherwise, I'll ask for input on dev@ before deciding. 2.

Re: 4.1.3 building

Patricia Shanahan wrote: 1. My current policy for release blocker is to grant it immediately if it seems obvious to me that a fix is needed to build 4.1.3. I will also do so based on prior security@ discussion. Otherwise, I'll ask for input on dev@ before deciding. OK. 4.1.4 is a good fallback

4.1.3 building

1. My current policy for release blocker is to grant it immediately if it seems obvious to me that a fix is needed to build 4.1.3. I will also do so based on prior security@ discussion. Otherwise, I'll ask for input on dev@ before deciding. 2. I would like to get a list of environments in