Apache OpenOffice on google+

Hello, Is anyone actually moderating the AOO-profile on google+? (This mailadress is listed as contact) https://plus.google.com/u/0/+openoffice/posts It has been quite active sometimes but now there is no news since 29.10.2015. Maybe a good place to announce the upcoming 4.1.3? kind regards

Re: Fwd: [Issue 125147] CRASH applying styles to text

In my opinion it *should* be a release blocker because at the moment AOO is unusable on Linux (Ubuntu). If not for 4.1.3 then for 4.1.4. As I understand it there is already a fix in the trunk for 1 1/2 year? But I am only a user and leave those decisions to the developers... ;-) Am 19.09.2016

Re: How do all the binaries get built?

If useful, I can replace my 64bit CentOS5 vm with a 32bit one. > On Sep 17, 2016, at 4:05 PM, Andrea Pescetti wrote: > > On 16/09/2016 Jim Jagielski wrote: >> I'm in the process of bringing up a new CentOS5 system as we speak > > Good news! The recipe on our MWiki > >

Fwd: [Issue 125147] CRASH applying styles to text

Recently, we have only been adding changes for 4.1.3 if they are necessary to building it. If you request 4.1.3 release blocker for a general bug fix, please discuss the reasons for putting the particular change in. Forwarded Message Subject: [Issue 125147] CRASH applying

Re: 4.1.4 Release Manager?

The idea for the Phönix Motiv is ment as a statement. And IMHO has most drama on 4.1.3 release. Today Xing (Germans linkid social media ) posted the article from ZDF.de (Germans 2nd state TV station) about the upcoming death of open office. Referring Dennis email about the idea of retirement for

Re: building on Windows 10 breaks at guistdio.exe

I installed some more things in my build environment such as the Windows Drive Kit and I enabled the atl flags. I cleaned the whole build and started over again with new config and using the multiprocessor and multi threading capability, and have now made it close to the end of the build. Only the

Re: Fwd: [Issue 125147] CRASH applying styles to text

Hello; I have no intent of getting in the way of 4.1.x (x >=3), I understand it is important for the project to show it's capacity to push out a new release in a short time. OTOH, we were caught unprepared, as we had abandoned the 41 branch completely about 11 months ago. Given this is

Re: building on Windows 10 breaks at guistdio.exe

On Mon, Sep 19, 2016 at 07:12:29PM -0700, Patricia Shanahan wrote: > 4.1.3 does have changes to the language library URLs. Has anyone else done a > build that included Italian? His logs say aoo-trunk, so I assume John isn't building branch AOO413. NSIS >= 3.* is only on that branch. Regards --

Re: building on Windows 10 breaks at guistdio.exe

I actually did see an error in the packaging phase, but it didn't seem to affect the final output, I still got the setup.exe which worked just fine, and I can open and use soffice.exe just fine after running setup. This is the error I got: ERROR: The following errors occurred in packaging process:

Re: building on Windows 10 breaks at guistdio.exe

I wound up building in stages, since the build was breaking here and there. I just picked it up from where it left off as I fixed things. So I don't have a single output... unless there is a log file that collects various build stages together into one single output? I would also recommend

Re: building on Windows 10 breaks at guistdio.exe

4.1.3 does have changes to the language library URLs. Has anyone else done a build that included Italian? On 9/19/2016 6:33 PM, John D'Orazio wrote: I actually did see an error in the packaging phase, but it didn't seem to affect the final output, I still got the setup.exe which worked just

Re: building on Windows 10 breaks at guistdio.exe

Sorry, "output" was ambiguous. I'm not interested in the log files at this time, but in the installation files. I want to try to install the result of your build on a Windows 7 machine. On 9/19/2016 6:22 PM, John D'Orazio wrote: I wound up building in stages, since the build was breaking here

Re: building on Windows 10 breaks at guistdio.exe

On Tue, Sep 20, 2016 at 03:22:40AM +0200, John D'Orazio wrote: > I wound up building in stages, since the build was breaking here and there. > I just picked it up from where it left off as I fixed things. So I don't > have a single output... unless there is a log file that collects various > build

Re: Fwd: [Issue 125147] CRASH applying styles to text

Given the number of users who install AOO on Ubuntu (after purging LibreOffice) it may not be the prime target... But the fix should be included in one of the next releases. As well as: https://bz.apache.org/ooo/show_bug.cgi?id=125762 kind regards Matthias Seidel Am 19.09.2016 um 15:46 schrieb

Re: Fwd: [Issue 125147] CRASH applying styles to text

User opinions are important, especially on the seriousness of a bug. On 9/19/2016 6:36 AM, Matthias Seidel wrote: In my opinion it *should* be a release blocker because at the moment AOO is unusable on Linux (Ubuntu). If not for 4.1.3 then for 4.1.4. As I understand it there is already a fix

[RESULT][VOTE] Recommend Marcus Lange (marcus) as the New Vice President for Apache OpenOffice

[BCC to PMC] The [VOTE] to recommend Marcus Lange (marcus) as the New Vice President for Apache OpenOffice has passed. Tally +1 Jan Høydahl +1 Dennis E. Hamilton +1 Gavin McDonald +1 Herbert Duerr +1 Patricia Shanahan +1 Louis Suárez-Potts +1 Mechtilde Stehmann +1

Re: Fwd: [Issue 125147] CRASH applying styles to text

