[GitHub] [openoffice] ardovm opened a new pull request, #175: Ensure compatibility with GNU Make 4.4
ardovm opened a new pull request, #175: URL: https://github.com/apache/openoffice/pull/175 Make >= 4.4 is today's default on Cygwin. Once approved, these edits shall be applied to AOO41X as well. Please squash these commits when merging this PR. -- 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: Probleme nach 4.1.14 Update
Hi All, FYI: Problem solved! Avast Antivirus blocked OpenOffice. This seems to happen from time to time: https://forum.openoffice.org/en/forum/viewtopic.php?t=103591 Regards, Matthias Am 07.03.23 um 10:46 schrieb Matthias Seidel: > > FYI: > > "Have been using Windows 10 with Apache Openoffice every day for years > now without any problems, always with the same settings. The system is > always up-to-date and set to me as administrator with all rights. > Since the update to 4.1.14, the files can only be opened read-only or > as a working copy. With the 4.1.13 on another computer it was still > normal to open, after the update to 4.1.14 then no longer." > > Translated with www.DeepL.com/Translator (free version) > > That seems to be from the second review complaining about "locked" > files from the Microsoft Store. > > AOO 4.1.14 has already been downloaded more than 400,000 times, so I > don't think this is a general problem. > > Since he seems to be from Germany I would take over via private Mail > and post the results here. > > Regards, > > Matthias > > Am 07.03.23 um 03:52 schrieb christian200...@aol.com.INVALID: >> Benutze nun seit Jahren täglich ohne Probleme Windows 10 mit Apache >> Openoffice, immer mit den selben Einstellungen. Das System ist >> zeitnah immer aktuell und auf mich als Administrator mit allen >> Rechten eingerichtet. Seit dem Update auf 4.1.14 lassen sich die >> Dateien nur Schreibgeschützt oder als Arbeitskopie öffnen. Mit der >> 4.1.13 auf einem anderem Rechner war es noch normal zu öffnen, nach >> dem Update auf 4.1.14 dann nicht mehr. >> >> - >> 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
[GitHub] [openoffice] Pilot-Pirx commented on pull request #173: fgrep is deprecated and may be removed soon, use grep -F instead
Pilot-Pirx commented on PR #173: URL: https://github.com/apache/openoffice/pull/173#issuecomment-1458166787 The same is valid for egrep -> grep -E -- 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
[GitHub] [openoffice] 20kdc opened a new pull request, #174: Remove use of pthread_mutexattr_setkind_np due to compile errors
20kdc opened a new pull request, #174: URL: https://github.com/apache/openoffice/pull/174 This is intended as an informative notification, since I have no idea how to actually create a bugzilla account. The code being removed here causes a compilation issue on Ubuntu Jammy Jellyfish. (undefined reference to `pthread_mutexattr_setkind_np`) The best I can tell, https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2003146 explains this somewhat. This workaround likely hasn't been necessary for the past 20 years, if glibc "converted to git" repositories are any indication (see for instance https://github.com/lattera/glibc/blob/d82e4c7bb231c9e0f835bd46467563ac3b56cebe/linuxthreads/sysdeps/pthread/pthread.h ). And indeed, anyone who would be attempting to run OpenOffice on such a system would likely encounter issues with the other varied libraries in use. Unfortunately other compilation issues prevented me from performing a full test, but osl mutex tests pass at least. -- 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
Fwd: Upgraded: grep 3.9
FYI
Weitergeleitete Nachricht
Betreff:Upgraded: grep 3.9
Datum: Mon, 06 Mar 2023 14:32:55 -0700
Von:Cygwin grep Co-Maintainer via Cygwin-announce
Antwort an: Cygwin
An: Cygwin Announcements
Kopie (CC): Cygwin grep Co-Maintainer
The following package has been upgraded in the Cygwin distribution:
* grep 3.9
GNU grep searches one or more input files for lines containing a match
to a specified pattern. By default, grep outputs the matching lines. The
GNU implementation includes several useful extensions over POSIX.
The previous release stated that egrep and fgrep are deprecated
obsolescent commands, will be dropped in future, and from this release
until then, every use will show a stderr warning message, reminding you
how to change your commands and scripts:
$ egrep ...
egrep: warning: egrep is obsolescent; using grep -E
...
$ fgrep ...
fgrep: warning: fgrep is obsolescent; using grep -F
...
Cygwin releases will suppress the egrep and fgrep warning messages, but
developers and maintainers should rigorously remove all such usages from
their practices and scripts, as those commands could be dropped, or any
warning messages could be treated as fatal errors, in future.
Other invalid usages documented previously also now generate stderr
warning or error messages e.g.
grep: warning: * at start of expression
grep: warning: ? at start of expression
grep: warning: + at start of expression
grep: warning: {...} at start of expression
grep: warning: stray \ before
grep: warning: stray \ before unprintable character
grep: warning: stray \ before white space
For more information see the project home pages:
https://www.gnu.org/software/grep/
https://sv.gnu.org/projects/grep/
For changes since the previous Cygwin release please see below or read
/usr/share/doc/grep/NEWS after installation; for complete details see:
/usr/share/doc/grep/ChangeLog
https://git.sv.gnu.org/gitweb/?p=grep.git;a=log;h=refs/tags/v3.9
Noteworthy changes in release 3.9 (2023-03-05) [stable]
* Bug fixes
With -P, some non-ASCII UTF8 characters were not recognized as
word-constituent due to our omission of the PCRE2_UCP flag. E.g.,
given f(){ echo Perú|LC_ALL=en_US.UTF-8 grep -Po "$1"; } and
this command, echo $(f 'r\w'):$(f '.\b'), before it would print ":r".
After the fix, it prints the correct results: "rú:ú".
When given multiple patterns the last of which has a back-reference,
grep no longer sometimes mistakenly matches lines in some cases.
[Bug#36148#13 introduced in grep 3.4]
smime.p7s
Description: S/MIME Cryptographic Signature
[GitHub] [openoffice] Pilot-Pirx opened a new pull request, #173: fgrep is deprecated and may be removed soon, use grep -F instead
Pilot-Pirx opened a new pull request, #173: URL: https://github.com/apache/openoffice/pull/173 I am not a developer, so comments are welcome! -- 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: Buildbot problems
Hi Damjan, I think it now breaks at the point where the external libraries should get pulled in from: https://github.com/apache/openoffice-externals I don't know what was changed recently with our buildbots. They were running perfectly for some time after Gavin moved them to the new server... This seems to be a constant battle. Meanwhile I will do my Windows test builds as usual. Regards, Matthias Am 07.03.23 um 05:50 schrieb Damjan Jovanovic: > Unfortunately that's not our only problem. > > Even before the MozillaBuild update, every "build --all" got "cancelled" > after about 37 minutes. For example see > https://ci2.apache.org/#/builders/67/builds/628 > > Regards > Damjan > > On Sun, Mar 5, 2023 at 10:16 PM Matthias Seidel > wrote: > >> Hi Damjan, >> >> Thank you for all the work on the buildbots! >> >> Looking at the Windows bot now: >> >> checking whether to build LDAP configuration backend... checking whether to >> build the internal NSS module... yes >> configure: error: Mozilla build tooling incomplete! >> >> It seems like MozillaBuild was updated to 4.x, which we do not support yet. >> >> Regards, >> >>Matthias >> >> Am 02.03.23 um 05:46 schrieb Damjan Jovanovic: >> >> On Sun, Jan 22, 2023 at 1:33 PM Matthias Seidel >> >> wrote: >> >> >> Now regarding Awk, instead of doing: >> rm /bin/awk >> mv /bin/gawk.exe /bin/awk.exe >> can't we prepend PATH with a directory containing an "awk" script that >> >> just >> >> calls gawk.exe? >> >> It would be great if there is a better way to do it. I just followed our >> Windows building guide all these years. >> >> But this is beyond my capabilities and one of the reasons why I cannot >> maintain our buildbots anymore. >> >> >> This approach did eventually work. I eventually succeeded in creating an >> "awk" script that calls "gawk" and setting PATH to its directory within >> Cygwin, and ./configure now gets further. >> >> Now the next problem is that Cygwin doesn't have gcc and g++ >> (https://ci2.apache.org/#/builders/67/builds/516/steps/9/logs/stdio): >> >> which: no gcc in >> >> >> (/cygdrive/e/buildbot/openoffice-win10/utils:/usr/local/bin:/usr/bin:/cygdrive/e/Python39/Scripts:/cygdrive/e/Python39:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Windows/System32/OpenSSH:/cygdrive/c/Program >> >> Files/Puppet Labs/Puppet/bin:/cygdrive/c/Program Files >> (x86)/Subversion/bin:/cygdrive/c/Program >> Files/Git/cmd:/cygdrive/e/buildbot/tools/Windows Kits/10/Windows >> Performance >> Toolkit:/cygdrive/c/Users/buildbot/AppData/Local/Microsoft/WindowsApps) >> configure: error: cygwin gcc and g++ are needed, please install them. >> >> How can we install them? >> >> That's an Infra job. ;-) >> >> >> >> Weeks ago, on the openoffice-win10 buildbot, many Cygwin dependencies >> somehow got deleted, and days of battling Buildbot and working with Infra >> on https://issues.apache.org/jira/browse/INFRA-24114 were needed to install >> them again. >> >> The git crlf problem on Cygwin was another major issue that needed fixing. >> >> Awk was another, my idea for an "awk" script that calls gawk didn't work, I >> ended up copying /usr/bin/gawk.exe to awk.exe in a directory that is then >> prepended to the PATH environment variable passed to "configure" and >> "build", which worked in my own build and should work on the buildbot too. >> Since this copies gawk on every build, this approach won't be broken by >> future Cygwin upgrades like our previous renaming of gawk to awk by Infra >> was. >> >> I also changed haltOnFailure to False for the "build" step, so that the >> logs are uploaded even when the build fails, like the Linux buildbots do. >> Haven't checked whether that works yet. >> >> It eventually got through configure and started building, but every time >> that happened, the build was cancelled somehow. >> >> Then Java 8 changed somehow (upgrade or whatever), and Java detection >> broke. That has taken several more weeks to fix, and a command I was trying >> to run to log Java's files wasn't working due to a missing bracket which I >> eventually found and fixed. >> >> A further Java problem is that oowintool fails to detect Java, as it's >> looking for the 32 bit Java registry key, while we only have a 64 bit Java >> installed. I had to dig through the buildbot script's history to find a >> working 32 bit Java directory to specify (which oowintool can't detect >> because it's just unzipped, not installed and added to the registry). >> >> With those endless problems fixed, the build is now progressing >> nicely:https://ci2.apache.org/#/builders/67/builds/625 >> >> >> Regards, >> >>Matthias >> >> >> >> Regards >> Damjan >> >> >> smime.p7s Description: S/MIME Cryptographic Signature
Re: Probleme nach 4.1.14 Update
FYI: "Have been using Windows 10 with Apache Openoffice every day for years now without any problems, always with the same settings. The system is always up-to-date and set to me as administrator with all rights. Since the update to 4.1.14, the files can only be opened read-only or as a working copy. With the 4.1.13 on another computer it was still normal to open, after the update to 4.1.14 then no longer." Translated with www.DeepL.com/Translator (free version) That seems to be from the second review complaining about "locked" files from the Microsoft Store. AOO 4.1.14 has already been downloaded more than 400,000 times, so I don't think this is a general problem. Since he seems to be from Germany I would take over via private Mail and post the results here. Regards, Matthias Am 07.03.23 um 03:52 schrieb christian200...@aol.com.INVALID: > Benutze nun seit Jahren täglich ohne Probleme Windows 10 mit Apache > Openoffice, immer mit den selben Einstellungen. Das System ist zeitnah > immer aktuell und auf mich als Administrator mit allen Rechten > eingerichtet. Seit dem Update auf 4.1.14 lassen sich die Dateien nur > Schreibgeschützt oder als Arbeitskopie öffnen. Mit der 4.1.13 auf > einem anderem Rechner war es noch normal zu öffnen, nach dem Update > auf 4.1.14 dann nicht mehr. > > - > 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
