binutils error? (autobuilder failure)

2003-02-05 Thread Rene Engelhard
stamp=1044431895&file=log&as=raw Regards, Rene -- .''`. Rene Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB

Re: binutils error? (autobuilder failure)

2003-02-05 Thread Rene Engelhard
Hi again, [ please Cc: me, as I am not subscribed to -68k ] Rene Engelhard wrote: > anyone of you know what causes the follwing build failure and what to do? > Versions till -3 built successfully; but binutils got updated > recently... > > http://buildd.debian.org/fetch.php?&

Re: binutils error? (autobuilder failure)

2003-02-05 Thread Rene Engelhard
Hi, [ please Cc: me as Iam not sucribed to -68k and not to -glibc ] Richard Zidlicky wrote: > On Wed, Feb 05, 2003 at 09:06:42AM +0100, Rene Engelhard wrote: > > anyone of you know what causes the follwing build failure and what to do? > > Versions till -3 built successfully; b

unbreaking LibreOffices tests on at least release architectures

2023-06-18 Thread Rene Engelhard
Hi, I originally wanted to send the mail after all the architectures got result but now even after 6d mips64el didn't try it so I send it now. Prompted by riscv64 supposed to be added to the archive and even as a release arch for trixie - see https://lists.debian.org/debian-devel-announce/2023/

Re: unbreaking LibreOffices tests on at least release architectures

2023-06-18 Thread Rene Engelhard
Hi, Am 18.06.23 um 10:19 schrieb John Paul Adrian Glaubitz: On Sun, 2023-06-18 at 09:31 +0200, Rene Engelhard wrote: Also note I am not talking about the debian-ports architectures. Those I forgot and I have no problems making them stay into "testsuite ran but results ignored" set

Re: unbreaking LibreOffices tests on at least release architectures

2023-06-18 Thread Rene Engelhard
Hi again. Am 18.06.23 um 10:32 schrieb Rene Engelhard: I don't really like sweeping it under the carpet again and would actually pursue the "getting those architectures removed from unstable" way pointed out and (implicitely) approved/suggested by the release team... You want

Re: unbreaking LibreOffices tests on at least release architectures

2023-06-18 Thread Rene Engelhard
Hi, Am 18.06.23 um 21:28 schrieb Rob Landley: Of course I mean "getting those architectures removed from unstable" *for libreoffice*. This is the same GPLv3 package that Red Hat just dropped support for? GPLv3 doesn't have anything to do with this here. https://lwn.net/Articles/933525/ Inde

Re: unbreaking LibreOffices tests on at least release architectures

2023-06-18 Thread Rene Engelhard
Hi again, some more comments. Am 18.06.23 um 21:28 schrieb Rob Landley: No, that's how I read it too. You said getting the _architectures_ removed, not getting libreoffice removed from those architectures. That is hilarious. The subject says we are talking about LibreOffice here, not genera

Re: unbreaking LibreOffices tests on at least release architectures

2023-06-19 Thread Rene Engelhard
Hi, Am 19.06.23 um 23:19 schrieb Adrian Bunk: On Sun, Jun 18, 2023 at 09:31:05AM +0200, Rene Engelhard wrote: ... I won't be of much help here unfortunately, except maybe testing patches, but then again there's porterboxes ... You are the only one who could realistically debug man

Re: unbreaking LibreOffices tests on at least release architectures

2023-06-19 Thread Rene Engelhard
Hi, Am 20.06.23 um 00:03 schrieb Jeffrey Walton: You can usually uncover them by building the package with CFLAGS=" ... -fsanitize=undefined ... " and CXXFLAGS=" ... -fsanitize=undefined ... ". The UBsan sanitizer operates on real data. There are no false positives. I'd personally assume this

Re: unbreaking LibreOffices tests on at least release architectures

2023-06-19 Thread Rene Engelhard
Hi, Am 19.06.23 um 23:29 schrieb Rene Engelhard: The pragmatic option would be to run only a smoketest for build success on architectures not tested by upstream. And have Format->Character in Impress crash with Bus error like on mipsel? That doesn't sound too good for basic quality.

Re: unbreaking LibreOffices tests on at least release architectures

2023-06-20 Thread Rene Engelhard
Hi, Am 20.06.23 um 16:52 schrieb Kurt Roeckx: On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote: Hi, Am 19.06.23 um 23:29 schrieb Rene Engelhard: The pragmatic option would be to run only a smoketest for build success on architectures not tested by upstream. And have Format

Re: unbreaking LibreOffices tests on at least release architectures

2023-06-25 Thread Rene Engelhard
Hi, Am 20.06.23 um 10:25 schrieb Adrian Bunk: On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote: Hi, Am 19.06.23 um 23:29 schrieb Rene Engelhard: The pragmatic option would be to run only a smoketest for build success on architectures not tested by upstream. And have Format

LibreOffice bridges/smoketest on mips(64)el (was: Re: unbreaking LibreOffices tests on at least release architectures)

2023-07-03 Thread Rene Engelhard
Hi, Am 25.06.23 um 13:37 schrieb Rene Engelhard: what about the following: - make all test failures fatal on a*64 (since upstream tests these), and - make smoketest failures fatal on all architectures (including ports) That was implemented (+ two more important tests) in experimental. See

Re: LibreOffice bridges/smoketest on mips(64)el (was: Re: unbreaking LibreOffices tests on at least release architectures)

2023-07-03 Thread Rene Engelhard
Hi, Am 03.07.23 um 21:31 schrieb Rene Engelhard: Am 25.06.23 um 13:37 schrieb Rene Engelhard: what about the following: - make all test failures fatal on a*64 (since upstream tests these), and - make smoketest failures fatal on all architectures (including ports) That was implemented (+ two

Re: unbreaking LibreOffices tests on at least release architectures

2023-07-22 Thread Rene Engelhard
Hi, Am 22.07.23 um 14:02 schrieb Andreas Schwab: On Jun 18 2023, Rene Engelhard wrote: For riscv64 I already pointed that out in the thread starting at https://lists.debian.org/debian-riscv/2023/06/msg0.html, but for the other architectures there is the mail now. riscv64 is different

Re: unbreaking LibreOffices tests on at least release architectures

2023-07-22 Thread Rene Engelhard
Hi, Am 22.07.23 um 14:09 schrieb Rene Engelhard: And that included packaged extensions so if they install but don't work that's a grave bug. And that includes LibreOffice-bundled extensions like the english,hungarian,russian grammar checker for example. Ot external finnish spe

Re: unbreaking LibreOffices tests on at least release architectures

2023-07-22 Thread Rene Engelhard
Hi, Am 22.07.23 um 14:25 schrieb Andreas Schwab: On Jul 22 2023, Rene Engelhard wrote: Just not registering or unregistering *any* extension. What does that mean? I haven't seen any errors about extensions. Do you run the testsuite? Especially the smoketest? And you are replyi

Re: unbreaking LibreOffices tests on at least release architectures

2023-07-22 Thread Rene Engelhard
Hi, Am 22.07.23 um 14:28 schrieb Andreas Schwab: On Jul 22 2023, Rene Engelhard wrote: Yes. _basically_. (Only with -O0 or maybe -Os as upstreams makefile says, though) On openSUSE Factory, libreoffice is built with the usual compiler flags, wich includes full optimisation and hardening

Re: unbreaking LibreOffices tests on at least release architectures

2023-07-22 Thread Rene Engelhard
Hi, Am 22.07.23 um 14:34 schrieb Andreas Schwab: On Jul 22 2023, Rene Engelhard wrote: And that includes LibreOffice-bundled extensions like the english,hungarian,russian grammar checker for example. Ot external finnish spellchecking, hyphenation and grammer checking. Or turkish spellchecing

Re: unbreaking LibreOffices tests on at least release architectures

2023-07-22 Thread Rene Engelhard
Hi, Am 22.07.23 um 15:02 schrieb Andreas Schwab: On Jul 22 2023, Rene Engelhard wrote: https://lists.debian.org/debian-riscv/2023/07/msg00014.html is for manual thing. And the IRC log shows that even libreoffice-lightproof-en etc don't appear as bundled extensions. $ unopkg list --bu

Re: unbreaking LibreOffices tests on at least release architectures

2023-07-22 Thread Rene Engelhard
Hi, Am 22.07.23 um 15:07 schrieb Andreas Schwab: Which gives the smoketest test failure here I pointed out (again) in my other mail. $ find /usr/lib64/libreoffice/ -name "*smoke*" /usr/lib64/libreoffice/program/classes/smoketest.jar How can I run that? You can't from that, ttbomk. You miss o

Re: unbreaking LibreOffices tests on at least release architectures

2023-07-22 Thread Rene Engelhard
Am 22.07.23 um 15:53 schrieb Andreas Schwab: On Jul 22 2023, Rene Engelhard wrote: Does opensuse have some public git/$VCS? https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/libreoffice/standard/riscv64 Thanks... But maybe I am too blind. I don't see the a

Re: unbreaking LibreOffices tests on at least release architectures

2023-07-22 Thread Rene Engelhard
Hi, Am 22.07.23 um 16:09 schrieb Andreas Schwab: On Jul 22 2023, Rene Engelhard wrote: Am 22.07.23 um 15:53 schrieb Andreas Schwab: On Jul 22 2023, Rene Engelhard wrote: Does opensuse have some public git/$VCS? https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV

LibreOffice architecture support (was: Fwd: Plan to remove dead C++ UNO bridge implementations (bridges/source/cpp_uno/*))

2023-01-10 Thread Rene Engelhard
dead C++ UNO bridge implementations (bridges/source/cpp_uno/*) Datum: Tue, 10 Jan 2023 17:31:12 +0100 Von:Stephan Bergmann An: libreoff...@lists.freedesktop.org Kopie (CC): Sakura286 , wjh-la , Rene Engelhard , Tor Lillqvist There are currently 27 different, per-platform C+