date:20201021

Here is hoping 4th time is the charm...

http://home.apache.org/~jim/AOO-builds/

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

Re: AOO418-RC2: General Error on opening files on Ubuntu

2020-10-21 Thread Pedro Lino

Hi Jim

I'm afraid not...

FYI I just finished compiling under Ubuntu 18.04.5 x64 using

./configure --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" 
--with-dmake-url=https://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
 --enable-opengl --disable-odk --enable-category-b --enable-bundled-dictionaries

and everything works as expected with no error messages.

Regards,
Pedro

> On 10/21/2020 1:28 PM Jim Jagielski  wrote:
> 
>  
> Here is hoping 4th time is the charm...
> 
> http://home.apache.org/~jim/AOO-builds/
> 
> -
> 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: AOO418-RC2: General Error on opening files on Ubuntu

Is it just ubuntu we are having these issues with? What was the last 4.1.8-dev 
version that worked OK?

> On Oct 21, 2020, at 9:41 AM, Pedro Lino  wrote:
> 
> Hi Jim
> 
> I'm afraid not...
> 
> FYI I just finished compiling under Ubuntu 18.04.5 x64 using
> 
> ./configure --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" 
> --with-dmake-url=https://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
>  --enable-opengl --disable-odk --enable-category-b 
> --enable-bundled-dictionaries
> 
> and everything works as expected with no error messages.
> 
> Regards,
> Pedro
> 
>> On 10/21/2020 1:28 PM Jim Jagielski  wrote:
>> 
>> 
>> Here is hoping 4th time is the charm...
>> 
>>http://home.apache.org/~jim/AOO-builds/
>> 
>> -
>> 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: AOO418-RC2: General Error on opening files on Ubuntu

2020-10-21 Thread Pedro Lino

Hi again

> On 10/21/2020 2:51 PM Jim Jagielski  wrote:
> 
>  
> Is it just ubuntu we are having these issues with? What was the last 
> 4.1.8-dev version that worked OK?

In case my message was not clear: the build I compiled today in Ubuntu 18.04.5 
x64 works perfectly.

If your question is if the error messages that popup when using  your builds 
only show up on Ubuntu, then I can not answer. I don't use other distros.

Regards,
Pedro

 
> > On Oct 21, 2020, at 9:41 AM, Pedro Lino  wrote:
> > 
> > Hi Jim
> > 
> > I'm afraid not...
> > 
> > FYI I just finished compiling under Ubuntu 18.04.5 x64 using
> > 
> > ./configure --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" 
> > --with-dmake-url=https://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
> >  --enable-opengl --disable-odk --enable-category-b 
> > --enable-bundled-dictionaries
> > 
> > and everything works as expected with no error messages.
> > 
> > Regards,
> > Pedro
> > 
> >> On 10/21/2020 1:28 PM Jim Jagielski  wrote:
> >> 
> >> 
> >> Here is hoping 4th time is the charm...
> >> 
> >>http://home.apache.org/~jim/AOO-builds/
> >> 
> >> -
> >> 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: AOO418-RC2: General Error on opening files on Ubuntu

Hi,

Am 21.10.20 um 16:01 schrieb Pedro Lino:
> Hi again
>
>> On 10/21/2020 2:51 PM Jim Jagielski  wrote:
>>
>>  
>> Is it just ubuntu we are having these issues with? What was the last 
>> 4.1.8-dev version that worked OK?
> In case my message was not clear: the build I compiled today in Ubuntu 
> 18.04.5 x64 works perfectly.
>
> If your question is if the error messages that popup when using  your builds 
> only show up on Ubuntu, then I can not answer. I don't use other distros.

We have at least confirmations from Debian, so I suspect all Debian
based distros are affected...

Maybe some others could find the time to test now?

Regards,

   Matthias

>
> Regards,
> Pedro
>
>  
>>> On Oct 21, 2020, at 9:41 AM, Pedro Lino  wrote:
>>>
>>> Hi Jim
>>>
>>> I'm afraid not...
>>>
>>> FYI I just finished compiling under Ubuntu 18.04.5 x64 using
>>>
>>> ./configure --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" 
>>> --with-dmake-url=https://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
>>>  --enable-opengl --disable-odk --enable-category-b 
>>> --enable-bundled-dictionaries
>>>
>>> and everything works as expected with no error messages.
>>>
>>> Regards,
>>> Pedro
>>>
 On 10/21/2020 1:28 PM Jim Jagielski  wrote:


 Here is hoping 4th time is the charm...

http://home.apache.org/~jim/AOO-builds/

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



smime.p7s
Description: S/MIME Cryptographic Signature

Re: AOO418-RC2: General Error on opening files on Ubuntu

As I've said, the build system has not changed a whit between 4.1.7 and now, so 
there is something with the various changes causing these issues. One way of 
tracking this down is finding out when the last version of 4.1.8-dev worked. 
The problem is that as long as the builds I provide crash, then we cannot 
release the Linux 32/64 bit community builds, at least not without changing the 
build system, which is something we should NOT do between patch versions.

I may have to start playing around w/ git bisect or, at least, rebuild 4.1.7 
and ensure that something didn't sneak into the build environ.

> On Oct 21, 2020, at 10:01 AM, Pedro Lino  
> wrote:
> 
> Hi again
> 
>> On 10/21/2020 2:51 PM Jim Jagielski > > wrote:
>> 
>> 
>> Is it just ubuntu we are having these issues with? What was the last 
>> 4.1.8-dev version that worked OK?
> 
> In case my message was not clear: the build I compiled today in Ubuntu 
> 18.04.5 x64 works perfectly.
> 
> If your question is if the error messages that popup when using  your builds 
> only show up on Ubuntu, then I can not answer. I don't use other distros.
> 
> Regards,
> Pedro
> 
> 
>>> On Oct 21, 2020, at 9:41 AM, Pedro Lino  wrote:
>>> 
>>> Hi Jim
>>> 
>>> I'm afraid not...
>>> 
>>> FYI I just finished compiling under Ubuntu 18.04.5 x64 using
>>> 
>>> ./configure --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" 
>>> --with-dmake-url=https://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
>>>  --enable-opengl --disable-odk --enable-category-b 
>>> --enable-bundled-dictionaries
>>> 
>>> and everything works as expected with no error messages.
>>> 
>>> Regards,
>>> Pedro
>>> 
 On 10/21/2020 1:28 PM Jim Jagielski  wrote:
 
 
 Here is hoping 4th time is the charm...
 
   http://home.apache.org/~jim/AOO-builds/
 
 -
 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: AOO418-RC2: General Error on opening files on Ubuntu

2020-10-21 Thread Rory O'Farrell

On Wed, 21 Oct 2020 10:39:57 -0400
Jim Jagielski  wrote:

> As I've said, the build system has not changed a whit between 4.1.7 and now, 
> so there is something with the various changes causing these issues. One way 
> of tracking this down is finding out when the last version of 4.1.8-dev 
> worked. The problem is that as long as the builds I provide crash, then we 
> cannot release the Linux 32/64 bit community builds, at least not without 
> changing the build system, which is something we should NOT do between patch 
> versions.
> 
> I may have to start playing around w/ git bisect or, at least, rebuild 4.1.7 
> and ensure that something didn't sneak into the build environ.

