Re: Openssl, serf and curl
Hello All, excuse my late reply. On Thu, Nov 11, 2021 at 08:59:33AM -0500, Jim Jagielski wrote: > 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. +1 I can understand the importance of downloading AOO through https, as it gives an additional proof of the identity of the serving web site. But simple information such as "there is a new version" is IMHO not so important to require encryption, protection from man-in-the-middle attacks and all the other goodies of https. [...] > 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 > Then OpenSSL should be upgraded nevertheless! ;-) If I understood correctly, upgrading Serf would also require: 1- installing Scons. We could argue that we could ``throw our heart over the bar'' and engage into this, as it could be the (somewhat distant) future of AOO build system. 2- upgrading APR. I am a bit worried about what an APR upgrade would depend on by itself. But upgrading our dependencies should be considered A Good Thing, right? Dropping Serf could also be a good path to follow, as _lowering_ the number of our dependencies may be A Good Thing as well. But I have no idea of the effort that replacing Serf calls with equivalent Curl calls will require. I hope the above makes sense. Comments are welcome. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[Infra as code] A docker build environment for AOO
Hello all, I have created a dockerfile that creates an Image to build AOO on. Recently Arrigo tried it, and it did work for him too. I would like to query where you think it would be a good place to put this? The dockerfile depends on centos7 image, with Java 1.8 and an outdated ant. So probably small fixes are needed. I would maybe add a mwiki page next to our build guides, and have that explored there. Is this fine or someone has a better idea? All the best Peter - 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?
Hello Michael, > -Original Message- > From: Dr. Michael Stehmann [mailto:anw...@rechtsanwalt-stehmann.de] > Sent: Thursday, November 11, 2021 10:00 AM > To: dev@openoffice.apache.org > Subject: Re: Who moderates users...@openoffice.apache.org? > > 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. Michael, why are you accusing me of a "special allegation" here, when I have clearly asked(!): "Are you calling me a liar in public?" and by the way: Mathias has no right to talk about "old times" in relation to OpenOffice, because he was never part of those "old times". > You should also try to differ between censorship and repression and a > friendly minded "si tacuisses, philosophus mansisses". Mathias is not friendly to my person because he succumbed to a misunderstanding a long time ago and I am too angry to clear up this misunderstanding. > EOD +1 Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Infra as code] A docker build environment for AOO
Hello Peter, All, On Sat, Nov 13, 2021 at 10:24:20AM +0100, Peter Kovacs wrote: > Hello all, > > I have created a dockerfile that creates an Image to build AOO on. > > Recently Arrigo tried it, and it did work for him too. I would like to query > where you think it would be a good place to put this? IMHO we could put it on the SVN repository together with the build scripts. > The dockerfile depends on centos7 image, with Java 1.8 and an outdated ant. > So probably small fixes are needed. I suggested adding Java 1.7 because it is currently required by the build scripts for 4.2.0-Dev3. Hover [1] lists Java 8 as minimum requirement for all current and future releases, so... should we rather fix the build script? :-P > I would maybe add a mwiki page next to our build guides, and have that > explored there. Is this fine or someone has a better idea? +1: the building guide on our mwiki would be IMHO the best place. [1]: https://cwiki.apache.org/confluence/display/OOOUSERS/Target+System+Requirements Best regards, -- Arrigo - 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
Hi All, On 11/11/21 6:23 PM, Matthias Seidel wrote: 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 I'll contact infra and see what we need to do to get our builds running again. I've also found I cant get the last nightly from September to run on CentoOS 7. I'll discuss that in another thread. It may have an impact on what we can build with. 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
Hi Carl, Am 13.11.21 um 16:39 schrieb Carl Marcum: > Hi All, > > On 11/11/21 6:23 PM, Matthias Seidel wrote: >> 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 >>> > I'll contact infra and see what we need to do to get our builds > running again. The Windows bot seems to have lost connection to the upload location, builds run fine until the logs get uploaded. > > I've also found I cant get the last nightly from September to run on > CentoOS 7. > I'll discuss that in another thread. > > It may have an impact on what we can build with. Remember that the buildbots use Ubuntu. We do not get other machines from Infra, but we do not build releases on it. Regards, Matthias > > Best regards, > 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
Hi Matthias, On 11/13/21 10:48 AM, Matthias Seidel wrote: Hi Carl, Am 13.11.21 um 16:39 schrieb Carl Marcum: Hi All, On 11/11/21 6:23 PM, Matthias Seidel wrote: 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 I'll contact infra and see what we need to do to get our builds running again. The Windows bot seems to have lost connection to the upload location, builds run fine until the logs get uploaded. I've also found I cant get the last nightly from September to run on CentoOS 7. I'll discuss that in another thread. It may have an impact on what we can build with. Remember that the buildbots use Ubuntu. We do not get other machines from Infra, but we do not build releases on it. And that seems to be a problem because the last nightly 4.5.0 from September won't start for me on CentOS 7 which should be a supported platform. Runs fine on Ubuntu 18.04. It's hard to use them for testing if they don't run :( Best regards, Carl Regards, Matthias Best regards, 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: [Infra as code] A docker build environment for AOO
Hi Peter, On 11/13/21 9:47 AM, Arrigo Marchiori wrote: Hello Peter, All, On Sat, Nov 13, 2021 at 10:24:20AM +0100, Peter Kovacs wrote: Hello all, I have created a dockerfile that creates an Image to build AOO on. Recently Arrigo tried it, and it did work for him too. I would like to query where you think it would be a good place to put this? I'd like to try it also! IMHO we could put it on the SVN repository together with the build scripts. The dockerfile depends on centos7 image, with Java 1.8 and an outdated ant. So probably small fixes are needed. I don't know if it's feasible but I use SDKMAN on my systems to easily switch JDK's and versions of things like Java and Ant. It can be downloaded with curl. I suggested adding Java 1.7 because it is currently required by the build scripts for 4.2.0-Dev3. Hover [1] lists Java 8 as minimum requirement for all current and future releases, so... should we rather fix the build script? :-P I would maybe add a mwiki page next to our build guides, and have that explored there. Is this fine or someone has a better idea? +1: the building guide on our mwiki would be IMHO the best place. +1 for building guide. [1]: https://cwiki.apache.org/confluence/display/OOOUSERS/Target+System+Requirements Best regards, Do you think this could be used on a buildbot? I don't know much about the process yet but I think there is a problem with building on Ubuntu and running on CentOS 7. I'll have another thread for that but this maybe a solution. Let me know where I can find it. Thanks, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
problem reading old XML formats with trunk
Hi All, When I build trunk lately I'm getting build verification test failures for the following tests in bvt.gui.FileTypeTest testSaveNewSTC testSaveNewSTD testSaveNewSTI testSaveNewSTW testSaveNewSXC testSaveNewSXD testSaveNewSXI testSaveNewSXW I've also manually checked them by saving a new document in one of these formats. Close and reopen it and I get a Read Error. I've built and tested on CentOS 7 and Ubuntu 18.04 and get the same results. Does anyone have a recent build of trunk to confirm? Thanks, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
