Re: building on Windows 10 breaks at guistdio.exe

2016-09-19 Thread Ariel Constenla-Haile 
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
-- 
Ariel Constenla-Haile


signature.asc
Description: Digital signature

Re: building on Windows 10 breaks at guistdio.exe

2016-09-19 Thread Ariel Constenla-Haile 
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 stages together into one single output?
> I would also recommend installing as many packages in cygwin as possible
> without going through the extra step of installing lynx or apt-cyg... While
> that does make the environment more similar to a linux build environment,
> it's still an extra step and I believe it could be indicated as a second
> possibliity. Somewhere in the Step by Step guide I added which packages to
> choose in the cygwin interface if installing them from the cygwin
> interface. I think installing the packages from the cygwin interface should
> be indicated as the first step to take when first installing cygwin, adding
> all the necessary packages along with the first install.
> The only package I couldn't find from the cygwin interface was the Perl
> LWP::UserAgent package, so I installed that using "cpan -i LWP::UserAgent".

That is perl-LWP-Protocol-https, please see the updated version of
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO#General_Build_Requirements


Regards
-- 
Ariel Constenla-Haile


signature.asc
Description: Digital signature

Re: building on Windows 10 breaks at guistdio.exe

2016-09-19 Thread Patricia Shanahan 
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 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 installing as many packages in cygwin as possible
without going through the extra step of installing lynx or apt-cyg... While
that does make the environment more similar to a linux build environment,
it's still an extra step and I believe it could be indicated as a second
possibliity. Somewhere in the Step by Step guide I added which packages to
choose in the cygwin interface if installing them from the cygwin
interface. I think installing the packages from the cygwin interface should
be indicated as the first step to take when first installing cygwin, adding
all the necessary packages along with the first install.
The only package I couldn't find from the cygwin interface was the Perl
LWP::UserAgent package, so I installed that using "cpan -i LWP::UserAgent".


On Tue, Sep 20, 2016 at 12:25 AM, Patricia Shanahan  wrote:


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 that is
necessary. Could you test your Windows 10 build on a Windows 7 machine? Or
send me the output - that may be quicker than waiting for my Windows 10
build to go through.


On 9/19/2016 1:46 PM, John D'Orazio wrote:


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, Patricia Shanahan  wrote:

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 somewhere that maybe using 64 bit cygwin can resolve the

occupied addresses and child_fork_process errors. I made an attempt at
getting the build environment ready in 64 bit cygwin but configure is
complaining about not finding Visual Studio C++, while this does not
happen
in 32 bit cygwin (I'm passing in the with-cl-home flag so it shouldn't
have
any problem finding it... I'm reading it has something to do with
registry
keys, idk I have to look into this better).

...



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org







-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org







-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: building on Windows 10 breaks at guistdio.exe

2016-09-19 Thread Patricia Shanahan 
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 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:

  273.923309 : ERROR: D:/NSIS/makensis.exe
D:/source/aoo-trunk/main/instsetoo_native/
wntmsci12.pro/Apache_OpenOffice/msi/nsis/it/downloadtemplate.nsi | !
  273.923514 : !include: error in script:
"D:/source/aoo-trunk/main/instsetoo_native/
wntmsci12.pro/Apache_OpenOffice/msi/nsis/it\Italian_pack.nsh" on line 10
  273.923550 : Error in macro LANGFILE_INCLUDE on macroline 11
  273.923588 : Error in macro MUI_LANGUAGE_PACK on macroline 12
  273.923619 : Error in script
"D:/source/aoo-trunk/main/instsetoo_native/
wntmsci12.pro/Apache_OpenOffice/msi/nsis/it/downloadtemplate.nsi" on line
270 -- aborting creation process

Not sure what that might affect.

Also, here are my final working configure settings:

SDK_PATH="D:\Microsoft_SDKs\Windows\v7.0"

./configure --with-build-version="$(date +"%Y-%m-%d %H:%M:%S (%a, %d %b
%Y)")"
--with-directx-home="D:\Microsoft_DirectX_SDK_June_2010"
--with-frame-home="D:/Microsoft_SDKs/Windows/v7.0"
--with-psdk-home="D:/Microsoft_SDKs/Windows/v7.0"
--with-midl-path="D:/Microsoft_SDKs/Windows/v7.0/bin"
--with-ant-home="/cygdrive/d/apache-ant/apache-ant-1.9.7"
--with-nsis-path="D:/NSIS"
--with-jdk-home="C:/PROGRA~2/Java/JDK18~1.0_7"
--with-csc-path="C:/Windows/Microsoft.NET/Framework/v3.5"
--with-cl-home="C:/PROGRA~2/MI1DCA~1.0/VC"
--with-asm-home="C:/PROGRA~2/MI1DCA~1.0/VC/bin"
--with-mozilla-build="/cygdrive/d/mozilla-build"
--with-atl-include-dir=/cygdrive/c/WinDDK/7600.16385.1/inc/atl71
--with-atl-lib-dir=/cygdrive/c/WinDDK/7600.16385.1/lib/ATL/i386
--with-mfc-include-dir=/cygdrive/c/WinDDK/7600.16385.1/inc/mfc42
--with-mfc-lib-dir=/cygdrive/c/WinDDK/7600.16385.1/lib/Mfc/i386
--with-dmake-url="
http://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2;
--with-epm-url="
https://sourceforge.net/projects/oooextras.mirror/files/epm-3.7.tar.gz;
--without-junit
--without-stlport
--enable-win-x64-shellext
--enable-wiki-publisher
--enable-category-b
--enable-bundled-dictionaries
--with-lang="en-US it"

