Re: English dictionary
Am 02.11.19 um 23:24 schrieb Rory O'Farrell: > On Sat, 2 Nov 2019 23:03:12 +0100 > Matthias Seidel wrote: > >> Hi all, >> >> Marco did update the English dictionary, but I think the page got >> unpublished again: >> >> https://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice >> >> @Andrea: Can you fix it? ;-) >> >> Regards, >> >> Matthias >> >> > Yes, I get an Access denied message "You do not have permission to access > this page" The web frontend is "broken", but you can still download it via: https://sourceforge.net/projects/aoo-extensions/files/17102/49/ Matthias > > Rory > > smime.p7s Description: S/MIME Cryptographic Signature
Re: English dictionary
Well, it happens every time and I am annoyed with it, so I just upload the .oxt and fill the fields. I no longer check if it works or not as I did all the correct procedures. On 02/11/2019 22:03, Matthias Seidel wrote: > Hi all, > > Marco did update the English dictionary, but I think the page got > unpublished again: > > https://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice > > @Andrea: Can you fix it? ;-) > > Regards, > > Matthias > > -- signature.asc Description: OpenPGP digital signature
Re: English dictionary
On Sat, 2 Nov 2019 23:03:12 +0100 Matthias Seidel wrote: > Hi all, > > Marco did update the English dictionary, but I think the page got > unpublished again: > > https://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice > > @Andrea: Can you fix it? ;-) > > Regards, > > Matthias > > Yes, I get an Access denied message "You do not have permission to access this page" Rory -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
English dictionary
Hi all, Marco did update the English dictionary, but I think the page got unpublished again: https://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice @Andrea: Can you fix it? ;-) Regards, Matthias smime.p7s Description: S/MIME Cryptographic Signature
Re: [openoffice] 03/03: Fixes from upstream for newer GCC
Hi Ariel, Am 02.11.19 um 18:57 schrieb Matthias Seidel: > Hi Ariel, > > Am 02.11.19 um 18:49 schrieb Ariel Constenla-Haile: >> On Sat, Nov 2, 2019 at 5:53 AM Peter Kovacs wrote: >>> On Windows the issue is that the Git() command checks out the data at a >>> position where cygwin does not see it. >>> >>> On the other hand if I pass the command directly no checkout happens. >> It's always useful to see the logs: >> https://ci.apache.org/builders/openoffice-win7/builds/37/steps/git%20clone%20under%20cygwin/logs/stdio >> >> + cd /home/buildslave >> ... >> + git clone --single-branch --branch trunk >> https://gitbox.apache.org/repos/asf/openoffice.git build >> fatal: destination path 'build' already exists and is not an empty directory. >> >> You have to cd to the right dir, quite strange some line below you >> seem to do so... >> You also removed the svn revision stuff but left got_revision. >> It looks like the underlying OS was changed from Win7 32 bits to Win10 >> 64 bits, that's good news, the buildbot is capable of building >> releases. > Yes, Windows was updated some years ago, but we didn't change the names > of the builbots... ;-) >> Quite strange you changed the name (aoo - openoffice) but not the win7 ;) >> >> Now the buildbot stops due to missing NASM >> https://ci.apache.org/builders/openoffice-win7/builds/40/steps/configure/logs/stdio >> checking nasm.exe assembler path... checking for nasm.exe... no >> configure: error: NASM is required to build on Windows, please install >> or use --with-nasm-home >> program finished with exit code 1 > NASM is a new requirement now. I think it was related to the updated > OpenSSL version. >> I don't have any machine with Windows to build, so please someone >> building master/trunk on Windows (Matthias?) open a jira ticket >> requesting to install NASM (once installed, the shell command should >> include the new switch). > I will do so! Done: https://issues.apache.org/jira/browse/INFRA-19373 I have also added you to our Slack channel, I hope you don't mind... ;-) Matthias > > Regards, > > Matthias > >> Regards smime.p7s Description: S/MIME Cryptographic Signature
Re: [openoffice] 03/03: Fixes from upstream for newer GCC
Update to Python 3 is reported as an issue since 2014: https://bz.apache.org/ooo/show_bug.cgi?id=123975 - Mail original - > De: "Don Lewis" > À: dev@openoffice.apache.org > Envoyé: Samedi 2 Novembre 2019 19:09:17 > Objet: Re: [openoffice] 03/03: Fixes from upstream for newer GCC > > On 2 Nov, Ariel Constenla-Haile wrote: > > Hi Don, > > > > On Fri, Nov 1, 2019 at 8:06 PM Don Lewis > > wrote: > >> nss really needs to be updated. Unfortunately very recent > >> versions > >> can't be built with some of the ancient compilers that we are > >> stuck with > >> (like the old version of Visual C++ that we use for 32-bit Windows > >> builds), or at least not without an insane amount of patching. > > > > Python 2 is going EOL on January 1 2020 > > https://www.python.org/doc/sunset-python-2/ > > https://pythonclock.org/ > > > > But Python 3 needs a more recent Visual Studio > > https://devguide.python.org/setup/#windows > > Unless AOO drops support for Python, updating the version of the > > Windows compiler seems a priority, python clock is ticking. > > Yes, we need to upgrade to python 3 for 4.2.x and higher. This is an > incompatible change, so it's probably not appropriate for 4.1.x. > I've > tried building the FreeBSD port with the system python 3 and the > build > fails, so there are probably some other code changes required. I > haven't > delved into that at all. > > Recent versions of nss are written using c99 features. It looks like > we > need Visual Studio 2015 for that. > > What version do we need for python 3? > > >> I don't know if gcc on CentOS 6 is also a problem. > > > > It seems Jim was building 4.1.7 on CentOS 5 and 4.2 on 7 > > I've been building both on CentOS 6. My CentOS 5 VM broke and I > haven't > been able to fix it. > > > -- > > Ariel Constenla-Haile > > La Plata, Buenos Aires > > Argentina > > > > - > > 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: [openoffice] 03/03: Fixes from upstream for newer GCC
On 2 Nov, Matthias Seidel wrote: > Hi Ariel, > > Am 02.11.19 um 18:49 schrieb Ariel Constenla-Haile: >> On Sat, Nov 2, 2019 at 5:53 AM Peter Kovacs wrote: >>> On Windows the issue is that the Git() command checks out the data at a >>> position where cygwin does not see it. >>> >>> On the other hand if I pass the command directly no checkout happens. >> It's always useful to see the logs: >> https://ci.apache.org/builders/openoffice-win7/builds/37/steps/git%20clone%20under%20cygwin/logs/stdio >> >> + cd /home/buildslave >> ... >> + git clone --single-branch --branch trunk >> https://gitbox.apache.org/repos/asf/openoffice.git build >> fatal: destination path 'build' already exists and is not an empty directory. >> >> You have to cd to the right dir, quite strange some line below you >> seem to do so... >> You also removed the svn revision stuff but left got_revision. >> It looks like the underlying OS was changed from Win7 32 bits to Win10 >> 64 bits, that's good news, the buildbot is capable of building >> releases. > Yes, Windows was updated some years ago, but we didn't change the names > of the builbots... ;-) >> Quite strange you changed the name (aoo - openoffice) but not the win7 ;) >> >> Now the buildbot stops due to missing NASM >> https://ci.apache.org/builders/openoffice-win7/builds/40/steps/configure/logs/stdio >> checking nasm.exe assembler path... checking for nasm.exe... no >> configure: error: NASM is required to build on Windows, please install >> or use --with-nasm-home >> program finished with exit code 1 > NASM is a new requirement now. I think it was related to the updated > OpenSSL version. Yes. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [openoffice] 03/03: Fixes from upstream for newer GCC
On 2 Nov, Ariel Constenla-Haile wrote: > Hi Don, > > On Fri, Nov 1, 2019 at 8:06 PM Don Lewis wrote: >> nss really needs to be updated. Unfortunately very recent versions >> can't be built with some of the ancient compilers that we are stuck with >> (like the old version of Visual C++ that we use for 32-bit Windows >> builds), or at least not without an insane amount of patching. > > Python 2 is going EOL on January 1 2020 > https://www.python.org/doc/sunset-python-2/ > https://pythonclock.org/ > > But Python 3 needs a more recent Visual Studio > https://devguide.python.org/setup/#windows > Unless AOO drops support for Python, updating the version of the > Windows compiler seems a priority, python clock is ticking. Yes, we need to upgrade to python 3 for 4.2.x and higher. This is an incompatible change, so it's probably not appropriate for 4.1.x. I've tried building the FreeBSD port with the system python 3 and the build fails, so there are probably some other code changes required. I haven't delved into that at all. Recent versions of nss are written using c99 features. It looks like we need Visual Studio 2015 for that. What version do we need for python 3? >> I don't know if gcc on CentOS 6 is also a problem. > > It seems Jim was building 4.1.7 on CentOS 5 and 4.2 on 7 I've been building both on CentOS 6. My CentOS 5 VM broke and I haven't been able to fix it. > -- > Ariel Constenla-Haile > La Plata, Buenos Aires > Argentina > > - > 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: [openoffice] 03/03: Fixes from upstream for newer GCC
Hi Ariel, Am 02.11.19 um 18:49 schrieb Ariel Constenla-Haile: > On Sat, Nov 2, 2019 at 5:53 AM Peter Kovacs wrote: >> On Windows the issue is that the Git() command checks out the data at a >> position where cygwin does not see it. >> >> On the other hand if I pass the command directly no checkout happens. > It's always useful to see the logs: > https://ci.apache.org/builders/openoffice-win7/builds/37/steps/git%20clone%20under%20cygwin/logs/stdio > > + cd /home/buildslave > ... > + git clone --single-branch --branch trunk > https://gitbox.apache.org/repos/asf/openoffice.git build > fatal: destination path 'build' already exists and is not an empty directory. > > You have to cd to the right dir, quite strange some line below you > seem to do so... > You also removed the svn revision stuff but left got_revision. > It looks like the underlying OS was changed from Win7 32 bits to Win10 > 64 bits, that's good news, the buildbot is capable of building > releases. Yes, Windows was updated some years ago, but we didn't change the names of the builbots... ;-) > Quite strange you changed the name (aoo - openoffice) but not the win7 ;) > > Now the buildbot stops due to missing NASM > https://ci.apache.org/builders/openoffice-win7/builds/40/steps/configure/logs/stdio > checking nasm.exe assembler path... checking for nasm.exe... no > configure: error: NASM is required to build on Windows, please install > or use --with-nasm-home > program finished with exit code 1 NASM is a new requirement now. I think it was related to the updated OpenSSL version. > I don't have any machine with Windows to build, so please someone > building master/trunk on Windows (Matthias?) open a jira ticket > requesting to install NASM (once installed, the shell command should > include the new switch). I will do so! Regards, Matthias > > Regards smime.p7s Description: S/MIME Cryptographic Signature
Re: [openoffice] 03/03: Fixes from upstream for newer GCC
On Sat, Nov 2, 2019 at 5:53 AM Peter Kovacs wrote: > On Windows the issue is that the Git() command checks out the data at a > position where cygwin does not see it. > > On the other hand if I pass the command directly no checkout happens. It's always useful to see the logs: https://ci.apache.org/builders/openoffice-win7/builds/37/steps/git%20clone%20under%20cygwin/logs/stdio + cd /home/buildslave ... + git clone --single-branch --branch trunk https://gitbox.apache.org/repos/asf/openoffice.git build fatal: destination path 'build' already exists and is not an empty directory. You have to cd to the right dir, quite strange some line below you seem to do so... You also removed the svn revision stuff but left got_revision. It looks like the underlying OS was changed from Win7 32 bits to Win10 64 bits, that's good news, the buildbot is capable of building releases. Quite strange you changed the name (aoo - openoffice) but not the win7 ;) Now the buildbot stops due to missing NASM https://ci.apache.org/builders/openoffice-win7/builds/40/steps/configure/logs/stdio checking nasm.exe assembler path... checking for nasm.exe... no configure: error: NASM is required to build on Windows, please install or use --with-nasm-home program finished with exit code 1 I don't have any machine with Windows to build, so please someone building master/trunk on Windows (Matthias?) open a jira ticket requesting to install NASM (once installed, the shell command should include the new switch). Regards -- Ariel Constenla-Haile La Plata, Buenos Aires Argentina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Building AOO42X under Debian9
Hi Mechtilde, On Sat, Nov 2, 2019 at 11:49 AM Mechtilde wrote: > > Hello Ariel, > > I have 22 cores. What can be good values for build --all? It's just a question of doing maths: if I have 6 cores: -P3 -- -P2 = 3 modules in parallel, 2 jobs per module -P2 -- -P3 = 2 modules in parallel, 3 jobs per module WIth 22 cores, you can try -P5 -- -P4. But expect that build system might be broken. Regards -- Ariel Constenla-Haile La Plata, Buenos Aires Argentina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Building AOO42X under Debian9
Hello Ariel, I have 22 cores. What can be good values for build --all? Kind regards Mechtilde Am 02.11.19 um 15:11 schrieb Ariel Constenla-Haile: > Hi Mechtilde, > > On Sat, Nov 2, 2019 at 2:53 AM Mechtilde wrote: >>> I can sort of reproduce this, but with other modules, always if I >>> build with a single process; I guess you are building with >>> build --all >> >> yes I do so >>> without the -P switch. >> >> I use build --all -P12 -- -P12 >> >> we have sponsoring of a multicore maschine to build AOO >> >> What is the right configuration to build with as much Cores as possible? > > It depends on how many cores you have, because the first -PN is for > build.pl, it will process N modules at the same time, the second -PN > is passed to (d)make. > > Anyway, it should work with a single process; something is really > broken: drawinglayer is a dependency for svx, it should be built > first. > > Regards > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: Building AOO42X under Debian9
Hi Mechtilde, On Sat, Nov 2, 2019 at 2:53 AM Mechtilde wrote: > > I can sort of reproduce this, but with other modules, always if I > > build with a single process; I guess you are building with > > build --all > > yes I do so > > without the -P switch. > > I use build --all -P12 -- -P12 > > we have sponsoring of a multicore maschine to build AOO > > What is the right configuration to build with as much Cores as possible? It depends on how many cores you have, because the first -PN is for build.pl, it will process N modules at the same time, the second -PN is passed to (d)make. Anyway, it should work with a single process; something is really broken: drawinglayer is a dependency for svx, it should be built first. Regards -- Ariel Constenla-Haile La Plata, Buenos Aires Argentina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [openoffice] 03/03: Fixes from upstream for newer GCC
On Sat, Nov 2, 2019 at 5:53 AM Peter Kovacs wrote: > > I fixed the git statements on Linux. However now perl moduls are > missing. I have asked infra to fix it. Maybe I miss some pointers. Last time I added packages via puppet (*), but things changed since then, I asked on the INFRA issue. Is there a way to contact infra more directly? (*) https://github.com/apache/infrastructure-puppet/commit/66422bb0e21c204a6118e5bba15f028b92fe4e7a Regards -- Ariel Constenla-Haile La Plata, Buenos Aires Argentina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [openoffice] 03/03: Fixes from upstream for newer GCC
Hi Don, On Fri, Nov 1, 2019 at 8:06 PM Don Lewis wrote: > nss really needs to be updated. Unfortunately very recent versions > can't be built with some of the ancient compilers that we are stuck with > (like the old version of Visual C++ that we use for 32-bit Windows > builds), or at least not without an insane amount of patching. Python 2 is going EOL on January 1 2020 https://www.python.org/doc/sunset-python-2/ https://pythonclock.org/ But Python 3 needs a more recent Visual Studio https://devguide.python.org/setup/#windows Unless AOO drops support for Python, updating the version of the Windows compiler seems a priority, python clock is ticking. > I don't know if gcc on CentOS 6 is also a problem. It seems Jim was building 4.1.7 on CentOS 5 and 4.2 on 7 Regards -- Ariel Constenla-Haile La Plata, Buenos Aires Argentina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [openoffice] 03/03: Fixes from upstream for newer GCC
I fixed the git statements on Linux. However now perl moduls are missing. I have asked infra to fix it. Maybe I miss some pointers. On Windows the issue is that the Git() command checks out the data at a position where cygwin does not see it. On the other hand if I pass the command directly no checkout happens. I am looking for a timeslot to have another round for the windows build bots. And to go after the missing modules on Linux. On 01.11.19 18:37, Matthias Seidel wrote: > Hi Ariel, > > Am 01.11.19 um 18:20 schrieb Ariel Constenla-Haile: >> Hi Matthias, >> >> On Fri, Nov 1, 2019 at 6:17 AM Matthias Seidel >> wrote: >>> C:/Source/openoffice/main/nss/wntmsci12.pro/misc/build/nss-3.25/nss/cmd/signtool/sign.c(85) >>> : warning C4013: 'snprintf' undefined; assuming extern returning int >> Try with commit 60374adc815ee4dfe39410d357c22db295ee1026 > Thanks, I will try... >> Are the buildbots dead? > Yes, for some month now... > > First the Linux machines were upgraded to Ubuntu 18.04 and stopped > building from SVN. > Windows machines were fine until we switched to Git. > > Peter did some changes on the config, but apparently this didn't work out. > > Regards, > > Matthias > >> Regards >> -- >> Ariel Constenla-Haile >> La Plata, Buenos Aires >> Argentina >> >> - >> 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
