gcc version problems on CentOS 7 using SDK tools from trunk daily built on Ubuntu buildbot

[Carl Marcum]

Hi All,

When I installed the 4.5.0 latest daily build for linux64 (September 
13th BTW separate thread about buildbots) on a CentOS 7 VM for running 
tests and I'm getting an error when compiling the standalone test suite.


The error happens when building the smoketestdoc TestExtension:
/opt/openoffice4/sdk/bin/idlc: /lib64/libstdc++.so.6: version 
`GLIBCXX_3.4.21' not found (required by /opt/openoffice4/sdk/bin/idlc)


I remember getting a similar error when trying to run a "installed" 
build from Arrigo on this VM.


This ant build uses the idlc from the installed AOO SDK.
It seems I require a libstdc++.so.6 with version GLIBCXX_3.4.21 maybe?

when I check this on CentOS 7
$ strings /lib64/libstdc++.so.6 | grep GLIBCXX

it only goes up to 3.4.19.

My CentOS 7 VM is using libstdc++.x86_64 4.8.5-44.el7

which is where I think this comes from.

On my Ubuntu 18.04 VM there are no issues as:

$ strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX
list versions up to GLIBCXX_3.4.25.

Besides the test suite (when using the standalone-tests branch), other 
programs that build extensions like the Netbeans plugin for AOO and some 
of my other extension template projects use SDK tools like idlc, 
regmerge, and javamaker from the installed AOO that may be affected by 
the library versions used to build the SDK on newer platforms.


This is more of an FYI right now until I can do more testing.

Best regards,
Carl


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

Re: [NOTICE] - Moving and Upgrading of Buildbot Jobs

[Matthias Seidel]

Hi,

Am 12.11.21 um 00:13 schrieb Carl Marcum:
> Hi All,
>
> On 8/15/21 4:44 AM, Gavin McDonald wrote:
>> Hi All.
>>
>> This NOTICE goes out via BCC to all affected projects and to the
>> main bui...@apache.org mailing list.
>> Please have replies CC the builds list.
>>
>> https://ci.apache.org is currently on version 0.8 and is to be turned
>> off
>> soon.
>> https://ci2.apache.org is version 3.2 and is the direct replacement.
>>
>> If you project has Buildbot jobs they are listed here:
>>
>> https://cwiki.apache.org/confluence/display/INFRA/Buildbot+0.8+-%3E+3.2+Migration
>>
>>
>> Infra will perform the migration for you over the next 2 weeks. Starting
>> Monday.
>>
>> Your $project.conf code will be updated to be compatible with
>> Buildbot 3.2
>> (from 0.8)
>>
>> Unless you state otherwise - your config will be moved to a new SVN
>> [1] or
>> GIT [2] area
>> depending on whether you primarily use SVN or GIT.
>>
>> [1] - https://svn.apache.org/repos/infra/infrastructure/buildbot2
>> [2] - https://github.com/apache/infrastructure-bb2
>>
>> An INFRA ticket will be created for each project migration and your dev
>> list will be kept in the loop.
>>
>> For those of you with nightly builds that use ci.apache.org/projects/* -
>> please note that this service is deprecated and will NOT be available
>> going
>> forward. Instead, your jobs should be changed to upload to
>> https://nightlies.apache.org/$project/* instead. Please request if
>> you want
>> your existing content migrated over otherwise we will not do so.
>>
>> After migration: Once everybody is off of the old Buildbot 0.8 - we will
>> change ci.apache.org to point to the new 3.2 instance. We will also
>> put in
>> a redirect for ci.apache.org/projects/$project/* to point to your new
>> location at nightlies.apache.org/$project/*
>>
>> Please let us know if you have any questions. Either Drew Foulks or
>> myself
>> will perform your migration.
>>
>> Kind Regards.
>>
>
> Looks like I missed this.
>
> As anyone looked into getting our builds migrated yet?

I don't think so.

The Linux buildbots hang for 60 days.

Our Windows buildbot has problems for the last days.
I understand that we have a Windows 11 buildbot somewhere now, but we
will have to see if our old environment works on Windows 11.

Regards,

   Matthias

>
> Thanks,
> Carl
>
> -
> 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: [NOTICE] - Moving and Upgrading of Buildbot Jobs

[Carl Marcum]

Hi All,

On 8/15/21 4:44 AM, Gavin McDonald wrote:

Hi All.

This NOTICE goes out via BCC to all affected projects and to the
main bui...@apache.org mailing list.
Please have replies CC the builds list.

https://ci.apache.org is currently on version 0.8 and is to be turned off
soon.
https://ci2.apache.org is version 3.2 and is the direct replacement.

If you project has Buildbot jobs they are listed here:

https://cwiki.apache.org/confluence/display/INFRA/Buildbot+0.8+-%3E+3.2+Migration

Infra will perform the migration for you over the next 2 weeks. Starting
Monday.

Your $project.conf code will be updated to be compatible with Buildbot 3.2
(from 0.8)

Unless you state otherwise - your config will be moved to a new SVN [1] or
GIT [2] area
depending on whether you primarily use SVN or GIT.

[1] - https://svn.apache.org/repos/infra/infrastructure/buildbot2
[2] - https://github.com/apache/infrastructure-bb2

An INFRA ticket will be created for each project migration and your dev
list will be kept in the loop.

For those of you with nightly builds that use ci.apache.org/projects/* -
please note that this service is deprecated and will NOT be available going
forward. Instead, your jobs should be changed to upload to
https://nightlies.apache.org/$project/* instead. Please request if you want
your existing content migrated over otherwise we will not do so.

After migration: Once everybody is off of the old Buildbot 0.8 - we will
change ci.apache.org to point to the new 3.2 instance. We will also put in
a redirect for ci.apache.org/projects/$project/* to point to your new
location at nightlies.apache.org/$project/*

Please let us know if you have any questions. Either Drew Foulks or myself
will perform your migration.

Kind Regards.



Looks like I missed this.

As anyone looked into getting our builds migrated yet?

Thanks,
Carl

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

[GitHub] [openoffice-org] marcus-aoo commented on pull request #60: Update index2.html

[GitBox]

marcus-aoo commented on pull request #60:
URL: https://github.com/apache/openoffice-org/pull/60#issuecomment-966613132


   Thanks for the addition text. I've committed them and this + previous ones 
are now available for review:
   https://www.openoffice.org/fr/index2.html
   https://www.openoffice.org/fr/download/index2.html


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

Re: Openssl, serf and curl

[Matthias Seidel]

Am 11.11.21 um 19:15 schrieb Jim Jagielski:
>
>> On Nov 11, 2021, at 10:51 AM, Matthias Seidel  
>> wrote:
>>
>>
>>
>> I still think we should work on 2. somehow.
> For AOO42X and above, I agree. It's a lot of work for AOO41X simply because 
> of the additional requirements for the old build systems.

OK for me, if we can reconfigure the server.




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Openssl, serf and curl

[Jim Jagielski]

> On Nov 11, 2021, at 10:51 AM, Matthias Seidel  
> wrote:
> 
> 
> 
> I still think we should work on 2. somehow.

For AOO42X and above, I agree. It's a lot of work for AOO41X simply because of 
the additional requirements for the old build systems.

Re: Openssl, serf and curl

[Matthias Seidel]

Am 11.11.21 um 14:59 schrieb Jim Jagielski:
> Wild question: Why do we even need TLS? I know, I know, that there is this 
> push for SSL everywhere, but really, despite what the powers behind the "new 
> internet" think, not all comms require TLS.
>
> But Ok, with that off my chest :)
>
> So we think/know that OpenSSL1.1 would NOT have that problem because it works 
> around the LetsEncrypt issue. Which means we have 2 options:
>
>   1. Stay w/ OpenSSL 1.0.2 and use the LE hack mentioned in this thread
>   2. Upgrade all to OpenSSL 1.1

In the short term we should do 1.
We would need to ask SourceForge if they can configure the certificates
for the extension site as mentioned.

And we should start to move our Update Feed locations to a seperate
server which also could have older TLS enabled.

I still think we should work on 2. somehow.

>
> My assumption is that dropping Serf for Curl wouldn't make a difference since 
> both use OpenSSL
>
>> On Nov 11, 2021, at 8:46 AM, Matthias Seidel  
>> wrote:
>>
>> Hi Jim,
>>
>> Am 11.11.21 um 14:16 schrieb Jim Jagielski:
>>> According to the serf mailing list, there are issues, at least with the 
>>> test suite.
>>>
>>> Can someone confirm that AOO42X/trunk do NOT have the problem? It would be 
>>> a lot easier to back port the openssl and apr/serf stuff from those 
>>> branches to AOO41X than upgrade all to openssl1.1/serf1.3.9
>> I just started my xubuntu VM with AOO 4.2.0 and it has the same problem.
>> No connection to our Update Feed/Extension site.
>>
 On Nov 11, 2021, at 7:35 AM, Arrigo Marchiori  
 wrote:

 Hello Jim, All,

 On Wed, Nov 10, 2021 at 01:19:16PM -0500, Jim Jagielski wrote:

> To be honest, I think we are *stuck* with OpenSSL 1.0.2 until Serf
> is upgraded to support 1.1
 Sorry... do you mean _our_ serf?

 Because serf 1.3.9 seems to build and run fine standalone with openssl
 1.1.1.

 Thank you in advance for making this clear.

 Best regards,
 -- 
 Arrigo

 -
 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: Openssl, serf and curl

[Jim Jagielski]

Wild question: Why do we even need TLS? I know, I know, that there is this push 
for SSL everywhere, but really, despite what the powers behind the "new 
internet" think, not all comms require TLS.

But Ok, with that off my chest :)

So we think/know that OpenSSL1.1 would NOT have that problem because it works 
around the LetsEncrypt issue. Which means we have 2 options:

  1. Stay w/ OpenSSL 1.0.2 and use the LE hack mentioned in this thread
  2. Upgrade all to OpenSSL 1.1

My assumption is that dropping Serf for Curl wouldn't make a difference since 
both use OpenSSL

> On Nov 11, 2021, at 8:46 AM, Matthias Seidel  
> wrote:
> 
> Hi Jim,
> 
> Am 11.11.21 um 14:16 schrieb Jim Jagielski:
>> According to the serf mailing list, there are issues, at least with the test 
>> suite.
>> 
>> Can someone confirm that AOO42X/trunk do NOT have the problem? It would be a 
>> lot easier to back port the openssl and apr/serf stuff from those branches 
>> to AOO41X than upgrade all to openssl1.1/serf1.3.9
> 
> I just started my xubuntu VM with AOO 4.2.0 and it has the same problem.
> No connection to our Update Feed/Extension site.
> 
>> 
>>> On Nov 11, 2021, at 7:35 AM, Arrigo Marchiori  
>>> wrote:
>>> 
>>> Hello Jim, All,
>>> 
>>> On Wed, Nov 10, 2021 at 01:19:16PM -0500, Jim Jagielski wrote:
>>> 
 To be honest, I think we are *stuck* with OpenSSL 1.0.2 until Serf
 is upgraded to support 1.1
>>> Sorry... do you mean _our_ serf?
>>> 
>>> Because serf 1.3.9 seems to build and run fine standalone with openssl
>>> 1.1.1.
>>> 
>>> Thank you in advance for making this clear.
>>> 
>>> Best regards,
>>> -- 
>>> Arrigo
>>> 
>>> -
>>> 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: Openssl, serf and curl

[Matthias Seidel]

Hi Jim,

Am 11.11.21 um 14:16 schrieb Jim Jagielski:
> According to the serf mailing list, there are issues, at least with the test 
> suite.
>
> Can someone confirm that AOO42X/trunk do NOT have the problem? It would be a 
> lot easier to back port the openssl and apr/serf stuff from those branches to 
> AOO41X than upgrade all to openssl1.1/serf1.3.9

I just started my xubuntu VM with AOO 4.2.0 and it has the same problem.
No connection to our Update Feed/Extension site.

>
>> On Nov 11, 2021, at 7:35 AM, Arrigo Marchiori  
>> wrote:
>>
>> Hello Jim, All,
>>
>> On Wed, Nov 10, 2021 at 01:19:16PM -0500, Jim Jagielski wrote:
>>
>>> To be honest, I think we are *stuck* with OpenSSL 1.0.2 until Serf
>>> is upgraded to support 1.1
>> Sorry... do you mean _our_ serf?
>>
>> Because serf 1.3.9 seems to build and run fine standalone with openssl
>> 1.1.1.
>>
>> Thank you in advance for making this clear.
>>
>> Best regards,
>> -- 
>> Arrigo
>>
>> -
>> 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: Openssl, serf and curl

[Jim Jagielski]

According to the serf mailing list, there are issues, at least with the test 
suite.

Can someone confirm that AOO42X/trunk do NOT have the problem? It would be a 
lot easier to back port the openssl and apr/serf stuff from those branches to 
AOO41X than upgrade all to openssl1.1/serf1.3.9

> On Nov 11, 2021, at 7:35 AM, Arrigo Marchiori  wrote:
> 
> Hello Jim, All,
> 
> On Wed, Nov 10, 2021 at 01:19:16PM -0500, Jim Jagielski wrote:
> 
>> To be honest, I think we are *stuck* with OpenSSL 1.0.2 until Serf
>> is upgraded to support 1.1
> 
> Sorry... do you mean _our_ serf?
> 
> Because serf 1.3.9 seems to build and run fine standalone with openssl
> 1.1.1.
> 
> Thank you in advance for making this clear.
> 
> Best regards,
> -- 
> Arrigo
> 
> -
> 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: Openssl, serf and curl

[Arrigo Marchiori]

Hello Jim, All,

On Wed, Nov 10, 2021 at 01:19:16PM -0500, Jim Jagielski wrote:

> To be honest, I think we are *stuck* with OpenSSL 1.0.2 until Serf
> is upgraded to support 1.1

Sorry... do you mean _our_ serf?

Because serf 1.3.9 seems to build and run fine standalone with openssl
1.1.1.

Thank you in advance for making this clear.

Best regards,
-- 
Arrigo

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

Re: Openssl, serf and curl

[Matthias Seidel]

Hi Jim,

Am 11.11.21 um 12:59 schrieb Jim Jagielski:
>
>> On Nov 10, 2021, at 1:33 PM, Matthias Seidel  
>> wrote:
>>
>> Am 10.11.21 um 19:30 schrieb Jim Jagielski:
>>> We could, but they are worse at releases than we are :-P
>> A problem that needs to be fixed... ;-)
>>
>> BTW: I think you reverted one of my commits?
> Yikes! I must have picked the wrong hash.

I just re-applied it...

>
 On Nov 10, 2021, at 1:24 PM, Matthias Seidel  
 wrote:

 Am 10.11.21 um 19:19 schrieb Jim Jagielski:
> To be honest, I think we are *stuck* with OpenSSL 1.0.2 until Serf is 
> upgraded to support 1.1
 Serf is an Apache project isn't it?

 Should we ask for collaboration?

>> On Nov 10, 2021, at 12:22 PM, Matthias Seidel 
>>  wrote:
>>
>> Am 10.11.21 um 18:05 schrieb Jim Jagielski:
>>> Ugg ugg and double ugg
>>>
>>> We seem to be stuck in a chicken-and-egg situation.
>>>
>>> Do we *really* need OpenSSL 1.1? Because even the latest release of 
>>> serf doesn't really support that.
>>>
>>> What is the issue w/ using OpenSSL 1.0.2 that is driving us to OpenSSL 
>>> 1.1?
>> The main problem is that Let's Encrypt root certificates expired at the
>> end of October and OpenSSL 1.0.2 has problems with the new ones:
>>
>> https://www.openssl.org/blog/blog/2021/09/13/LetsEncryptRootCertExpire/
>>
>> For whatever reason it still works on Windows, but AOO on Linux and
>> macOS cannot connect to our Update Feed and the extensions site anymore.
>>
>> Workaround 3 (mentioned in the article) would be a possibility to fix
>> that on the server side.
>>
>>> PS: OpenSSL is universally, IMO, becoming a major PITA. I'm all for 
>>> upgrades and keeping things fresh, but it seems like it is moving way 
>>> too fast for its consumers.
>>> -
>>> 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: Openssl, serf and curl

[Jim Jagielski]

> On Nov 10, 2021, at 1:33 PM, Matthias Seidel  
> wrote:
> 
> Am 10.11.21 um 19:30 schrieb Jim Jagielski:
>> We could, but they are worse at releases than we are :-P
> 
> A problem that needs to be fixed... ;-)
> 
> BTW: I think you reverted one of my commits?

Yikes! I must have picked the wrong hash.

> 
>> 
>>> On Nov 10, 2021, at 1:24 PM, Matthias Seidel  
>>> wrote:
>>> 
>>> Am 10.11.21 um 19:19 schrieb Jim Jagielski:
 To be honest, I think we are *stuck* with OpenSSL 1.0.2 until Serf is 
 upgraded to support 1.1
>>> Serf is an Apache project isn't it?
>>> 
>>> Should we ask for collaboration?
>>> 
 
> On Nov 10, 2021, at 12:22 PM, Matthias Seidel 
>  wrote:
> 
> Am 10.11.21 um 18:05 schrieb Jim Jagielski:
>> Ugg ugg and double ugg
>> 
>> We seem to be stuck in a chicken-and-egg situation.
>> 
>> Do we *really* need OpenSSL 1.1? Because even the latest release of serf 
>> doesn't really support that.
>> 
>> What is the issue w/ using OpenSSL 1.0.2 that is driving us to OpenSSL 
>> 1.1?
> The main problem is that Let's Encrypt root certificates expired at the
> end of October and OpenSSL 1.0.2 has problems with the new ones:
> 
> https://www.openssl.org/blog/blog/2021/09/13/LetsEncryptRootCertExpire/
> 
> For whatever reason it still works on Windows, but AOO on Linux and
> macOS cannot connect to our Update Feed and the extensions site anymore.
> 
> Workaround 3 (mentioned in the article) would be a possibility to fix
> that on the server side.
> 
>> PS: OpenSSL is universally, IMO, becoming a major PITA. I'm all for 
>> upgrades and keeping things fresh, but it seems like it is moving way 
>> too fast for its consumers.
>> -
>> 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: Who moderates users...@openoffice.apache.org?

[Dr. Michael Stehmann]

Hello Jörg,

please read what Matthias really wrote.

There is _no_ sentence "Jörg is a liar." written by hin. So it is your 
own and very special allegation he might called you a liar.


I wrote:

"we know that you have another point of view regarding facts than some 
other participants of this list."


And I think recently that's true.

Matthias gave an interpretation of the term "another point of view 
regarding facts" to such an extent I would have called you a liar (if I 
would use the wording of "the old times"). He only interpreted my 
expression in the sentence above.


But this interpretation is very one-sided and narrowing  because I 
respect " Hanlon’s Razor". I would never presume a lie, if there are 
many other explanations for a behavior.


To finish the discussion on my side:

You should also try to differ between censorship and repression and a 
friendly minded "si tacuisses, philosophus mansisses".


EOD

Regards
Michael



OpenPGP_signature
Description: OpenPGP digital signature