For those cases where I couldn't customize the install path, I used the
cygpath tool to get the shortened path as suggested on this page
https://wiki.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows#configure
(e.g. cygpath -m -s "C:\Path With Spaces\That Needs Shortening").




On Tue, Sep 20, 2016 at 3:22 AM, John D'Orazio <
john.dora...@cappellaniauniroma3.org> 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 stages together into one single output?
I would also recommend installing as many packages in cygwin as possible
without going through the extra step of installing lynx or apt-cyg... While
that does make the environment more similar to a linux build environment,
it's still an extra step and I believe it could be indicated as a second
possibliity. Somewhere in the Step by Step guide I added which packages to
choose in the cygwin interface if installing them from the cygwin
interface. I think installing the packages from the cygwin interface should
be indicated as the first step to take when first installing cygwin, adding
all the necessary packages along with the first install.
The only package I couldn't find from the cygwin interface was the Perl
LWP::UserAgent package, so I installed that using "cpan -i LWP::UserAgent".


On Tue, Sep 20, 2016 at 12:25 AM, Patricia Shanahan  wrote:


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 that is
necessary. Could you test your Windows 10 build on a Windows 7 machine? Or
send me the output - that may be quicker than waiting for my Windows 10
build to go through.


On 9/19/2016 1:46 PM, John D'Orazio wrote:


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, Patricia

Re: building on Windows 10 breaks at guistdio.exe

2016-09-19 Thread John D'Orazio 
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:

  273.923309 : ERROR: D:/NSIS/makensis.exe
D:/source/aoo-trunk/main/instsetoo_native/
wntmsci12.pro/Apache_OpenOffice/msi/nsis/it/downloadtemplate.nsi | !
  273.923514 : !include: error in script:
"D:/source/aoo-trunk/main/instsetoo_native/
wntmsci12.pro/Apache_OpenOffice/msi/nsis/it\Italian_pack.nsh" on line 10
  273.923550 : Error in macro LANGFILE_INCLUDE on macroline 11
  273.923588 : Error in macro MUI_LANGUAGE_PACK on macroline 12
  273.923619 : Error in script
"D:/source/aoo-trunk/main/instsetoo_native/
wntmsci12.pro/Apache_OpenOffice/msi/nsis/it/downloadtemplate.nsi" on line
270 -- aborting creation process

Not sure what that might affect.

Also, here are my final working configure settings:

SDK_PATH="D:\Microsoft_SDKs\Windows\v7.0"

./configure --with-build-version="$(date +"%Y-%m-%d %H:%M:%S (%a, %d %b
%Y)")"
--with-directx-home="D:\Microsoft_DirectX_SDK_June_2010"
--with-frame-home="D:/Microsoft_SDKs/Windows/v7.0"
--with-psdk-home="D:/Microsoft_SDKs/Windows/v7.0"
--with-midl-path="D:/Microsoft_SDKs/Windows/v7.0/bin"
--with-ant-home="/cygdrive/d/apache-ant/apache-ant-1.9.7"
--with-nsis-path="D:/NSIS"
--with-jdk-home="C:/PROGRA~2/Java/JDK18~1.0_7"
--with-csc-path="C:/Windows/Microsoft.NET/Framework/v3.5"
--with-cl-home="C:/PROGRA~2/MI1DCA~1.0/VC"
--with-asm-home="C:/PROGRA~2/MI1DCA~1.0/VC/bin"
--with-mozilla-build="/cygdrive/d/mozilla-build"
--with-atl-include-dir=/cygdrive/c/WinDDK/7600.16385.1/inc/atl71
--with-atl-lib-dir=/cygdrive/c/WinDDK/7600.16385.1/lib/ATL/i386
--with-mfc-include-dir=/cygdrive/c/WinDDK/7600.16385.1/inc/mfc42
--with-mfc-lib-dir=/cygdrive/c/WinDDK/7600.16385.1/lib/Mfc/i386
--with-dmake-url="
http://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2;
--with-epm-url="
https://sourceforge.net/projects/oooextras.mirror/files/epm-3.7.tar.gz;
--without-junit
--without-stlport
--enable-win-x64-shellext
--enable-wiki-publisher
--enable-category-b
--enable-bundled-dictionaries
--with-lang="en-US it"

For those cases where I couldn't customize the install path, I used the
cygpath tool to get the shortened path as suggested on this page
https://wiki.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows#configure
(e.g. cygpath -m -s "C:\Path With Spaces\That Needs Shortening").