Might there be some crosstalk with another application?  Java is the obvious 
first suspect.

Rory


> 
> > On Oct 21, 2020, at 10:01 AM, Pedro Lino  
> > wrote:
> > 
> > Hi again
> > 
> >> On 10/21/2020 2:51 PM Jim Jagielski  >> > wrote:
> >> 
> >> 
> >> Is it just ubuntu we are having these issues with? What was the last 
> >> 4.1.8-dev version that worked OK?
> > 
> > In case my message was not clear: the build I compiled today in Ubuntu 
> > 18.04.5 x64 works perfectly.
> > 
> > If your question is if the error messages that popup when using  your 
> > builds only show up on Ubuntu, then I can not answer. I don't use other 
> > distros.
> > 
> > Regards,
> > Pedro
> > 
> > 
> >>> On Oct 21, 2020, at 9:41 AM, Pedro Lino  wrote:
> >>> 
> >>> Hi Jim
> >>> 
> >>> I'm afraid not...
> >>> 
> >>> FYI I just finished compiling under Ubuntu 18.04.5 x64 using
> >>> 
> >>> ./configure --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname 
> >>> -sm`" 
> >>> --with-dmake-url=https://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
> >>>  --enable-opengl --disable-odk --enable-category-b 
> >>> --enable-bundled-dictionaries
> >>> 
> >>> and everything works as expected with no error messages.
> >>> 
> >>> Regards,
> >>> Pedro
> >>> 
>  On 10/21/2020 1:28 PM Jim Jagielski  wrote:
>  
>  
>  Here is hoping 4th time is the charm...
>  
>    http://home.apache.org/~jim/AOO-builds/
>  
>  -
>  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 
> > 


-- 
Rory O'Farrell 

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

Re: AOO418-RC2: General Error on opening files on Ubuntu

Hi Jim,

Am 21.10.20 um 16:39 schrieb Jim Jagielski:
> As I've said, the build system has not changed a whit between 4.1.7 and now, 
> so there is something with the various changes causing these issues. One way 
> of tracking this down is finding out when the last version of 4.1.8-dev 
> worked. The problem is that as long as the builds I provide crash, then we 
> cannot release the Linux 32/64 bit community builds, at least not without 
> changing the build system, which is something we should NOT do between patch 
> versions.
Understood!
>
> I may have to start playing around w/ git bisect or, at least, rebuild 4.1.7 
> and ensure that something didn't sneak into the build environ.

I am pretty sure that the last version you built before RC1/RC2 didn't
have that problem.
But I am not sure when that was (August?)

Matthias

>
>> On Oct 21, 2020, at 10:01 AM, Pedro Lino  
>> wrote:
>>
>> Hi again
>>
>>> On 10/21/2020 2:51 PM Jim Jagielski >> > wrote:
>>>
>>>
>>> Is it just ubuntu we are having these issues with? What was the last 
>>> 4.1.8-dev version that worked OK?
>> In case my message was not clear: the build I compiled today in Ubuntu 
>> 18.04.5 x64 works perfectly.
>>
>> If your question is if the error messages that popup when using  your builds 
>> only show up on Ubuntu, then I can not answer. I don't use other distros.
>>
>> Regards,
>> Pedro
>>
>>
 On Oct 21, 2020, at 9:41 AM, Pedro Lino  wrote:

 Hi Jim

 I'm afraid not...

 FYI I just finished compiling under Ubuntu 18.04.5 x64 using

 ./configure --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" 
 --with-dmake-url=https://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
  --enable-opengl --disable-odk --enable-category-b 
 --enable-bundled-dictionaries

 and everything works as expected with no error messages.

 Regards,
 Pedro

> On 10/21/2020 1:28 PM Jim Jagielski  wrote:
>
>
> Here is hoping 4th time is the charm...
>
>   http://home.apache.org/~jim/AOO-builds/
>
> -
> 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 
>> 



smime.p7s
Description: S/MIME Cryptographic Signature

Re: AOO418-RC2: General Error on opening files on Ubuntu

Let me double check.. I am rebuilding AOO417. Lets see if that works.

PS: The one change that DID happen is that I upgraded Vmware Fusion, which I 
use to run the CentOS5 VMs. That should NOT make any difference. But we will 
see.

I'll posted when my 4.1.7 test builds are ready. TIA!
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Test to Apache_OpenOffice_4.1.8_Linux_x86-64_install-deb_en-US-v2

2020-10-21 Thread Bidouille

> When I open a odt document made by a current version of LibreOffice,
> for example, 7.0.2, swriter say:
> 
> "This document was created by a newer version of OpenOffice. It may
> contain features not supported by your current version.

LibO seems to use ODF 1.3 

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

Re: AOO418-RC2: General Error on opening files on Ubuntu

Hi Jim,

Am 21.10.20 um 16:54 schrieb Jim Jagielski:
> Let me double check.. I am rebuilding AOO417. Lets see if that works.
>
> PS: The one change that DID happen is that I upgraded Vmware Fusion, which I 
> use to run the CentOS5 VMs. That should NOT make any difference. But we will 
> see.
>
> I'll posted when my 4.1.7 test builds are ready. TIA!

To be clear, the last version that worked for me was 4.1.8.
But it was before we built Release Candidates.

Unfortunately, I didn't keep it, but maybe you can upload it again?

> -
> 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: AOO418-RC2: General Error on opening files on Ubuntu

2020-10-21 Thread Dave Fisher

Well should it turn out to be a build issue then maybe we should rename 4.2 
branch as 4.3 and change 4.1.8 into 4.2.0.

Best Regards,
Dave

Sent from my iPhone

> On Oct 21, 2020, at 7:50 AM, Jim Jagielski  wrote:
> 
> As I've said, the build system has not changed a whit between 4.1.7 and now, 
> so there is something with the various changes causing these issues. One way 
> of tracking this down is finding out when the last version of 4.1.8-dev 
> worked. The problem is that as long as the builds I provide crash, then we 
> cannot release the Linux 32/64 bit community builds, at least not without 
> changing the build system, which is something we should NOT do between patch 
> versions.
> 
> I may have to start playing around w/ git bisect or, at least, rebuild 4.1.7 
> and ensure that something didn't sneak into the build environ.
> 
>> On Oct 21, 2020, at 10:01 AM, Pedro Lino  
>> wrote:
>> 
>> Hi again
>> 
 On 10/21/2020 2:51 PM Jim Jagielski >>> > wrote:
>>> 
>>> 
>>> Is it just ubuntu we are having these issues with? What was the last 
>>> 4.1.8-dev version that worked OK?
>> 
>> In case my message was not clear: the build I compiled today in Ubuntu 
>> 18.04.5 x64 works perfectly.
>> 
>> If your question is if the error messages that popup when using  your builds 
>> only show up on Ubuntu, then I can not answer. I don't use other distros.
>> 
>> Regards,
>> Pedro
>> 
>> 
 On Oct 21, 2020, at 9:41 AM, Pedro Lino  wrote:
 
 Hi Jim
 
 I'm afraid not...
 
 FYI I just finished compiling under Ubuntu 18.04.5 x64 using
 
 ./configure --with-build-version="$(date +"%Y-%m-%d %H:%M") - `uname -sm`" 
 --with-dmake-url=https://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
  --enable-opengl --disable-odk --enable-category-b 
 --enable-bundled-dictionaries
 
 and everything works as expected with no error messages.
 
 Regards,
 Pedro
 
> On 10/21/2020 1:28 PM Jim Jagielski  wrote:
> 
> 
> Here is hoping 4th time is the charm...
> 
>  http://home.apache.org/~jim/AOO-builds/
> 
> -
> 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 
>> 


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

Re: AOO418-RC2: General Error on opening files on Ubuntu

I don't have it, but that was around the end of Aug right? So right around the 
time when a bunch of stuff was included like updates to nss, libxslt, libxml2...

I'm trying to get my head around the logic of


https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09

> On Oct 21, 2020, at 10:58 AM, Matthias Seidel  
> wrote:
> 
> Hi Jim,
> 
> Am 21.10.20 um 16:54 schrieb Jim Jagielski:
>> Let me double check.. I am rebuilding AOO417. Lets see if that works.
>> 
>> PS: The one change that DID happen is that I upgraded Vmware Fusion, which I 
>> use to run the CentOS5 VMs. That should NOT make any difference. But we will 
>> see.
>> 
>> I'll posted when my 4.1.7 test builds are ready. TIA!
> 
> To be clear, the last version that worked for me was 4.1.8.
> But it was before we built Release Candidates.
> 
> Unfortunately, I didn't keep it, but maybe you can upload it again?
> 
>> -
>> 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: AOO418-RC2: General Error on opening files on Ubuntu

Should that fix be just:



> On Oct 21, 2020, at 11:37 AM, Jim Jagielski  wrote:
> 
> I don't have it, but that was around the end of Aug right? So right around 
> the time when a bunch of stuff was included like updates to nss, libxslt, 
> libxml2...
> 
> I'm trying to get my head around the logic of
> 
>
> https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09
> 
>> On Oct 21, 2020, at 10:58 AM, Matthias Seidel  
>> wrote:
>> 
>> Hi Jim,
>> 
>> Am 21.10.20 um 16:54 schrieb Jim Jagielski:
>>> Let me double check.. I am rebuilding AOO417. Lets see if that works.
>>> 
>>> PS: The one change that DID happen is that I upgraded Vmware Fusion, which 
>>> I use to run the CentOS5 VMs. That should NOT make any difference. But we 
>>> will see.
>>> 
>>> I'll posted when my 4.1.7 test builds are ready. TIA!
>> 
>> To be clear, the last version that worked for me was 4.1.8.
>> But it was before we built Release Candidates.
>> 
>> Unfortunately, I didn't keep it, but maybe you can upload it again?
>> 
>>> -
>>> 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: AOO418-RC2: General Error on opening files on Ubuntu

I am trying to build from a git co 99ef902016. If that works, then I'll start a 
git bisect from there.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: AOO418-RC2: General Error on opening files on Ubuntu

Am 21.10.20 um 17:43 schrieb Jim Jagielski:
> Should that fix be just:
>
> 

https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09

Really looks like a candidate...

>
>> On Oct 21, 2020, at 11:37 AM, Jim Jagielski  wrote:
>>
>> I don't have it, but that was around the end of Aug right? So right around 
>> the time when a bunch of stuff was included like updates to nss, libxslt, 
>> libxml2...
>>
>> I'm trying to get my head around the logic of
>>
>>
>> https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09
>>
>>> On Oct 21, 2020, at 10:58 AM, Matthias Seidel  
>>> wrote:
>>>
>>> Hi Jim,
>>>
>>> Am 21.10.20 um 16:54 schrieb Jim Jagielski:
 Let me double check.. I am rebuilding AOO417. Lets see if that works.

 PS: The one change that DID happen is that I upgraded Vmware Fusion, which 
 I use to run the CentOS5 VMs. That should NOT make any difference. But we 
 will see.

 I'll posted when my 4.1.7 test builds are ready. TIA!
>>> To be clear, the last version that worked for me was 4.1.8.
>>> But it was before we built Release Candidates.
>>>
>>> Unfortunately, I didn't keep it, but maybe you can upload it again?
>>>
 -
 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
>>
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: AOO418-RC2: General Error on opening files on Ubuntu

Agreed. That's why I mentioned it :-)

> On Oct 21, 2020, at 12:22 PM, Matthias Seidel  
> wrote:
> 
> Am 21.10.20 um 17:43 schrieb Jim Jagielski:
>> Should that fix be just:
>> 
>>
> 
> https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09
> 
> Really looks like a candidate...
> 
>> 
>>> On Oct 21, 2020, at 11:37 AM, Jim Jagielski  wrote:
>>> 
>>> I don't have it, but that was around the end of Aug right? So right around 
>>> the time when a bunch of stuff was included like updates to nss, libxslt, 
>>> libxml2...
>>> 
>>> I'm trying to get my head around the logic of
>>> 
>>>   
>>> https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09
>>> 
 On Oct 21, 2020, at 10:58 AM, Matthias Seidel  
 wrote:
 
 Hi Jim,
 
 Am 21.10.20 um 16:54 schrieb Jim Jagielski:
> Let me double check.. I am rebuilding AOO417. Lets see if that works.
> 
> PS: The one change that DID happen is that I upgraded Vmware Fusion, 
> which I use to run the CentOS5 VMs. That should NOT make any difference. 
> But we will see.
> 
> I'll posted when my 4.1.7 test builds are ready. TIA!
 To be clear, the last version that worked for me was 4.1.8.
 But it was before we built Release Candidates.
 
 Unfortunately, I didn't keep it, but maybe you can upload it again?
 
> -
> 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: AOO418-RC2: General Error on opening files on Ubuntu

On 21 Oct, Jim Jagielski wrote:
> I don't have it, but that was around the end of Aug right? So right around 
> the time when a bunch of stuff was included like updates to nss, libxslt, 
> libxml2...
> 
> I'm trying to get my head around the logic of
> 
> 
> https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09

If $shift is blank then "$shift>0" becomes ">0", which is a malformed
expression.  For some reason, it still works correctly in most cases.
The case where it does not is with the latest libxslt when built on
CentOS 5.  In that cause, when we use the newly built xsltproc to
generate headers, one of them is corrupted and results in a build
failure when we try to compile with that header.  Adding the length
check avoids evaluating "$shift>0" when $shift is blank

This problem is only a build failure.

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

Re: AOO418-RC2: General Error on opening files on Ubuntu

On 21 Oct, Jim Jagielski wrote:
> Should that fix be just:
> 
> 

That would work, but it would produce a different output.  It would
always put ">> $shift" in the output whenever $shift is nonblank.  The
change that I committed only puts ">> $shift" in the output if $shift is
nonblank and greater than zero.  This is what the original version does
with older versions of libxslt, or when building on anything newer than
CentOS 5.

> 
>> On Oct 21, 2020, at 11:37 AM, Jim Jagielski  wrote:
>> 
>> I don't have it, but that was around the end of Aug right? So right around 
>> the time when a bunch of stuff was included like updates to nss, libxslt, 
>> libxml2...
>> 
>> I'm trying to get my head around the logic of
>> 
>>
>> https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09
>> 
>>> On Oct 21, 2020, at 10:58 AM, Matthias Seidel  
>>> wrote:
>>> 
>>> Hi Jim,
>>> 
>>> Am 21.10.20 um 16:54 schrieb Jim Jagielski:
 Let me double check.. I am rebuilding AOO417. Lets see if that works.
 
 PS: The one change that DID happen is that I upgraded Vmware Fusion, which 
 I use to run the CentOS5 VMs. That should NOT make any difference. But we 
 will see.
 
 I'll posted when my 4.1.7 test builds are ready. TIA!
>>> 
>>> To be clear, the last version that worked for me was 4.1.8.
>>> But it was before we built Release Candidates.
>>> 
>>> Unfortunately, I didn't keep it, but maybe you can upload it again?
>>> 
 -
 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: AOO418-RC2: General Error on opening files on Ubuntu

so are YOU able to build HEAD of AOO418 on CentOS5 ??


> On Oct 21, 2020, at 2:09 PM, Don Lewis  wrote:
> 
> On 21 Oct, Jim Jagielski wrote:
>> I don't have it, but that was around the end of Aug right? So right around 
>> the time when a bunch of stuff was included like updates to nss, libxslt, 
>> libxml2...
>> 
>> I'm trying to get my head around the logic of
>> 
>>
>> https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09
> 
> If $shift is blank then "$shift>0" becomes ">0", which is a malformed
> expression.  For some reason, it still works correctly in most cases.
> The case where it does not is with the latest libxslt when built on
> CentOS 5.  In that cause, when we use the newly built xsltproc to
> generate headers, one of them is corrupted and results in a build
> failure when we try to compile with that header.  Adding the length
> check avoids evaluating "$shift>0" when $shift is blank
> 
> This problem is only a build failure.
> 
> 
> 
> -
> 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: AOO418-RC2: General Error on opening files on Ubuntu

OK... so $shift is a number then, or should be? But sometimes $shift is simply 
blank. And we want a black $shift to be evaluated as 0. So if all that is 
correct, could we use number($shift)>0 ?

I'm thinking this isn't the problem though with the failures :/


> On Oct 21, 2020, at 2:15 PM, Don Lewis  wrote:
> 
> On 21 Oct, Jim Jagielski wrote:
>> Should that fix be just:
>> 
>>
> 
> That would work, but it would produce a different output.  It would
> always put ">> $shift" in the output whenever $shift is nonblank.  The
> change that I committed only puts ">> $shift" in the output if $shift is
> nonblank and greater than zero.  This is what the original version does
> with older versions of libxslt, or when building on anything newer than
> CentOS 5.
> 
>> 
>>> On Oct 21, 2020, at 11:37 AM, Jim Jagielski  wrote:
>>> 
>>> I don't have it, but that was around the end of Aug right? So right around 
>>> the time when a bunch of stuff was included like updates to nss, libxslt, 
>>> libxml2...
>>> 
>>> I'm trying to get my head around the logic of
>>> 
>>>   
>>> https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09
>>> 
 On Oct 21, 2020, at 10:58 AM, Matthias Seidel  
 wrote:
 
 Hi Jim,
 
 Am 21.10.20 um 16:54 schrieb Jim Jagielski:
> Let me double check.. I am rebuilding AOO417. Lets see if that works.
> 
> PS: The one change that DID happen is that I upgraded Vmware Fusion, 
> which I use to run the CentOS5 VMs. That should NOT make any difference. 
> But we will see.
> 
> I'll posted when my 4.1.7 test builds are ready. TIA!
 
 To be clear, the last version that worked for me was 4.1.8.
 But it was before we built Release Candidates.
 
 Unfortunately, I didn't keep it, but maybe you can upload it again?
 
> -
> 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: AOO418-RC2: General Error on opening files on Ubuntu

never mind this... it's not a matter of building. I can build fine. It just 
crashes on Ubuntu. no idea why.

> On Oct 21, 2020, at 2:16 PM, Jim Jagielski  wrote:
> 
> so are YOU able to build HEAD of AOO418 on CentOS5 ??
> 
> 
>> On Oct 21, 2020, at 2:09 PM, Don Lewis  wrote:
>> 
>> On 21 Oct, Jim Jagielski wrote:
>>> I don't have it, but that was around the end of Aug right? So right around 
>>> the time when a bunch of stuff was included like updates to nss, libxslt, 
>>> libxml2...
>>> 
>>> I'm trying to get my head around the logic of
>>> 
>>>   
>>> https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09
>> 
>> If $shift is blank then "$shift>0" becomes ">0", which is a malformed
>> expression.  For some reason, it still works correctly in most cases.
>> The case where it does not is with the latest libxslt when built on
>> CentOS 5.  In that cause, when we use the newly built xsltproc to
>> generate headers, one of them is corrupted and results in a build
>> failure when we try to compile with that header.  Adding the length
>> check avoids evaluating "$shift>0" when $shift is blank
>> 
>> This problem is only a build failure.
>> 
>> 
>> 
>> -
>> 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: AOO418-RC2: General Error on opening files on Ubuntu

On 21 Oct, Matthias Seidel wrote:
> Am 21.10.20 um 17:43 schrieb Jim Jagielski:
>> Should that fix be just:
>>
>> 
> 
> https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09
> 
> Really looks like a candidate...

I doubt it. Unless you are building on CentOS 5,
writerfilter/.../inc/doctok/resources.hxx is identical with or without this
commit.  On CentOS 5, resources.hxx differs, and causes a compile error
because it contains the correct C expression "something >> ".

I didn't commit this change to trunk or AOO42X because the problem only
shows up when building on CentOS 5.

Also, I believe that we've seen this problem previously on trunk and/or
AOO42X that does not have this commit but the problem has mysteriously
gone away, and it seems to be related to the combination of what OS the
build was done on and what OS the resulting binaries are run on.

I've done testing on CentOS 5, CentOS 7, Debian stretch and a bit of
testing on Ubuntu and have never run into this problem, *but* I've
always run the binaries on the same OS where they were compiled.

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

Re: AOO418-RC2: General Error on opening files on Ubuntu

On 21 Oct, Jim Jagielski wrote:
> so are YOU able to build HEAD of AOO418 on CentOS5 ??

I haven't tried to build today's HEAD, but I've built and tested all of
my AOO418 commits on CentOS 5 before I made the commits.


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

Re: AOO418-RC2: General Error on opening files on Ubuntu

On 21 Oct, Jim Jagielski wrote:
> OK... so $shift is a number then, or should be? But sometimes $shift
> is simply blank. And we want a black $shift to be evaluated as 0. So
> if all that is correct, could we use number($shift)>0 ?

The input file that generates the header doesn't specifiy $shift in
all cases, so I assume that $shift is treated as an empty string.

Something I thought would work was test="$shift" since either an empty
string or a zero in a boolean context should evaluate to false, but for
some reason it did not work.

I didn't stumble across number() in my reading.  I don't know what
number() would do in this situation.
  
> I'm thinking this isn't the problem though with the failures :/

Yeah, I think it's probably something else that went in at the same time,
and I think also that build OS vs. deployment OS is part of the mix.
 
>> On Oct 21, 2020, at 2:15 PM, Don Lewis  wrote:
>> 
>> On 21 Oct, Jim Jagielski wrote:
>>> Should that fix be just:
>>> 
>>>
>> 
>> That would work, but it would produce a different output.  It would
>> always put ">> $shift" in the output whenever $shift is nonblank. 
>> The change that I committed only puts ">> $shift" in the output if
>> $shift is nonblank and greater than zero.  This is what the original
>> version does with older versions of libxslt, or when building on
>> anything newer than CentOS 5.
>> 
>>> 
 On Oct 21, 2020, at 11:37 AM, Jim Jagielski  wrote:
 
 I don't have it, but that was around the end of Aug right? So right
 around the time when a bunch of stuff was included like updates to
 nss, libxslt, libxml2...
 
 I'm trying to get my head around the logic of
 
   
 https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09
 
> On Oct 21, 2020, at 10:58 AM, Matthias Seidel
>  wrote:
> 
> Hi Jim,
> 
> Am 21.10.20 um 16:54 schrieb Jim Jagielski:
>> Let me double check.. I am rebuilding AOO417. Lets see if that
>> works.
>> 
>> PS: The one change that DID happen is that I upgraded Vmware
>> Fusion, which I use to run the CentOS5 VMs. That should NOT make
>> any difference. But we will see.
>> 
>> I'll posted when my 4.1.7 test builds are ready. TIA!
> 
> To be clear, the last version that worked for me was 4.1.8.
> But it was before we built Release Candidates.
> 
> Unfortunately, I didn't keep it, but maybe you can upload it again?
> 
>> -
>> 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
>> 


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

Re: AOO418-RC2: General Error on opening files on Ubuntu

On 21 Oct, Jim Jagielski wrote:
> never mind this... it's not a matter of building. I can build fine. It
> just crashes on Ubuntu. no idea why.

Are you building on the same version of Ubuntu?


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

Re: AOO418-RC2: General Error on opening files on Ubuntu

No. I am building on CentOS5. I am building on the exact setup I've used to 
build the community builds for 4.1.x.

Something happened within the last month or so such that my builds crash on 
Ubuntu. So basically, we cannot create community builds for Linux until we know 
what broke.

> On Oct 21, 2020, at 2:43 PM, Don Lewis  wrote:
> 
> On 21 Oct, Jim Jagielski wrote:
>> never mind this... it's not a matter of building. I can build fine. It
>> just crashes on Ubuntu. no idea why.
> 
> Are you building on the same version of Ubuntu?
> 
> 
> -
> 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: AOO418-RC2: General Error on opening files on Ubuntu

In the meantime, please review main/writerfilter/source/doctok/resources.xsl on 
trunk and AOO42X

> On Oct 21, 2020, at 2:41 PM, Don Lewis  wrote:
> 
> On 21 Oct, Jim Jagielski wrote:
>> OK... so $shift is a number then, or should be? But sometimes $shift
>> is simply blank. And we want a black $shift to be evaluated as 0. So
>> if all that is correct, could we use number($shift)>0 ?
> 
> The input file that generates the header doesn't specifiy $shift in
> all cases, so I assume that $shift is treated as an empty string.
> 
> Something I thought would work was test="$shift" since either an empty
> string or a zero in a boolean context should evaluate to false, but for
> some reason it did not work.
> 
> I didn't stumble across number() in my reading.  I don't know what
> number() would do in this situation.
> 
>> I'm thinking this isn't the problem though with the failures :/
> 
> Yeah, I think it's probably something else that went in at the same time,
> and I think also that build OS vs. deployment OS is part of the mix.
> 
>>> On Oct 21, 2020, at 2:15 PM, Don Lewis  wrote:
>>> 
>>> On 21 Oct, Jim Jagielski wrote:
 Should that fix be just:
 
   
>>> 
>>> That would work, but it would produce a different output.  It would
>>> always put ">> $shift" in the output whenever $shift is nonblank. 
>>> The change that I committed only puts ">> $shift" in the output if
>>> $shift is nonblank and greater than zero.  This is what the original
>>> version does with older versions of libxslt, or when building on
>>> anything newer than CentOS 5.
>>> 
 
> On Oct 21, 2020, at 11:37 AM, Jim Jagielski  wrote:
> 
> I don't have it, but that was around the end of Aug right? So right
> around the time when a bunch of stuff was included like updates to
> nss, libxslt, libxml2...
> 
> I'm trying to get my head around the logic of
> 
>  
> https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09
> 
>> On Oct 21, 2020, at 10:58 AM, Matthias Seidel
>>  wrote:
>> 
>> Hi Jim,
>> 
>> Am 21.10.20 um 16:54 schrieb Jim Jagielski:
>>> Let me double check.. I am rebuilding AOO417. Lets see if that
>>> works.
>>> 
>>> PS: The one change that DID happen is that I upgraded Vmware
>>> Fusion, which I use to run the CentOS5 VMs. That should NOT make
>>> any difference. But we will see.
>>> 
>>> I'll posted when my 4.1.7 test builds are ready. TIA!
>> 
>> To be clear, the last version that worked for me was 4.1.8.
>> But it was before we built Release Candidates.
>> 
>> Unfortunately, I didn't keep it, but maybe you can upload it again?
>> 
>>> -
>>> 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
>>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
> 
> For additional commands, e-mail: dev-h...@openoffice.apache.org 
>

Re: Google Analytics and Download Count

2020-10-21 Thread Peter Kovacs




Am 19.10.20 um 23:48 schrieb Marcus:

Am 19.10.20 um 23:15 schrieb Dave Fisher:

On Oct 19, 2020, at 2:06 PM, Peter Kovacs  wrote:

I am not sure what you mean.


I am for eliminating all both google analytics and entourage js from 
our pages as we move.


when we don't use the statistcs data and therefore don't need this, 
then - for sure - let's get rid of it.


I am against eliminating the Statistics without replacement. I think 
that we can replace google Analytics.


However I would like to be involved in a migration to another system. I 
am sure Matthias wants to be involved to.


Am 19.10.20 um 23:15 schrieb Dave Fisher:


We can make a special web request and get a filtered apache access log from 
Infra.

We could maybe feed AWStat with it.

https://awstats.sourceforge.io/

I would like to try the software out and if we are satisfied with it we 
can remove the analytics.


Would that be fine for everyone?


If it is about using the data I can make a community Report on our 
Statistics. Maybe Matthias could add his update staistics.


And then we could release it on our blog page?


All the Best

Peter


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

Re: AOO418-RC2: General Error on opening files on Ubuntu

2020-10-21 Thread Andrea Pescetti


Don Lewis wrote:

On 21 Oct, Jim Jagielski wrote:

so are YOU able to build HEAD of AOO418 on CentOS5 ??


I haven't tried to build today's HEAD, but I've built and tested all of
my AOO418 commits on CentOS 5 before I made the commits.


It looks like we are getting closer I mean, we have a commit that is 
only relevant to CentOS 5 and we know that Jim's builds are done on 
CentOS 5 and have the bug, while the others (mine on CentOS 7; Pedro's 
on Ubuntu 18) do not have it.


Possibly some build error that goes unnoticed due to a "dirty" build? 
Otherwise I can't explain why Don's CentOS 5 tests passed...


I don't have a CentOS 5 VM ready, but I can surely setup one this 
weekend if it's useful to have more CentOS 5 VMs, or simply a double-check.


Regards,
  Andrea.

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

Re: AOO418-RC2: General Error on opening files on Ubuntu

I have uploaded builds of AOO-4.1.7 from my CentOS5 build VM. If these break, 
then we know it's something on my build platform. If not, then we know it's 
code related.

 http://home.apache.org/~jim/AOO-builds/ 


Thx!

Re: AOO418-RC2: General Error on opening files on Ubuntu




> On Oct 21, 2020, at 4:21 PM, Andrea Pescetti  wrote:
> 
> It looks like we are getting closer I mean, we have a commit that is only 
> relevant to CentOS 5 and we know that Jim's builds are done on CentOS 5 and 
> have the bug, while the others (mine on CentOS 7; Pedro's on Ubuntu 18) do 
> not have it.
> 
> Possibly some build error that goes unnoticed due to a "dirty" build? 
> Otherwise I can't explain why Don's CentOS 5 tests passed...
> 

I don't think anyone else tested Don's CentOS5 built builds... just himself. I 
think.


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

Re: Google Analytics and Download Count

2020-10-21 Thread Andrea Pescetti


On 20/10/2020 Matthias Seidel wrote:

It seems that I am the only one interested in the data Google Analytics
provides.


I'm interested in keeping Google Analytics too.

We have years of historic data there and they are useful right now, 
since we'll want to ensure that the top 30 pages are still perfectly 
working if we change the web infrastructure. Also, Google Analytics data 
will help if we ever decide to restructure the site (dropping the 
majority of pages and keeping only pages that receive traffic). And if 
we interrupt data collection now there is no way back.


AWStats is not a feature-complete replacement by any means and it also 
places additional requirements on the server. I understand that it is 
better from a philosophical/ideological perspective (open source, self 
hosted). We can try and add it - we can have both AWStats and Google 
Analytics working at the same time and then judge which one is better 
after some months.


Google Analytics is an industry standard; if we configure it in a way 
that honors do-not-track requirements and does not store irrelevant data 
about users I believe it is acceptable. We've already applied a 
reasonable trade-off in the past to ensure Google Analytics does not 
become too invasive.


Regards,
  Andrea.

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

Possible error in File https://www.openoffice.org/sc/excelfileformat.pdf (was: How to go about confirming a possible bug and contributing updates to a document )

2020-10-21 Thread Peter Kovacs

Hello Jay,

Am 21.10.20 um 16:49 schrieb Jay Wren (jawren):

Hello,

I hope this message finds you well.

First, I want to thank you for
https://www.openoffice.org/sc/excelfileformat.pdf I have found it invaluable.
Thank you.
You are welcome. It is good to know that people take interest in our
pages. :)

I wanted to ask about a possible bug or submitting a patch to this document. I
think I may have found an error in the size table in section 3.4.7.
Specifically, tFunc and tFuncVar on page 43. The BIFF8 size is listed at 4 and
5 respectively. However, in section 3.7.1 and 3.7.2 only 3 bytes and 4 bytes
respectively are documented. Indeed in practice as I write a parser, I can only
read 4 bytes and not 5 for tFuncVar.

I am not sure if we have a editable Document somewhere. I switch from
recruitment to dev List. Maybe someone knows if we have an better editor
able file that we can provide you for a fix..

I am not sure, but our code reads 4 Tokes Int16. I do not see a fifth.
So this sounds according to your observation.

http://opengrok.openoffice.org/xref/trunk/main/oox/source/xls/formulaparser.cxx?r=a893be29#importFuncVarToken4

I am not sure if Apache POI has also some input on this? I am a bit
unfamiliar with their Project.

*Dave*

you have some idea how to quickly search the POI Code?

If I missed something, I’d love to be corrected. If I did not, I’d love to
contribute if you suggest.

Contribution are all welcome. I think it is best to create a ticket in
Bugzilla, upload your patch there. And bring then the case to an
attention on the dev list, by answering to this thread with the ticket.

Just for better awarness. :)

all the best

Peter

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

Re: Google Analytics and Download Count

2020-10-21 Thread Peter Kovacs




Am 21.10.20 um 22:51 schrieb Andrea Pescetti:

On 20/10/2020 Matthias Seidel wrote:

It seems that I am the only one interested in the data Google Analytics
provides.


I'm interested in keeping Google Analytics too.
If you provide a google address to me or Matthias we can add you to the 
analytics.


We have years of historic data there and they are useful right now, 
since we'll want to ensure that the top 30 pages are still perfectly 
working if we change the web infrastructure. Also, Google Analytics 
data will help if we ever decide to restructure the site (dropping the 
majority of pages and keeping only pages that receive traffic). And if 
we interrupt data collection now there is no way back.
We have dropped the time the data is kept to a minimum. I do not see one 
reason we need a long standing history. And the minimum is at 1 year I 
think. For me that is sufficient.


AWStats is not a feature-complete replacement by any means and it also 
places additional requirements on the server. I understand that it is 
better from a philosophical/ideological perspective (open source, self 
hosted). We can try and add it - we can have both AWStats and Google 
Analytics working at the same time and then judge which one is better 
after some months.

+1, my expectation is that we can live with the loss.


Google Analytics is an industry standard; if we configure it in a way 
that honors do-not-track requirements and does not store irrelevant 
data about users I believe it is acceptable. We've already applied a 
reasonable trade-off in the past to ensure Google Analytics does not 
become too invasive.
I am careful because on the members or board list it cause a lot of 
uproar. And I do not have much interest in getting some general shit 
storm, because people have no clue what they talking about.



All the best

Peter


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

Re: AOO418-RC2: General Error on opening files on Ubuntu

2020-10-21 Thread Pedro Lino

Hi Jim

> I have uploaded builds of AOO-4.1.7 from my CentOS5 build VM. If these break, 
> then we know it's something on my build platform. If not, then we know it's 
> code related.

These builds do not throw errors but I am on my home laptop now (still Ubuntu 
18.04.5 x64).
Do you have the 4.1.8 RC3 builds from this morning just to make sure?

Thanks!

Pedro

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

Re: AOO418-RC2: General Error on opening files on Ubuntu

On 21 Oct, Jim Jagielski wrote:
> 
> 
>> On Oct 21, 2020, at 4:21 PM, Andrea Pescetti 
>> wrote:
>> 
>> It looks like we are getting closer I mean, we have a commit that
>> is only relevant to CentOS 5 and we know that Jim's builds are done
>> on CentOS 5 and have the bug, while the others (mine on CentOS 7;
>> Pedro's on Ubuntu 18) do not have it.
>> 
>> Possibly some build error that goes unnoticed due to a "dirty" build?
>> Otherwise I can't explain why Don's CentOS 5 tests passed...
>> 
> 
> I don't think anyone else tested Don's CentOS5 built builds... just
> himself. I think.

I only tested my CentOS 5 build on CentOS 5.  I think the problem only
occurs when running a CentOS 5 build on something newer (Ubuntu only?).
This sort of smells like a system library incompatability of some sort.
Things work when the build is done using the system headers that match
the destination environment, but the problem crops up if the build is
done with the CentOS 5 headers but the runtime libraries are from a
newer distro. The mystery is what changed between 4.1.7 and now to
trigger the problem.

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

Re: AOO418-RC2: General Error on opening files on Ubuntu

Hi Jim,

Am 21.10.20 um 22:38 schrieb Jim Jagielski:
> I have uploaded builds of AOO-4.1.7 from my CentOS5 build VM. If these break, 
> then we know it's something on my build platform. If not, then we know it's 
> code related.
>
>  http://home.apache.org/~jim/AOO-builds/ 
> 
Opens ODT and ODS without Error messages on Ubuntu 16.04.
>
> Thx!



smime.p7s
Description: S/MIME Cryptographic Signature

Re: AOO418-RC2: General Error on opening files on Ubuntu

I don't, unfortunately... maybe others can test and double check that the 4.1.7 
works OK.

> On Oct 21, 2020, at 5:09 PM, Pedro Lino  
> wrote:
> 
> Hi Jim
> 
>> I have uploaded builds of AOO-4.1.7 from my CentOS5 build VM. If these 
>> break, then we know it's something on my build platform. If not, then we 
>> know it's code related.
> 
> These builds do not throw errors but I am on my home laptop now (still Ubuntu 
> 18.04.5 x64).
> Do you have the 4.1.8 RC3 builds from this morning just to make sure?
> 
> Thanks!
> 
> Pedro
> 
> -
> 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: AOO418-RC2: General Error on opening files on Ubuntu

Hi Jim,

Am 21.10.20 um 20:48 schrieb Jim Jagielski:
> In the meantime, please review main/writerfilter/source/doctok/resources.xsl 
> on trunk and AOO42X

Windows Buildbot (AOO42X) just stopped with this error:

1 module(s): writerfilter need(s) to be rebuilt Reason(s): ERROR: error
65280 occurred while making
/cygdrive/e/slave14/openoffice-win7-41x/build/main/writerfilter/prj When
you have fixed the errors in that module you can resume the build by
running: build --from writerfilter

>
>> On Oct 21, 2020, at 2:41 PM, Don Lewis  wrote:
>>
>> On 21 Oct, Jim Jagielski wrote:
>>> OK... so $shift is a number then, or should be? But sometimes $shift
>>> is simply blank. And we want a black $shift to be evaluated as 0. So
>>> if all that is correct, could we use number($shift)>0 ?
>> The input file that generates the header doesn't specifiy $shift in
>> all cases, so I assume that $shift is treated as an empty string.
>>
>> Something I thought would work was test="$shift" since either an empty
>> string or a zero in a boolean context should evaluate to false, but for
>> some reason it did not work.
>>
>> I didn't stumble across number() in my reading.  I don't know what
>> number() would do in this situation.
>>
>>> I'm thinking this isn't the problem though with the failures :/
>> Yeah, I think it's probably something else that went in at the same time,
>> and I think also that build OS vs. deployment OS is part of the mix.
>>
 On Oct 21, 2020, at 2:15 PM, Don Lewis  wrote:

 On 21 Oct, Jim Jagielski wrote:
> Should that fix be just:
>
>   
 That would work, but it would produce a different output.  It would
 always put ">> $shift" in the output whenever $shift is nonblank. 
 The change that I committed only puts ">> $shift" in the output if
 $shift is nonblank and greater than zero.  This is what the original
 version does with older versions of libxslt, or when building on
 anything newer than CentOS 5.

>> On Oct 21, 2020, at 11:37 AM, Jim Jagielski  wrote:
>>
>> I don't have it, but that was around the end of Aug right? So right
>> around the time when a bunch of stuff was included like updates to
>> nss, libxslt, libxml2...
>>
>> I'm trying to get my head around the logic of
>>
>>  
>> https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09
>>
>>> On Oct 21, 2020, at 10:58 AM, Matthias Seidel
>>>  wrote:
>>>
>>> Hi Jim,
>>>
>>> Am 21.10.20 um 16:54 schrieb Jim Jagielski:
 Let me double check.. I am rebuilding AOO417. Lets see if that
 works.

 PS: The one change that DID happen is that I upgraded Vmware
 Fusion, which I use to run the CentOS5 VMs. That should NOT make
 any difference. But we will see.

 I'll posted when my 4.1.7 test builds are ready. TIA!
>>> To be clear, the last version that worked for me was 4.1.8.
>>> But it was before we built Release Candidates.
>>>
>>> Unfortunately, I didn't keep it, but maybe you can upload it again?
>>>
 -
 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
 
>>
>> -
>> 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: Test to Apache_OpenOffice_4.1.8_Linux_x86-64_install-deb_en-US-v2

2020-10-21 Thread Delio Orozco Gonzalez

Hello:

I think that is not the library becuase with AOO 4.1.7 there isn't error 
message.

I tested with "Apache_OpenOffice_4.1.8_Linux_x86-64_install-deb_en-US-v4" and 
is the same error message.

- Mensaje original -
De: "Bidouille" 
Para: "dev" 
Enviados: Miércoles, 21 de Octubre 2020 10:58:11
Asunto: Re: Test to Apache_OpenOffice_4.1.8_Linux_x86-64_install-deb_en-US-v2

> When I open a odt document made by a current version of LibreOffice,
> for example, 7.0.2, swriter say:
> 
> "This document was created by a newer version of OpenOffice. It may
> contain features not supported by your current version.

LibO seems to use ODF 1.3 

-
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: AOO418-RC2: General Error on opening files on Ubuntu

2020-10-21 Thread Carl Marcum


Hi Jim,

On 10/21/20 4:38 PM, Jim Jagielski wrote:

I have uploaded builds of AOO-4.1.7 from my CentOS5 build VM. If these break, 
then we know it's something on my build platform. If not, then we know it's 
code related.

  http://home.apache.org/~jim/AOO-builds/ 


Thx!
I installed this in an Ubuntu 18.04 VM and have no error messages 
opening files.


Thanks,
Carl

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

Re: Google Analytics and Download Count

2020-10-21 Thread Dave Fisher

Hi -

Sent from my iPhone

> On Oct 21, 2020, at 5:45 PM, Peter Kovacs  wrote:
> 
> 
>> Am 21.10.20 um 22:51 schrieb Andrea Pescetti:
>>> On 20/10/2020 Matthias Seidel wrote:
>>> It seems that I am the only one interested in the data Google Analytics
>>> provides.
>> 
>> I'm interested in keeping Google Analytics too.
> If you provide a google address to me or Matthias we can add you to the 
> analytics.
>> 
>> We have years of historic data there and they are useful right now, since 
>> we'll want to ensure that the top 30 pages are still perfectly working if we 
>> change the web infrastructure. Also, Google Analytics data will help if we 
>> ever decide to restructure the site (dropping the majority of pages and 
>> keeping only pages that receive traffic). And if we interrupt data 
>> collection now there is no way back.
> We have dropped the time the data is kept to a minimum. I do not see one 
> reason we need a long standing history. And the minimum is at 1 year I think. 
> For me that is sufficient.

There are a plethora of historical information. I’m planning to preserve as 
much as we can/want.

>> 
>> AWStats is not a feature-complete replacement by any means and it also 
>> places additional requirements on the server. I understand that it is better 
>> from a philosophical/ideological perspective (open source, self hosted). We 
>> can try and add it - we can have both AWStats and Google Analytics working 
>> at the same time and then judge which one is better after some months.
> +1, my expectation is that we can live with the loss.

I will be doing the initial migration as quickly as I can. I think that metrics 
needs a specific discussion.

Initially I’ll comment this out.

>> 
>> Google Analytics is an industry standard; if we configure it in a way that 
>> honors do-not-track requirements and does not store irrelevant data about 
>> users I believe it is acceptable. We've already applied a reasonable 
>> trade-off in the past to ensure Google Analytics does not become too 
>> invasive.
> I am careful because on the members or board list it cause a lot of uproar. 
> And I do not have much interest in getting some general shit storm, because 
> people have no clue what they talking about.

Privacy concerns in certain jurisdictions is the foundation issue.

We can certainly harvest web logs with Infrastructure help.

Regards,
Dave

> 
> 
> All the best
> 
> Peter
> 
> 
> -
> 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: AOO418-RC2: General Error on opening files on Ubuntu

2020-10-21 Thread Delio Orozco Gonzalez

Hello

In Debian 9 and Debian 10, I have error messages whit AOO 4.1.8 v4; 
nevertheless whit AOO 4.1.7 there aren't error messages.

Delio.

- Mensaje original -
De: "Carl Marcum" 
Para: "dev" 
Enviados: Miércoles, 21 de Octubre 2020 19:22:39
Asunto: Re: AOO418-RC2: General Error on opening files on Ubuntu

Hi Jim,

On 10/21/20 4:38 PM, Jim Jagielski wrote:
> I have uploaded builds of AOO-4.1.7 from my CentOS5 build VM. If these break, 
> then we know it's something on my build platform. If not, then we know it's 
> code related.
>
>   http://home.apache.org/~jim/AOO-builds/ 
> 
>
> Thx!
I installed this in an Ubuntu 18.04 VM and have no error messages 
opening files.

Thanks,
Carl

-
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: AOO418-RC2: General Error on opening files on Ubuntu

2020-10-21 Thread Delio Orozco Gonzalez

Sorry:

I mean "with" not "whit"

Delio.

- Mensaje original -
De: "Delio Orozco Gonzalez" 
Para: "dev" 
Enviados: Miércoles, 21 de Octubre 2020 23:57:30
Asunto: Re: AOO418-RC2: General Error on opening files on Ubuntu

Hello

In Debian 9 and Debian 10, I have error messages whit AOO 4.1.8 v4; 
nevertheless whit AOO 4.1.7 there aren't error messages.

Delio.

- Mensaje original -
De: "Carl Marcum" 
Para: "dev" 
Enviados: Miércoles, 21 de Octubre 2020 19:22:39
Asunto: Re: AOO418-RC2: General Error on opening files on Ubuntu

Hi Jim,

On 10/21/20 4:38 PM, Jim Jagielski wrote:
> I have uploaded builds of AOO-4.1.7 from my CentOS5 build VM. If these break, 
> then we know it's something on my build platform. If not, then we know it's 
> code related.
>
>   http://home.apache.org/~jim/AOO-builds/ 
> 
>
> Thx!
I installed this in an Ubuntu 18.04 VM and have no error messages 
opening files.

Thanks,
Carl

-
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: AOO418-RC2: General Error on opening files on Ubuntu

On 22 Oct, Matthias Seidel wrote:
> Hi Jim,
> 
> Am 21.10.20 um 20:48 schrieb Jim Jagielski:
>> In the meantime, please review main/writerfilter/source/doctok/resources.xsl 
>> on trunk and AOO42X
> 
> Windows Buildbot (AOO42X) just stopped with this error:
> 
> 1 module(s): writerfilter need(s) to be rebuilt Reason(s): ERROR: error
> 65280 occurred while making
> /cygdrive/e/slave14/openoffice-win7-41x/build/main/writerfilter/prj When
> you have fixed the errors in that module you can resume the build by
> running: build --from writerfilter

Sounds like
  test="string-length($shift)!=0"
doesn't work, which is odd ...

>>
>>> On Oct 21, 2020, at 2:41 PM, Don Lewis  wrote:
>>>
>>> On 21 Oct, Jim Jagielski wrote:
 OK... so $shift is a number then, or should be? But sometimes $shift
 is simply blank. And we want a black $shift to be evaluated as 0. So
 if all that is correct, could we use number($shift)>0 ?
>>> The input file that generates the header doesn't specifiy $shift in
>>> all cases, so I assume that $shift is treated as an empty string.
>>>
>>> Something I thought would work was test="$shift" since either an empty
>>> string or a zero in a boolean context should evaluate to false, but for
>>> some reason it did not work.
>>>
>>> I didn't stumble across number() in my reading.  I don't know what
>>> number() would do in this situation.
>>>
 I'm thinking this isn't the problem though with the failures :/
>>> Yeah, I think it's probably something else that went in at the same time,
>>> and I think also that build OS vs. deployment OS is part of the mix.
>>>
> On Oct 21, 2020, at 2:15 PM, Don Lewis  wrote:
>
> On 21 Oct, Jim Jagielski wrote:
>> Should that fix be just:
>>
>>   
> That would work, but it would produce a different output.  It would
> always put ">> $shift" in the output whenever $shift is nonblank. 
> The change that I committed only puts ">> $shift" in the output if
> $shift is nonblank and greater than zero.  This is what the original
> version does with older versions of libxslt, or when building on
> anything newer than CentOS 5.
>
>>> On Oct 21, 2020, at 11:37 AM, Jim Jagielski  wrote:
>>>
>>> I don't have it, but that was around the end of Aug right? So right
>>> around the time when a bunch of stuff was included like updates to
>>> nss, libxslt, libxml2...
>>>
>>> I'm trying to get my head around the logic of
>>>
>>>  
>>> https://github.com/apache/openoffice/commit/9510f3847723b65ae47efff8796e6f14f586ce09
>>>
 On Oct 21, 2020, at 10:58 AM, Matthias Seidel
  wrote:

 Hi Jim,

 Am 21.10.20 um 16:54 schrieb Jim Jagielski:
> Let me double check.. I am rebuilding AOO417. Lets see if that
> works.
>
> PS: The one change that DID happen is that I upgraded Vmware
> Fusion, which I use to run the CentOS5 VMs. That should NOT make
> any difference. But we will see.
>
> I'll posted when my 4.1.7 test builds are ready. TIA!
 To be clear, the last version that worked for me was 4.1.8.
 But it was before we built Release Candidates.

 Unfortunately, I didn't keep it, but maybe you can upload it again?

> -
> 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
> 
>>>
>>> -
>>> 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: AOO418-RC2: General Error on opening files on Ubuntu