AOO418 cherry picks
I've got a bunch of cherry picks that I'm planning to merge into AOO418. There are two categories: * Fixes from the FreeBSD port that have been upstreamed to the trunk and AOO42X branches, but I'm still carrying around in the FreeBSD port of 4.1.7. * Updates of a bunch of the bundled dependencies. These have been updated in AOO42X and trunk for a while, but haven't been merged to AOO418. The FreeBSD port mostly usees the system versions of these. I'd like to revisit: commit 7a3beb322b74df1b6c96e03605837df34781c68f Author: Matthias Seidel Date: Thu Oct 11 16:53:51 2018 + Rollback to Rev. 1843088 due to build errors. git-svn-id: https://svn.apache.org/repos/asf/openoffice/branches/AOO416@18438571 13f79535-47bb-0310-9956-ffa450edef68 I'm still using the patch for the FreeBSD port. Without it, a build with --enable-odk will fail with Java 8 or newer. I don't see how it would break the build since the changes are just to structured comments that are parsed to generate the documentation in the ODK. When this was backed out, I thought the reason was that building with a newer version of the JDK would prevent runtime detection of older versions of the JDK. So far asa I know, that's not a problem with AOO42X and trunk, which have the changes. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Results of 4.1.8 QA Testing on rev. 5e8bc5703f for Windows 10
Hi Keith, Am 24.08.20 um 00:02 schrieb Keith N. McKenna: > Hi Matthias; > On 8/23/2020 1:51 PM, Matthias Seidel wrote: >> Hi Keith, >> >> Am 23.08.20 um 19:35 schrieb Keith N. McKenna: >>> The results of my testing can be downloaded from the following link: >>> https://1drv.ms/t/s!AsMYmStvrJNJixd-w2GbfJt6h9S5 >> Thanks for testing > You are very welcome, we need to get this moving forward. Definitely! >> Regarding "Noto CJK font", I downloaded this one from Google: >> https://noto-website-2.storage.googleapis.com/pkgs/NotoSansCJKjp-hinted.zip >> > Thanks the original link in the issue did not have it. Will download and > retest All these "Noto" fonts are available via https://www.google.com/get/noto/ I installed "Noto Sans CJK JP Regular" to test PDF export. >> Regarding update check, my latest builds have updated openSSL: >> https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/ >> > Downloaded and will install and retest later tonight or tomorrow. Thanks again! Regards, Matthias > >> Regards, >> >> Matthias >> >>> Regards >>> Keith >>> > smime.p7s Description: S/MIME Cryptographic Signature
Re: Results of 4.1.8 QA Testing on rev. 5e8bc5703f for Windows 10
Hi Matthias; On 8/23/2020 1:51 PM, Matthias Seidel wrote: > Hi Keith, > > Am 23.08.20 um 19:35 schrieb Keith N. McKenna: >> The results of my testing can be downloaded from the following link: >> https://1drv.ms/t/s!AsMYmStvrJNJixd-w2GbfJt6h9S5 > > Thanks for testing You are very welcome, we need to get this moving forward. > > Regarding "Noto CJK font", I downloaded this one from Google: > https://noto-website-2.storage.googleapis.com/pkgs/NotoSansCJKjp-hinted.zip > Thanks the original link in the issue did not have it. Will download and retest > Regarding update check, my latest builds have updated openSSL: > https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/ > Downloaded and will install and retest later tonight or tomorrow. > Regards, > > Matthias > >> >> Regards >> Keith >> > signature.asc Description: OpenPGP digital signature
Re: Results of 4.1.8 QA Testing on rev. 5e8bc5703f for Windows 10
Hi Matthias, Don, all > Regarding update check, my latest builds have updated openSSL: > https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/ Just tested your AOO418m1(Build:9801) - Rev. 2b2dfb9831 under Windows 7 Pro x64 AOO and extension updates work as expected! In addition editing files over WebDAV on 4.1.8 works again (it was broken recently because Mailbox.org updated to TLS 1.3) Thank you very much to all for this essential update! I am a very happy user! Kind regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OpenSSL versions
Hi, Am 23.08.20 um 01:51 schrieb Dave Fisher: > Hi - > > This is excellent. I’ve been investigating the code. My Windows Test builds are up (incl. openSSL1.0.2t): https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/ > > The services are called from main/extensions/source/update/check/download.cxx > using Curl. > > To fully confirm the fix the next step is to check into curl dependencies: > > https://curl.haxx.se/docs/libs.html > > OpenSSL is one of Curl’s TLS providers. > > Judging from the config.log files from past releases in > https://svn.apache.org/viewvc/openoffice/devtools/build-scripts/ which only > go back to 4.1.2. > > (1) Mac versions of AOO since 4.1.2 are built using the SYSTEM_OPENSSL=“YES” > which should explain why we are getting update checks from many or most of > our user’s Mac installations. > > (2) Our released versions of Linux and Windows have SYSTEM_OPENSSL=“NO”. It > could be that the handful of versions that do work were compiled from source > with SYSTEM_OPENSSL=“YES”. > > Does this make sense? I am not sure, Windows has no SYSTEM_OPENSSL. Of course people could have edited the URL but why would they stay on an old version then? I had one week when AOO on Ubuntu could connect to the server, then it broke again. Something changed on the way from my computer to the update feed... Regards, Matthias > > Regards, > Dave > >> On Aug 22, 2020, at 3:32 PM, Don Lewis wrote: >> >> On 23 Aug, Matthias Seidel wrote: >>> Hi Don, >>> >>> Finished my Windows builds and AOO 4.1.8 can connect to both, AOO >>> updates and Extension updates. >> Cool. I'll go ahead and merge the pull request. >> >> >> - >> 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: [GitHub] [openoffice] DonLewisFreeBSD opened a new pull request #93: Force Linux builds to use gnu++98 (C++98 + GNU extensions) mode to be
On 23 Aug, GitBox wrote: > > DonLewisFreeBSD opened a new pull request #93: > URL: https://github.com/apache/openoffice/pull/93 > > >the most compatible with our old code base rather than relying on the >compiler default mode. Compiling in C++11 or newer mode is very noisy >due to deprecation warnings about our use of std::auto_ptr. If the >compiler defaults to C++17 mode or newer, the build would be totally >broken because std::auto_ptr is removed from C++17. > >There is an unknown amount of porting effort needed to convert to >std::unique_ptr, which has somewhat different semantics and which is >not available before C++11, which would break building with older versions >of gcc which default to gnu++98 mode. > >std::shared_ptr, might be an alternative since there is a BOOST >implementation. This reduction of compiler warnings reduces the size of the build log by 2/3rd when compiling with gcc 6.3.0. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice] DonLewisFreeBSD opened a new pull request #93: Force Linux builds to use gnu++98 (C++98 + GNU extensions) mode to be
DonLewisFreeBSD opened a new pull request #93: URL: https://github.com/apache/openoffice/pull/93 the most compatible with our old code base rather than relying on the compiler default mode. Compiling in C++11 or newer mode is very noisy due to deprecation warnings about our use of std::auto_ptr. If the compiler defaults to C++17 mode or newer, the build would be totally broken because std::auto_ptr is removed from C++17. There is an unknown amount of porting effort needed to convert to std::unique_ptr, which has somewhat different semantics and which is not available before C++11, which would break building with older versions of gcc which default to gnu++98 mode. std::shared_ptr, might be an alternative since there is a BOOST implementation. 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. 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: installing git on centos 5.5
On 23 Aug, Carl Marcum wrote: > I'm setting up a new CentOS 5.5 VM that I can build 4.1.x series on. > > First hurdle was figuring out out how to point to the vault.centos.org > archived rpms. > Unfortunately no git was available then. > > Was this done for the build servers or has anyone else done this and how > did you do it? You may have to download the source and build it yourself. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Results of 4.1.8 QA Testing on rev. 5e8bc5703f for Windows 10
Hi Keith, Am 23.08.20 um 19:35 schrieb Keith N. McKenna: > The results of my testing can be downloaded from the following link: > https://1drv.ms/t/s!AsMYmStvrJNJixd-w2GbfJt6h9S5 Thanks for testing! Regarding "Noto CJK font", I downloaded this one from Google: https://noto-website-2.storage.googleapis.com/pkgs/NotoSansCJKjp-hinted.zip Regarding update check, my latest builds have updated openSSL: https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/ Regards, Matthias > > Regards > Keith > smime.p7s Description: S/MIME Cryptographic Signature
Results of 4.1.8 QA Testing on rev. 5e8bc5703f for Windows 10
The results of my testing can be downloaded from the following link: https://1drv.ms/t/s!AsMYmStvrJNJixd-w2GbfJt6h9S5 Regards Keith signature.asc Description: OpenPGP digital signature
installing git on centos 5.5
I'm setting up a new CentOS 5.5 VM that I can build 4.1.x series on. First hurdle was figuring out out how to point to the vault.centos.org archived rpms. Unfortunately no git was available then. Was this done for the build servers or has anyone else done this and how did you do it? Thanks, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
000
Sirs/Madams, I am truly grateful for what you and your developers have done and for the efforts you all did for the software. Your efforts are appreciated. I hope you are all doing well. Take care of yourselves. Sincerely, C. Peralta