On Tue, Sep 20, 2016 at 3:22 AM, John D'Orazio <
john.dora...@cappellaniauniroma3.org> 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 stages together into one single output?
> I would also recommend installing as many packages in cygwin as possible
> without going through the extra step of installing lynx or apt-cyg... While
> that does make the environment more similar to a linux build environment,
> it's still an extra step and I believe it could be indicated as a second
> possibliity. Somewhere in the Step by Step guide I added which packages to
> choose in the cygwin interface if installing them from the cygwin
> interface. I think installing the packages from the cygwin interface should
> be indicated as the first step to take when first installing cygwin, adding
> all the necessary packages along with the first install.
> The only package I couldn't find from the cygwin interface was the Perl
> LWP::UserAgent package, so I installed that using "cpan -i LWP::UserAgent".
>
>
> On Tue, Sep 20, 2016 at 12:25 AM, Patricia Shanahan  wrote:
>
>> 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 that is
>> necessary. Could you test your Windows 10 build on a Windows 7 machine? Or
>> send me the output - that may be quicker than waiting for my Windows 10
>> build to go through.
>>
>>
>> On 9/19/2016 1:46 PM, John D'Orazio wrote:
>>
>>> 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, Patricia Shanahan  wrote:
>>>
>>> I had installed 64-bit

Re: building on Windows 10 breaks at guistdio.exe

2016-09-19 Thread John D'Orazio 
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 installing as many packages in cygwin as possible
without going through the extra step of installing lynx or apt-cyg... While
that does make the environment more similar to a linux build environment,
it's still an extra step and I believe it could be indicated as a second
possibliity. Somewhere in the Step by Step guide I added which packages to
choose in the cygwin interface if installing them from the cygwin
interface. I think installing the packages from the cygwin interface should
be indicated as the first step to take when first installing cygwin, adding
all the necessary packages along with the first install.
The only package I couldn't find from the cygwin interface was the Perl
LWP::UserAgent package, so I installed that using "cpan -i LWP::UserAgent".


On Tue, Sep 20, 2016 at 12:25 AM, Patricia Shanahan  wrote:

> 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 that is
> necessary. Could you test your Windows 10 build on a Windows 7 machine? Or
> send me the output - that may be quicker than waiting for my Windows 10
> build to go through.
>
>
> On 9/19/2016 1:46 PM, John D'Orazio wrote:
>
>> 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, Patricia Shanahan  wrote:
>>
>> 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 somewhere that maybe using 64 bit cygwin can resolve the
 occupied addresses and child_fork_process errors. I made an attempt at
 getting the build environment ready in 64 bit cygwin but configure is
 complaining about not finding Visual Studio C++, while this does not
 happen
 in 32 bit cygwin (I'm passing in the with-cl-home flag so it shouldn't
 have
 any problem finding it... I'm reading it has something to do with
 registry
 keys, idk I have to look into this better).

 ...
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>>>
>>>
>>
>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
John R. D'Orazio

Re: building on Windows 10 breaks at guistdio.exe

2016-09-19 Thread Patricia Shanahan 
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 that 
is necessary. Could you test your Windows 10 build on a Windows 7 
machine? Or send me the output - that may be quicker than waiting for my 
Windows 10 build to go through.


On 9/19/2016 1:46 PM, John D'Orazio wrote:

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, Patricia Shanahan  wrote:


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 somewhere that maybe using 64 bit cygwin can resolve the
occupied addresses and child_fork_process errors. I made an attempt at
getting the build environment ready in 64 bit cygwin but configure is
complaining about not finding Visual Studio C++, while this does not
happen
in 32 bit cygwin (I'm passing in the with-cl-home flag so it shouldn't
have
any problem finding it... I'm reading it has something to do with registry
keys, idk I have to look into this better).


...


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org







-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: building on Windows 10 breaks at guistdio.exe

2016-09-19 Thread John D'Orazio 
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, Patricia Shanahan  wrote:

> 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 somewhere that maybe using 64 bit cygwin can resolve the
>> occupied addresses and child_fork_process errors. I made an attempt at
>> getting the build environment ready in 64 bit cygwin but configure is
>> complaining about not finding Visual Studio C++, while this does not
>> happen
>> in 32 bit cygwin (I'm passing in the with-cl-home flag so it shouldn't
>> have
>> any problem finding it... I'm reading it has something to do with registry
>> keys, idk I have to look into this better).
>>
> ...
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
John R. D'Orazio

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

2016-09-19 Thread Matthias Seidel 
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).
>> You might not incidentally know Carsten Müller or Jörg Skottke?
>
> sure, colleagues for many years. And of course many others more.
>
>>> So, I suggest to expand the build.lst to this setup.
>>
>> +1 for the proposal!
>
> Marcus
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature

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

2016-09-19 Thread Marcus 
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 big 
interest. Now it also depends on all of us to fill this interest with life.


I'm happy to go on to work together with you. :-)

Marcus



Am 09/19/2016 06:11 PM, schrieb Dennis E. Hamilton:

