Re: help needed with LibreOffice Java bridge on s390x/ppc64el

2023-12-02 Thread Rene Engelhard
Hi, Am 23.10.23 um 21:59 schrieb Rene Engelhard: Am 29.10.23 um 11:13 schrieb Rene Engelhard: > (The workaround would be --without-java which I verified to work on > zelenka (see aboe), but this opens a can of worms. Not only disabling > some (built-in) features like the Repor

Re: help needed with LibreOffice Java bridge on s390x/ppc64el

2023-10-24 Thread Rene Engelhard
Hi, Am 24.10.23 um 15:45 schrieb René Engelhard: Am 24. Oktober 2023 08:58:22 MESZ schrieb John Paul Adrian Glaubitz: Hello! On Mon, 2023-10-23 at 23:20 +0200, Rene Engelhard wrote: we're explicitly building with OpenJDK 8 while Debian builds with OpenJDK 17 [2] which might explain

Re: help needed with LibreOffice Java bridge on s390x/ppc64el

2023-10-23 Thread Rene Engelhard
Hi, Am 23.10.23 um 23:06 schrieb John Paul Adrian Glaubitz: On Mon, 2023-10-23 at 21:59 +0200, Rene Engelhard wrote: since LibreOffice 7.6 (which added some more tests which were manual before to the automatic set) the testtools' bridge test fails: https://buildd.debian.org/status/fetch.php

Re: help needed with LibreOffice Java bridge on s390x/ppc64el

2023-10-23 Thread Rene Engelhard
Hi, forgot to edit $SUBJECT. This is just ppc64el for now. (While s390x also has broken bridges --without-java doesn't seem to help here unfortunately :/) Regards, Rene Am 23.10.23 um 21:59 schrieb Rene Engelhard: Hi, since LibreOffice 7.6 (which added some more  tests which were manual

help needed with LibreOffice Java bridge on s390x/ppc64el

2023-10-23 Thread Rene Engelhard
Hi, since LibreOffice 7.6 (which added some more tests which were manual before to the automatic set) the testtools' bridge test fails: https://buildd.debian.org/status/fetch.php?pkg=libreoffice=ppc64el=4%3A7.6.2-3=1697981409=0 See the discussion upstream in

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

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 actual

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

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 --bundled

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 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: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 replying

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 spellchecking

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: 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

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: 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

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-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 qual

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

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 many

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

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/

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 Debi

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

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

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

2023-01-10 Thread Rene Engelhard
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++ UNO

Re: Bug#948120: libreoffice: Incorrect conditional test to enable BUILD_NOGUI_PACKAGES

2020-01-04 Thread Rene Engelhard
(1:6.2.3~rc2-1) experimental; urgency=medium * New upstream release candidate * debian/rules: - replace various $(findstring for arch checks by $(filter -- Rene Engelhard Tue, 16 Apr 2019 22:25:38 +0200 This one sneaked in when doing -nogui in 6.4.x, and $ grep findstring * | grep A

Re: Bug#948120: libreoffice: Incorrect conditional test to enable BUILD_NOGUI_PACKAGES

2020-01-04 Thread Rene Engelhard
Hi, On Sat, Jan 04, 2020 at 02:33:51PM +0100, John Paul Adrian Glaubitz wrote: > On 1/4/20 2:28 PM, Rene Engelhard wrote: > > That just means that BUILD_NOGUI_PACKAGES=n is set and the nogui part is > > not even tried. > > ppc64 is fast and has server uses, so should

Re: Bug#948120: libreoffice: Incorrect conditional test to enable BUILD_NOGUI_PACKAGES

2020-01-04 Thread Rene Engelhard
Hi, On Sat, Jan 04, 2020 at 02:07:36PM +0100, John Paul Adrian Glaubitz wrote: > On 1/4/20 10:19 AM, John Paul Adrian Glaubitz wrote: > > I haven't verified it, but my suspicion is that the following conditional > > test is > > incorrect as the function findstring will match "ppc64" in

Re: Bug#667047: [Debian Sid] unmet dependencies

2012-04-03 Thread Rene Engelhard
Hi, On Tue, Apr 03, 2012 at 02:08:10PM -0400, Douglas Mencken wrote: And okay, which version shall I use? From apt-cache show? None. There is none for 3.5. Disabled. means disabled. Yes, this *is* expected. Because Base is disabled because the database checks in the testsuite failedi

Re: sun-java problem

2009-07-26 Thread Rene Engelhard
Hi, drz wrote: I installed openjdk-6-jjre, but it doesnt appear in about:plugins in iceweasel, though I did an update-alternatives java and chose that package. Is this normal? Yes. There's no OpenJDK plugin for ppc (neither has Sun one nor any other Java except gcj and relted) and the

Re: make errors - continued

2008-12-22 Thread Rene Engelhard
dale wrote: does to me. Buy some glasses ;-) sammie:/usr/lib# less libc.so /* GNU ld script Use the shared library, but some functions are only in the static library, so try that secondarily. */ OUTPUT_FORMAT(elf32-i386) ^ elf32-i386 != elf32-powerpc.

Re: Re: problem with bcm43xx after resume

2006-06-24 Thread Rene Engelhard
Eugen Dedu wrote: On 2.6.15, rmmod bcm43xx;modprobe bcm43xx after resume and afterwards ifup eth1 worked sometimes... Yes, but that's exactly what is bad. Regards, Rene -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: external VGA on iBook G4 with etch

2006-06-18 Thread Rene Engelhard
Hi, Alexander Schmehl wrote: Option UseFBDev true Note that this one will break VGA out with X.org 7. At least did there on my sid as I wanted a presentation ;) (iBook G4 1.33 12). Just commenting it out made it work again. Just for the record. Regards, Rene

Re: Bug#365010: Xserver G5 usb keyboard not loaded ...

2006-04-27 Thread Rene Engelhard
Hi, Sven Luther wrote: On Thu, Apr 27, 2006 at 04:52:09PM +0200, Andreas Barth wrote: * Sven Luther ([EMAIL PROTECTED]) [060427 15:05]: Andreas, do you have an explanation of why d-i commit access was taken from me, and why i find out only now as i was going to fix the issue ?

Re: Bug#365010: Xserver G5 usb keyboard not loaded ...

2006-04-27 Thread Rene Engelhard
Sven Luther wrote: On Thu, Apr 27, 2006 at 05:10:17PM +0200, Rene Engelhard wrote: Hi, Sven Luther wrote: On Thu, Apr 27, 2006 at 04:52:09PM +0200, Andreas Barth wrote: * Sven Luther ([EMAIL PROTECTED]) [060427 15:05]: Andreas, do you have an explanation of why d-i commit access

Re: libuno_sal.so.3 from OOo 2.0 needed

2006-04-02 Thread Rene Engelhard
Wojciech Owczarek wrote: I get some glibc symbol error with OOo that most probably will need a rebuild of openoffice (http://lists.debian.org/debian-glibc/2005/05/msg00030.html), but I wonder if a quick dirty fix of substituting the libuno_sal.so.3 file Why are you using 1.9.x? having that

Re: Build the bcm43xx with own kernel

2006-01-29 Thread Rene Engelhard
Hi, Emmanuel Galatoulas wrote: Well this reminds me of the kind of experiments I did myself trying to build the module on top of the kernel's own source! So if I recall correctly (there is a more extensive report in a previous post in the list) the errors you get are due to differences

Re: Build the bcm43xx with own kernel

2006-01-29 Thread Rene Engelhard
Hi, Joerg Sommer wrote: Rene Engelhard [EMAIL PROTECTED] wrote: Rene Engelhard wrote: ieee80211_crypt: unregistered algorithm 'NULL' ieee80211_crypt: registered algorithm 'NULL' ieee80211: 802.11 data/management/control stack, git-1.1.7 ieee80211: Copyright (C) 2004-2005 Intel

Re: Build the bcm43xx with own kernel

2006-01-28 Thread Rene Engelhard
Hi, Joerg Sommer wrote: Firstly I needed the header files for ieee80211softmac. After building and installing the package I found the include files in /usr/src/linux-headers-2.6.15.1. The bcm43xx make file searches for them in my kernel tree /usr/src/linux-2.6.15.1/. How can I merge them

Re: Build the bcm43xx with own kernel

2006-01-28 Thread Rene Engelhard
Rene Engelhard wrote: ieee80211_crypt: unregistered algorithm 'NULL' ieee80211_crypt: registered algorithm 'NULL' ieee80211: 802.11 data/management/control stack, git-1.1.7 ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED] ieee80211softmac: Unknown symbol

Re: Build the bcm43xx with own kernel

2006-01-28 Thread Rene Engelhard
Hi, Sven Luther wrote: Nope, it should point to /lib/modules/2.6.15-1-powerpc/build (or whatever your version is). for the own-build you mean? Yes, I thought yo too initially but the problem is that people might remove the dir it pointed to. But I guess I should change that. But then we still

Re: Build the bcm43xx with own kernel

2006-01-28 Thread Rene Engelhard
Rene Engelhard wrote: But I guess I should change that. But then we still have the problem where to put the needed changes headers (and thefore dpkg-divert'ed away) to be picked up by the build. Advices? Mmh, nevermind. I could still set SOFTMAC_DIR for it. Think-first-then-write. Regards

Re: 2.6.16-rc1

2006-01-23 Thread Rene Engelhard
Hi, Emmanuel Galatoulas wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Has anyone managed to get linux-2.6.16-rc1 to boot successfully on a powermac? It appears to detect the IDE controller and HDD on my mac mini, but then fails to mount the root fs. (It's hard to double check

Bug#348206: ITP: ieee80211softmac -- IEEE 802.11 SoftMAC kernel module

2006-01-15 Thread Rene Engelhard
Package: wnpp Severity: wishlist Owner: Rene Engelhard [EMAIL PROTECTED] * Package name: ieee80211softmac Version : 20060114 Upstream Authors: * Copyright (c) 2005 Johannes Berg [EMAIL PROTECTED] *Joseph Jezak [EMAIL PROTECTED] *Larry

Bug#348207: ITP: bcm43xx -- Broadcom 43xx Wireless LAN driver module

2006-01-15 Thread Rene Engelhard
Package: wnpp Severity: wishlist Owner: Rene Engelhard [EMAIL PROTECTED] * Package name: bcm43xx Version : 20060108 Upstream Authors: Copyright (c) 2005 Martin Langer [EMAIL PROTECTED], Stefano Brivio [EMAIL PROTECTED] Michael Buesch

Re: d-link dwl 122 workin?

2005-12-12 Thread Rene Engelhard
Thomas Harding wrote: On Mon, Dec 12, 2005 at 08:35:41AM +0100, Bjoern wrote: That was it! I did not know about the firmware. Strange but there is no package for ubuntu, I could not find either the source. So probably I will attend my new installation.. Thanks a lot, now I know what to

Re: d-link dwl 122 workin?

2005-12-11 Thread Rene Engelhard
Bjoern wrote: #=== INFRASTRUCTURE STATION === # What kind of authentication? AuthType=opensystem # opensystem | sharedkey (requires WEP) Make that sharedkey... SSID_wlan0=AEMILIA ENABLE_wlan0=y [ 1659.701345] prism2sta_getcardinfo: Failed to retrieve NICIDENTITY

Re: PPC Bleeding Edge OOo Builds

2005-06-16 Thread Rene Engelhard
Hi, dr allan wrote: **Note: I have made a similar request in debian-openoff, so if this crosses your eyes twice, please excuse me** ARGL. WTF are you then not CCing it.in *one* mail but writing *two*? Anyway, I already answered on -openoffice. Let's do eventual discussion there, Reply-To: