Re: Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

On Sat, 2016-09-10 at 17:37 -0700, Jose R R wrote: > On Fri, Sep 9, 2016 at 12:37 PM, Wolfgang Tichy > wrote: > > > > Package: src:linux > > Version: 3.16.7-ckt25-2+deb8u3 > > Severity: critical > > Tags: security > > Justification: causes serious data loss > > > > Dear

4.1.3_release_blocker granted: [Issue 127100] Make NSIS 3.* a build requirement for building Windows installers

Patricia Shanahan has granted 4.1.3_release_blocker: Issue 127100: Make NSIS 3.* a build requirement for building Windows installers https://bz.apache.org/ooo/show_bug.cgi?id=127100 - To unsubscribe, e-mail:

Re: Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

On Sat, Sep 10, 2016 at 6:10 PM, Ben Hutchings wrote: > On Sat, 2016-09-10 at 17:37 -0700, Jose R R wrote: >> On Fri, Sep 9, 2016 at 12:37 PM, Wolfgang Tichy >> wrote: >> > >> > Package: src:linux >> > Version: 3.16.7-ckt25-2+deb8u3 >> > Severity:

Re: Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

On Sat, Sep 10, 2016 at 6:49 PM, Dennis E. Hamilton wrote: > > I don't understand the point of posting this message to dev@oo.a.o, > especially with all the details of an apparent Linux problem in conjunction > with LibreOffice (but not necessarily caused by

RE: Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

I don't understand the point of posting this message to dev@oo.a.o, especially with all the details of an apparent Linux problem in conjunction with LibreOffice (but not necessarily caused by LibreOffice). I assume the recommendation of Apache OpenOffice is not as a substitute but to see if

How do all the binaries get built?

What has to be done, in what sorts of environments, to generate all the binaries? Does, for example, building all the language versions for OSX have to be done on a Mac, or can one take some language files and some OSX files and combine them on a Windows machine?

Re: Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

On Fri, Sep 9, 2016 at 12:37 PM, Wolfgang Tichy wrote: > Package: src:linux > Version: 3.16.7-ckt25-2+deb8u3 > Severity: critical > Tags: security > Justification: causes serious data loss > > Dear Maintainer, > > when I open a particular word document (it contains images and

AOO413 branch created

I have created an AOO413 branch as a copy of AOO410. It is now available for check in of "release blocker" approved changes. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail:

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

Patricia Shanahan wrote: My view on this is that we should check in the changes for 4.1.3, freeze its code, and then create AOO414 as a copy of AOO413. Sure, this will work too. Then when you really release 4.1.3 with any last-minute fixes, a single "svn merge" command will update the AOO414

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

On 9/10/2016 3:10 PM, Andrea Pescetti wrote: Patricia Shanahan wrote: I'm going to wait a few hours to see if someone claims to depend on us not changing the branch. Absent a specific issue, I plan to create a 4.1.3 branch, and expect the, not yet selected, 4.1.4 Release Manager to create a

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

Patricia Shanahan wrote: I'm going to wait a few hours to see if someone claims to depend on us not changing the branch. Absent a specific issue, I plan to create a 4.1.3 branch, and expect the, not yet selected, 4.1.4 Release Manager to create a branch for it. OK. After all, I would assume

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

Patricia Shanahan wrote: On 9/10/2016 12:55 PM, Ariel Constenla-Haile wrote: only code with a bug and release blocker flag approved by the Release Manager can be checked in that branch; that is: if you want to include changes in the AOO413 branch: 1) open a bug 2) request releaser blocker

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

> On 11 Sep 2016, at 7:13 AM, Patricia Shanahan wrote: > > On 9/10/2016 12:55 PM, Ariel Constenla-Haile wrote: >> On Thu, Sep 08, 2016 at 12:40:48AM +0200, Andrea Pescetti wrote: >>> Recent events make it clear we will have to release OpenOffice 4.1.3 sooner >>> or later, with

4.1.3_release_blocker granted: [Issue 125980] Set default currency to Euro in Lithuanian locale

Patricia Shanahan has granted Ariel Constenla-Haile 's request for 4.1.3_release_blocker: Issue 125980: Set default currency to Euro in Lithuanian locale https://bz.apache.org/ooo/show_bug.cgi?id=125980

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

On 9/10/2016 12:55 PM, Ariel Constenla-Haile wrote: On Thu, Sep 08, 2016 at 12:40:48AM +0200, Andrea Pescetti wrote: Recent events make it clear we will have to release OpenOffice 4.1.3 sooner or later, with some duplication of work with respect to 4.1.2-patch1 but with more clarity for those

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

On Thu, Sep 08, 2016 at 12:40:48AM +0200, Andrea Pescetti wrote: > Recent events make it clear we will have to release OpenOffice 4.1.3 sooner > or later, with some duplication of work with respect to 4.1.2-patch1 but > with more clarity for those who couldn't see that we made a release last >

Re: Release process and 4.1.3

Patricia Shanahan wrote: I just created an account, user name "pats". Whitelisted. Andrea - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Release process and 4.1.3

On 9/10/2016 7:02 AM, Andrea Pescetti wrote: Patricia Shanahan wrote: On 9/9/2016 12:11 AM, Andrea Pescetti wrote: Actually, 4.1.2 was exactly this. Your starting point should thus be https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2 ; just copy the wiki page and edit/generalize

Re: Code signing available for OpenOffice

On 9 September 2016 23:29:49 BST, Andrea Pescetti wrote: >Mark Thomas wrote: >> The infrastructure team has regained access to the OpenOffice code >> signing account. If you would like to use it to sign releases please >> open an infra ticket and provide the Apache IDs of

Re: Status of ASF Ubuntu Buildbots

Hello +1 in general I think one build per week or two weeks is enough. It should be possible to start it manually if there are some bigger commits.. The person who commit code to the main branch should be able to start the buildbots. Kind regards Mechtilde Am 10.09.2016 um 02:24 schrieb