[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 Stuart Swales
+1 Kazunari Hirano
+1 Dr. Michael Stehmann
+1 Carl Marcum
+1 Andrea Pescetti
+1 Jörg Schmidt
+1 Olaf Felka
+1 Dave Fisher
+1 Dave Barton
+1 Regina Henschel
+1 Ariel Constenla-Haile
+1 Roberto Galoppini
+1 Phillip Rhodes
+1 Keith N. McKenna

 0 Marcus Lange
 0 Peter Kovacs

21  +1 Approvals
 2   0 Abstentions
 0  -1 Disapprovals


I will submit the resolution to the Board of the Apache Software Foundation for 
consideration at the Wednesday, 2016-09-21 meeting.

  - Dennis


-Original Message-
From: Dennis E. Hamilton [mailto:orc...@apache.org]
Sent: Thursday, September 15, 2016 08:36
To: dev@openoffice.apache.org
Subject: [VOTE] Recommend Marcus Lange (marcus) as the New Vice
President for Apache OpenOffice

[BCC to PMC]

 RESOLUTION: That Marcus Lange (marcus) be recommended to the
 Apache Software Foundation Board to serve as Vice President
 for Apache OpenOffice.

The Vice President for Apache OpenOffice serves in accordance with and
subject to the direction of the Board of Directors and the Bylaws of the
Foundation.  The Vice President for Apache OpenOffice is the Chair of
the OpenOffice Project Management Committee.

Please vote by reply to this dev@-list thread on approval of the
resolution.

  [  ] +1 Approve
  [  ]  0 Abstain
  [  ] -1 Disapprove, with explanation

This is a procedural vote and a majority of binding votes is sufficient
to carry the resolution.

Please do not do anything but [VOTE] (with any -1 explanations) on this
thread.

To discuss this vote or the process, please use a [DISCUSS][VOTE] reply
rather than discussing on the [VOTE] thread.

The [VOTE] will conclude no sooner than Monday, 2016-09-19T16:00Z.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

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

2016-09-19 Thread 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).
You might not incidentally know Carsten Müller or Jörg Skottke?


sure, colleagues for many years. And of course many others more.


So, I suggest to expand the build.lst to this setup.


+1 for the proposal!


Marcus


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

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

2016-09-19 Thread 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?

> So, I suggest to expand the build.lst to this setup. 

+1 for the proposal!

Regards

Matthias



smime.p7s
Description: S/MIME Cryptographic Signature

Re: 4.1.4 Release Manager?

2016-09-19 Thread Peter Kovacs 
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.
> >
> > 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 open office as
> > upcoming result.
> >
> > The arguments were:
> > No update
> > Outdated developer plan
> > Only 6 active developers
> > Dropping user numbers
> > Dennis mail of retirement  (that it is a discussion point is briefly
> > ignored)
> >
> > But true, maybe it is not worth the attention ^^
>
> the attention should come from the release itself. Sure a nice picture
> looks always good. Do we have one? Can you do it? Can we get it fast? I
> think not. ;-)
>
> Therefore I don't want to wait for this.
>
> Marcus
>
>
>
> > Patricia Shanahan  schrieb am So., 18. Sep. 2016, 14:34:
> >
> >>
> >>
> >> On 9/18/2016 12:14 AM, Marcus wrote:
> >>> Am 09/18/2016 07:45 AM, schrieb Peter Kovacs:
>  Hmm, does anyone know an artist that has some time and can draw a
> splash
>  screen?
>  I would love to see the next edition Called 4.1.3 Phoenix addition,
> And
>  I would love to see a Splashscreen that shows an Phönix carry the AOOo
>  Logo upward.
>  That would make a statement. Actually thinking of it, if this is liked
>  by the community I would pledge 50 Euro for an acceptable artwork
> (means
>  liked by AOOo. If this is dev or all involved we could discuss.).
>  Haha.
> >>>
> >>> a new splash screen would be indeed cool. But for a bugfix release? No,
> >>> let's do this art work for 4.2.0. Then we will have more time for
> ideas,
> >>> too.
> >>
> >> I agree. We have enough to do for 4.1.3 just dealing with build
> >> glitches. Let's keep the bugfix point releases to fixing bugs, and go
> >> splashy with the next feature release.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
> --

Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort
wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks
werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre
Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch
kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre
Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google
konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht
wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu
verhandeln.

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

2016-09-19 Thread Marcus 
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
- one Asian language (ko, ja, zh-CN, zh-TW) to cover BIDI and font
  problems

So, I suggest to expand the build.lst to this setup.

Marcus

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

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

2016-09-19 Thread Matthias Seidel 
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 Pescetti:
> 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 they are fixed on trunk ("4.2.0-dev"), this
> would be a useful information. If you don't know where to find
> buildbot builds, just ask.
>
> Regards,
>   Andrea.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: building on Windows 10 breaks at guistdio.exe

2016-09-19 Thread Patricia Shanahan 
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 somewhere that maybe using 64 bit cygwin can resolve the
occupied addresses and child_fork_process errors. I made an attempt at
getting the build environment ready in 64 bit cygwin but configure is
complaining about not finding Visual Studio C++, while this does not happen
in 32 bit cygwin (I'm passing in the with-cl-home flag so it shouldn't have
any problem finding it... I'm reading it has something to do with registry
keys, idk I have to look into this better).

...

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

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