Am 19.09.2016 um 19:33 schrieb Marcus: > IMHO "unusable" is the wrong description. I've no problem. Why? Maybe > I don't use en-US. ;-) > > Sure a large portion of users have problems to work with styles. But > "unuseable" has a total different meaning - at least for me. The related bugs were

[PROPOSAL] Buildbot builds should include mor than en-US only

I remember that old times at Sun where we have done builds with more than just en-US. In order to cover problems that could be language-related we have built: - en-US - as default - de - for the lazy German guys ;-) , can be left out now - pt - as these language has mostly the longest strings

Re: 4.1.4 Release Manager?

Am 09/19/2016 08:27 AM, schrieb Peter Kovacs: The idea for the Phönix Motiv is ment as a statement. And IMHO has most drama on 4.1.3 release. Today Xing (Germans linkid social media ) posted the article from ZDF.de (Germans 2nd state TV station) about the upcoming death of open office.

Re: Fwd: [Issue 125147] CRASH applying styles to text

This should be revision 1761439? https://ci.apache.org/projects/openoffice/index.html#linux64 is where I would look? Unfortunately there is only a build for en-US (Linux 64). But I will surely confirm if the problems are gone... Regards Matthias Am 19.09.2016 um 19:30 schrieb Andrea

Re: Fwd: [Issue 125147] CRASH applying styles to text

Matthias Seidel wrote: [ https://bz.apache.org/ooo/show_bug.cgi?id=125147 ] But the fix should be included in one of the next releases. As well as: https://bz.apache.org/ooo/show_bug.cgi?id=125762 Both should be nominated for 4.1.4. If you can check, on a trunk build from a buildbot, that

Re: 4.1.4 Release Manager?

I do not know. How much time there is for one to do. I have to ask people. Marcus schrieb am Mo., 19. Sep. 2016, 19:36: > Am 09/19/2016 08:27 AM, schrieb Peter Kovacs: > > The idea for the Phönix Motiv is ment as a statement. And IMHO has most > > drama on 4.1.3 release. >

FW: Resolution to Change the Apache OpenOffice Chair

[BCC to PMC] FYI, how this is done. Project Chairs add items to the upcoming Board meeting agenda using SVN additions to the text. This is how Board Reports are submitted, in spaces set for board-report attachments, and how other reports are inserted in slots of the agenda. The agenda is

Re: Fwd: [Issue 125147] CRASH applying styles to text

Am 09/19/2016 03:46 PM, schrieb Patricia Shanahan: User opinions are important, especially on the seriousness of a bug. On 9/19/2016 6:36 AM, Matthias Seidel wrote: In my opinion it *should* be a release blocker because at the moment AOO is unusable on Linux (Ubuntu). IMHO "unusable" is

Re: building on Windows 10 breaks at guistdio.exe

I had installed 64-bit Cygwin installed here before I started on compiling AOO. I hit problems, and had to go to the recommended 32-bit Cygwin. However, things have changed a bit since then, so it may be worth seeing if it works. On 9/19/2016 8:59 AM, John D'Orazio wrote: ... I also read

Re: [PROPOSAL] Buildbot builds should include mor than en-US only

Am 09/19/2016 08:23 PM, schrieb Matthias Seidel: Am 19.09.2016 um 20:08 schrieb Marcus: I remember that old times at Sun... Some of my OS/2-friends worked for SUN (Hamburg). You might not incidentally know Carsten Müller or Jörg Skottke? sure, colleagues for many years. And of course many

Re: [PROPOSAL] Buildbot builds should include mor than en-US only

So klein ist die Welt! ;-) Congratulations, Mr. Vice President! Am 19.09.2016 um 20:32 schrieb Marcus: > Am 09/19/2016 08:23 PM, schrieb Matthias Seidel: >> Am 19.09.2016 um 20:08 schrieb Marcus: >>> I remember that old times at Sun... >> >> Some of my OS/2-friends worked for SUN (Hamburg). >>

Re: [VOTE] Recommend Marcus Lange (marcus) as the New Vice President for Apache OpenOffice

[X] +1 Approve -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com

Re: [PROPOSAL] Buildbot builds should include mor than en-US only

Am 19.09.2016 um 20:08 schrieb Marcus: > I remember that old times at Sun... Some of my OS/2-friends worked for SUN (Hamburg). You might not incidentally know Carsten Müller or Jörg Skottke? > So, I suggest to expand the build.lst to this setup. +1 for the proposal! Regards Matthias

Re: [RESULT][VOTE] Recommend Marcus Lange (marcus) as the New Vice President for Apache OpenOffice

A big thank you to all of you for your votes, that you are putting your trust in me. However, I'm especially happy about the amount of votes (regardless of where in the ballot the cross was made). For me this should clearly show that the interest of a healthy Apache OpenOffice is still of a

Re: building on Windows 10 breaks at guistdio.exe

I have now successfully completed the build on Windows 10, and after changing the install path of NSIS to one without spaces, packaging also completed successfully. I have added "Windows 10" alongside "Windows 7" and "Windows 8.1" in the Step by Step guide. On Mon, Sep 19, 2016 at 7:50 PM,

Re: building on Windows 10 breaks at guistdio.exe

Congratulations! I'm about to do a Windows 10 build on a new machine, so please make sure the step-by-step incorporates all that you learned in the process. I have a specific test I would like run. The current release process calls for doing the Windows builds on Windows 7. I am wondering if