2016-09-19 Thread Matthias Seidel 
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 comfirmed for german, french and swedish. ;-) One
was confirmed on Mac.
And maybe you don't use Ubuntu (or a distribution based on it)?

"Unusable" might be too strong, but at least 3 different actions in
Writer caused a complete crash. It is like try and error... ;-)

Anyway, as a long time AOO-user I would like to have it fully functional
on Ubuntu.
Sooner or later... ;-)

kind regards

Matthias Seidel




smime.p7s
Description: S/MIME Cryptographic Signature

Re: 4.1.4 Release Manager?

2016-09-19 Thread Marcus 

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.
Referring Dennis email about the idea of retirement for open office as
upcoming result.

The arguments were:
No update
Outdated developer plan
Only 6 active developers
Dropping user numbers
Dennis mail of retirement  (that it is a discussion point is briefly
ignored)

But true, maybe it is not worth the attention ^^


the attention should come from the release itself. Sure a nice picture 
looks always good. Do we have one? Can you do it? Can we get it fast? I 
think not. ;-)


Therefore I don't want to wait for this.

Marcus




Patricia Shanahan  schrieb am So., 18. Sep. 2016, 14:34:




On 9/18/2016 12:14 AM, Marcus wrote:

Am 09/18/2016 07:45 AM, schrieb Peter Kovacs:

Hmm, does anyone know an artist that has some time and can draw a splash
screen?
I would love to see the next edition Called 4.1.3 Phoenix addition, And
I would love to see a Splashscreen that shows an Phönix carry the AOOo
Logo upward.
That would make a statement. Actually thinking of it, if this is liked
by the community I would pledge 50 Euro for an acceptable artwork (means
liked by AOOo. If this is dev or all involved we could discuss.).
Haha.


a new splash screen would be indeed cool. But for a bugfix release? No,
let's do this art work for 4.2.0. Then we will have more time for ideas,
too.


I agree. We have enough to do for 4.1.3 just dealing with build
glitches. Let's keep the bugfix point releases to fixing bugs, and go
splashy with the next feature release.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

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

2016-09-19 Thread Marcus 

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 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.



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?


With this I don't say it should not go into 4.1.3. At the end it's the 
decision of our release manager where to put the fix.




But I am only a user and leave those decisions to the developers... ;-)


Marcus




Am 19.09.2016 um 15:10 schrieb Patricia Shanahan:

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 styles to text
Date: Mon, 19 Sep 2016 11:33:56 +
From: bugzi...@apache.org
Reply-To: iss...@openoffice.apache.org
To: iss...@openoffice.apache.org

https://bz.apache.org/ooo/show_bug.cgi?id=125147

--- Comment #26 from hanya  ---
(In reply to Matthias Seidel from comment #25)

(In reply to hanya from comment #24)

Fixed on trunk, revision 1668939.


Has this fix been applied/tested only for english language?

Because the same crash still occurs in AOO4.1.2 on other languages
(german,
french and swedish are confirmed). -> Issue 126980

I could confirm issue 126980 even with en-US on Ubutntu 16.04.1. This
issue
125147 does not related to any language pack. But the reson of the
crash is the same, null pointer referencing.


I see the target milestone is 4.2.0?
It would be better now to set it to 4.1.3 and ask for release
blocker...

If it would be part of 4.1.3, it's better. I thought next release
would be 4.2
when I found the fix.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

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

2016-09-19 Thread Andrea Pescetti 

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 they are fixed on trunk ("4.2.0-dev"), this would 
be a useful information. If you don't know where to find buildbot 
builds, just ask.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

FW: Resolution to Change the Apache OpenOffice Chair

2016-09-19 Thread Dennis E. Hamilton 
[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 structured such that it is easily converted to the (draft) 
minutes of that same meeting by the Secretary.  

Then when the Board approves those minutes at a future Board meeting, the 
approved minutes are published on the web at 
.

When Change of Chair resolution is approved at a meeting, that goes into effect 
immediately.  The new Chair receives a welcome message and instructions on some 
steps to take to be involved as a Chair.  This includes having permission to 
edit certain files that are the Chair's first duty.

 - Dennis

> -Original Message-
> From: Dennis E. Hamilton [mailto:orc...@apache.org]
> Sent: Monday, September 19, 2016 09:47
> To: bo...@apache.org
> Subject: Resolution to Change the Apache OpenOffice Chair
> 
> Already added to the Special Orders:
> 
> C. Change the Apache OpenOffice Project Chair
> 
>WHEREAS, the Board of Directors heretofore appointed Dennis E.
> Hamilton
>to the office of Vice President, Apache OpenOffice, and
> 
>WHEREAS, the Board of Directors is in receipt of the resignation
> of
>Dennis E. Hamilton from the office of Vice President, Apache
>OpenOffice, and
> 
>WHEREAS, the Community of the Apache OpenOffice project
>has chosen to recommend Marcus Lange as the successor to the
>post;
> 
>NOW, THEREFORE, BE IT RESOLVED, that Dennis E. Hamilton is
> relieved and
>discharged from the duties and responsibilities of the office of
> Vice
>President, Apache OpenOffice, and
> 
>BE IT FURTHER RESOLVED, that Marcus Lange be and hereby is
>appointed to the office of Vice President, Apache OpenOffice, to
> serve
>in accordance with and subject to the direction of the Board of
>Directors and the Bylaws of the Foundation until death,
> resignation,
>retirement, removal or disqualification, or until a successor is
>appointed.
> 
> 
> 
> 



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

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

2016-09-19 Thread Dennis E. Hamilton 
[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 Stuart Swales
   +1 Kazunari Hirano
   +1 Dr. Michael Stehmann
   +1 Carl Marcum
   +1 Andrea Pescetti
   +1 Jörg Schmidt
   +1 Olaf Felka
   +1 Dave Fisher
   +1 Dave Barton
   +1 Regina Henschel
   +1 Ariel Constenla-Haile
   +1 Roberto Galoppini
   +1 Phillip Rhodes
   +1 Keith N. McKenna

0 Marcus Lange
0 Peter Kovacs

   21  +1 Approvals
2   0 Abstentions
0  -1 Disapprovals


I will submit the resolution to the Board of the Apache Software Foundation for 
consideration at the Wednesday, 2016-09-21 meeting.

 - Dennis

> -Original Message-
> From: Dennis E. Hamilton [mailto:orc...@apache.org]
> Sent: Thursday, September 15, 2016 08:36
> To: dev@openoffice.apache.org
> Subject: [VOTE] Recommend Marcus Lange (marcus) as the New Vice
> President for Apache OpenOffice
> 
> [BCC to PMC]
> 
> RESOLUTION: That Marcus Lange (marcus) be recommended to the
> Apache Software Foundation Board to serve as Vice President
> for Apache OpenOffice.
> 
> The Vice President for Apache OpenOffice serves in accordance with and
> subject to the direction of the Board of Directors and the Bylaws of the
> Foundation.  The Vice President for Apache OpenOffice is the Chair of
> the OpenOffice Project Management Committee.
> 
> Please vote by reply to this dev@-list thread on approval of the
> resolution.
> 
>  [  ] +1 Approve
>  [  ]  0 Abstain
>  [  ] -1 Disapprove, with explanation
> 
> This is a procedural vote and a majority of binding votes is sufficient
> to carry the resolution.
> 
> Please do not do anything but [VOTE] (with any -1 explanations) on this
> thread.
> 
> To discuss this vote or the process, please use a [DISCUSS][VOTE] reply
> rather than discussing on the [VOTE] thread.
> 
> The [VOTE] will conclude no sooner than Monday, 2016-09-19T16:00Z.
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

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

2016-09-19 Thread Pedro Giffuni 

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 already late you should probably reconsider bringing in 
some fixes to known bugs. If the idea is just that 4.1.3 = 4.1.2 + 
CVE-2016-15-13, then it seems to be a huge waste of bandwidth for both 
mirrors and end users.


All just IMHO,

Pedro.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: building on Windows 10 breaks at guistdio.exe

2016-09-19 Thread John D'Orazio 
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 last instsetoo_native module remains.

This last module is not completing, I keep getting perl child_fork_process
issues with address already busy etc.

I've been trying with solutions I'm finding online with a dash rebaseall,
haven't succeeded yet but will attempt again shortly.

I also read somewhere that maybe using 64 bit cygwin can resolve the
occupied addresses and child_fork_process errors. I made an attempt at
getting the build environment ready in 64 bit cygwin but configure is
complaining about not finding Visual Studio C++, while this does not happen
in 32 bit cygwin (I'm passing in the with-cl-home flag so it shouldn't have
any problem finding it... I'm reading it has something to do with registry
keys, idk I have to look into this better).

On Sep 18, 2016 20:05, "Patricia Shanahan"  wrote:

> Please excuse the delay responding - I put it aside hoping that someone
> with more knowledge would respond, and then got involved in other things.
>
> One possibility is that solver/420/wntmsci12.pro/xml/ was partially built
> due to an earlier failure. I suggest deleting solver/420/wntmsci12.pro
> and trying again.
>
> On 9/15/2016 5:52 AM, John D'Orazio wrote:
>
>> Patricia you are correct, after a few more attempts the desktop module did
>> build successfully. Now I'm up to the postprocess module, with this error:
>>
>> Entering /cygdrive/d/source/aoo-trunk/main/postprocess/packcomponents
>>
>> dmake:  Error: -- `/cygdrive/d/source/aoo-trunk/main/solver/420/
>> wntmsci12.pro/xml/chartcontroller.component' not found, and can't be made
>>
>> 1 module(s):
>> postprocess
>> need(s) to be rebuilt
>>
>> Reason(s):
>>
>> ERROR: error 65280 occurred while making
>> /cygdrive/d/source/aoo-trunk/main/postprocess/packcomponents
>>
>> When you have fixed the errors in that module you can resume the build by
>> running:
>>
>> build --all:postprocess
>>
>>
>> Any ideas on this "chartcontroller.component"?
>>
>>
>> On Wed, Sep 14, 2016 at 11:58 PM, John D'Orazio <
>> john.dora...@cappellaniauniroma3.org> wrote:
>>
>> If it can be of any use to understand better the problem, I'm using this
>>> configuration:
>>>
>>> SDK_PATH="D:\Microsoft_SDKs\Windows\v7.0"
>>>
>>> ./configure --with-frame-home="$SDK_PATH" --with-psdk-home="$SDK_PATH"
>>> --with-midl-path="$SDK_PATH/bin" --with-directx-home="D:\
>>> Microsoft_DirectX_SDK_June_2010" --with-ant-home="/cygdrive/d/a
>>> pache-ant/apache-ant-1.9.7"
>>> --with-jdk-home="C:\Program Files (x86)\Java\jdk1.8.0_73"
>>> --with-csc-path="C:\Windows\Microsoft.NET\Framework\v3.5"
>>> --with-dmake-url="http://sourceforge.net/projects/
>>> oooextras.mirror/files/dmake-4.12.tar.bz2" --with-epm-url="http://www.
>>> msweet.org/files/project2/epm-3.7-source.tar.gz" --disable-pch
>>> --disable-atl --disable-activex --without-junit
>>>
>>>
>>> On Wed, Sep 14, 2016 at 9:39 PM, John D'Orazio >> cappellaniauniroma3.org> wrote:
>>>
>>> So I've taken courage thanks also to the work done by Patricia Shanahan
 on building OpenOffice in Windows 7 and Windows 8.1. I'm using Windows
 10,
 and I've sorted through the first few obstacles and my build has now
 been
 running for 5-6 hours without any trouble. Until now that is. It just
 broke
 while building "guistdio.exe" in the desktop module. I'm not really
 seeing
 much information that can help me though, can any pick out what the
 trouble
 might be? Here is the last part of the build output:

 Compiling: desktop/test/deployment/active/active_native.cxx
 Making:test_deployment_active.lib
 Making:module definition file active_native.uno.def
 Making:itest_deployment_active_t1.lib
 lib -machine:IX86 @D:/cygwin/tmp/mktDdH6P
 Microsoft (R) Library Manager Version 9.00.30729.01
 Copyright (C) Microsoft Corporation.  All rights reserved.

 -out:../../../wntmsci12.pro/lib/itest_deployment_active_t1.lib
 -def:../../../wntmsci12.pro/misc/active_native.uno.def
Creating library ../../../wntmsci12.pro/lib/ite
 st_deployment_active_t1.lib and object ../../../wntmsci12.pro/lib/ite
 st_deployment_active_t1.exp
 Making:active_native.uno.dll
 Microsoft (R) Windows (R) Resource Compiler Version 6.1.7600.16385
 Copyright (C) Microsoft Corporation.  All rights reserved.

 Microsoft (R) Incremental Linker Version 9.00.30729.01
 Copyright (C) Microsoft Corporation.  All rights reserved.

 /MAP /OPT:NOREF -safeseh -nxcompat -dynamicbase -NODEFAULTLIB -RELEASE
 -DEBUG -INCREMENTAL:NO /SUBSYSTEM:CONSOLE /DLL -out:../../../
 wntmsci12.pro/bin/active_native.uno.dll

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

2016-09-19 Thread Matthias Seidel 
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 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).
>> 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 um 15:10 schrieb Patricia Shanahan:
>>> 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 styles to text
>>> Date: Mon, 19 Sep 2016 11:33:56 +
>>> From: bugzi...@apache.org
>>> Reply-To: iss...@openoffice.apache.org
>>> To: iss...@openoffice.apache.org
>>>
>>> https://bz.apache.org/ooo/show_bug.cgi?id=125147
>>>
>>> --- Comment #26 from hanya  ---
>>> (In reply to Matthias Seidel from comment #25)
 (In reply to hanya from comment #24)
> Fixed on trunk, revision 1668939.

 Has this fix been applied/tested only for english language?

 Because the same crash still occurs in AOO4.1.2 on other languages
 (german,
 french and swedish are confirmed). -> Issue 126980
>>> I could confirm issue 126980 even with en-US on Ubutntu 16.04.1. This
>>> issue
>>> 125147 does not related to any language pack. But the reson of the
>>> crash is the same, null pointer referencing.
>>>
 I see the target milestone is 4.2.0?
 It would be better now to set it to 4.1.3 and ask for release
 blocker...
>>> If it would be part of 4.1.3, it's better. I thought next release
>>> would be 4.2
>>> when I found the fix.
>>>
>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature

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

2016-09-19 Thread 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).
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 um 15:10 schrieb Patricia Shanahan:

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 styles to text
Date: Mon, 19 Sep 2016 11:33:56 +
From: bugzi...@apache.org
Reply-To: iss...@openoffice.apache.org
To: iss...@openoffice.apache.org

https://bz.apache.org/ooo/show_bug.cgi?id=125147

--- Comment #26 from hanya  ---
(In reply to Matthias Seidel from comment #25)

(In reply to hanya from comment #24)

Fixed on trunk, revision 1668939.


Has this fix been applied/tested only for english language?

Because the same crash still occurs in AOO4.1.2 on other languages
(german,
french and swedish are confirmed). -> Issue 126980

I could confirm issue 126980 even with en-US on Ubutntu 16.04.1. This
issue
125147 does not related to any language pack. But the reson of the
crash is the same, null pointer referencing.


I see the target milestone is 4.2.0?
It would be better now to set it to 4.1.3 and ask for release blocker...

If it would be part of 4.1.3, it's better. I thought next release
would be 4.2
when I found the fix.






-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

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

2016-09-19 Thread Matthias Seidel 
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 um 15:10 schrieb Patricia Shanahan:
> 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 styles to text
> Date: Mon, 19 Sep 2016 11:33:56 +
> From: bugzi...@apache.org
> Reply-To: iss...@openoffice.apache.org
> To: iss...@openoffice.apache.org
>
> https://bz.apache.org/ooo/show_bug.cgi?id=125147
>
> --- Comment #26 from hanya  ---
> (In reply to Matthias Seidel from comment #25)
>> (In reply to hanya from comment #24)
>> > Fixed on trunk, revision 1668939.
>>
>> Has this fix been applied/tested only for english language?
>>
>> Because the same crash still occurs in AOO4.1.2 on other languages
>> (german,
>> french and swedish are confirmed). -> Issue 126980
> I could confirm issue 126980 even with en-US on Ubutntu 16.04.1. This
> issue
> 125147 does not related to any language pack. But the reson of the
> crash is the same, null pointer referencing.
>
>> I see the target milestone is 4.2.0?
>> It would be better now to set it to 4.1.3 and ask for release blocker...
> If it would be part of 4.1.3, it's better. I thought next release
> would be 4.2
> when I found the fix.
>




smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: [Issue 125147] CRASH applying styles to text

2016-09-19 Thread Patricia Shanahan 
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 styles to text
Date: Mon, 19 Sep 2016 11:33:56 +
From: bugzi...@apache.org
Reply-To: iss...@openoffice.apache.org
To: iss...@openoffice.apache.org

https://bz.apache.org/ooo/show_bug.cgi?id=125147

--- Comment #26 from hanya  ---
(In reply to Matthias Seidel from comment #25)

(In reply to hanya from comment #24)
> Fixed on trunk, revision 1668939.

Has this fix been applied/tested only for english language?

Because the same crash still occurs in AOO4.1.2 on other languages (german,
french and swedish are confirmed). -> Issue 126980

I could confirm issue 126980 even with en-US on Ubutntu 16.04.1. This issue
125147 does not related to any language pack. But the reson of the crash 
is the same, null pointer referencing.



I see the target milestone is 4.2.0?
It would be better now to set it to 4.1.3 and ask for release blocker...
If it would be part of 4.1.3, it's better. I thought next release would 
be 4.2

when I found the fix.

--
You are receiving this mail because:
You are the assignee for the issue.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: How do all the binaries get built?

2016-09-19 Thread Jim Jagielski 
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
> 
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5
> 
> is still incomplete (see the "Ready to setup release build machines?" 
> thread). I'll make sure it is updated during the weekend, so we have a 
> "standard recipe" to get the build dependencies that are not available on 
> CentOS 5 through standard channels.
> 
> A CentOS 5 32-bit buildbot would be more useful than a 64-bit one, so that we 
> can differentiate further (I already have the 64-bit one working, with a test 
> run of builds coming this weekend).
> 
> Regards,
>  Andrea.
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Apache OpenOffice on google+

2016-09-19 Thread Matthias Seidel 
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

Matthias Seidel




smime.p7s
Description: S/MIME Cryptographic Signature

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

2016-09-19 Thread Jan Høydahl 
[X] +1 Approve

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com

Re: 4.1.4 Release Manager?

2016-09-19 Thread 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.
Referring Dennis email about the idea of retirement for open office as
upcoming result.

The arguments were:
No update
Outdated developer plan
Only 6 active developers
Dropping user numbers
Dennis mail of retirement  (that it is a discussion point is briefly
ignored)

But true, maybe it is not worth the attention ^^

Patricia Shanahan  schrieb am So., 18. Sep. 2016, 14:34:

>
>
> On 9/18/2016 12:14 AM, Marcus wrote:
> > Am 09/18/2016 07:45 AM, schrieb Peter Kovacs:
> >> Hmm, does anyone know an artist that has some time and can draw a splash
> >> screen?
> >> I would love to see the next edition Called 4.1.3 Phoenix addition, And
> >> I would love to see a Splashscreen that shows an Phönix carry the AOOo
> >> Logo upward.
> >> That would make a statement. Actually thinking of it, if this is liked
> >> by the community I would pledge 50 Euro for an acceptable artwork (means
> >> liked by AOOo. If this is dev or all involved we could discuss.).
> >> Haha.
> >
> > a new splash screen would be indeed cool. But for a bugfix release? No,
> > let's do this art work for 4.2.0. Then we will have more time for ideas,
> > too.
>
> I agree. We have enough to do for 4.1.3 just dealing with build
> glitches. Let's keep the bugfix point releases to fixing bugs, and go
> splashy with the next feature release.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
> --

Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort
wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks
werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre
Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch
kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre
Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google
konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht
wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu
verhandeln.