Bug#983843: xrdp FTBFS on several architectures

2021-03-22 Thread Thierry fa...@linux.ibm.com
At least that problem on ppc machines is due to fact that ppc64el is not taken in account properly A patch could be  diff xrdp-0.9.12/common/arch.h xrdp-bad/common/arch.h 64a65,70 > #if defined(__LITTLE_ENDIAN__) > #define L_ENDIAN > #else > #define B_ENDIAN > #endif > 68,69c74,75 <

Bug#942113: 3depict: FTBFS on PPC64EL - POWERPC macro not always defined

2019-10-16 Thread Thierry fa...@linux.ibm.com
Hello I've personally always used __powerpc__ . Here is my reference, very useful for all arch related defines : https://wiki.debian.org/ArchitectureSpecificsMemo Cheers Thierry I've Cc:-ed tille as his was the most recent upload. Let me know if you'd like me to NMU with a

Bug#942171: tcpdump: FTBFS on ppc64el for test ikev2pI2

2019-10-11 Thread Thierry fa...@linux.ibm.com
Source: tcpdump Version: 4.9.3-1 Severity: serious https://buildd.debian.org/status/logs.php?pkg=tcpdump=ppc64el=sid --- 1 tests failed 441 tests passed Failed test: ikev2pI2 41c41 < (v2auth: len=196 method=rsasig

Bug#918572: check FTBFS on ppc*: test failure

2019-09-23 Thread Thierry fa...@linux.ibm.com
this package rebuilt on ppc64el. It is still failing with GCC 9. Looks like further investigation is needed. https://buildd.debian.org/status/package.php?p=check Thanks, Boyuan Yang On Fri, 20 Sep 2019 09:57:02 +0200 "Thierry fa...@linux.ibm.com" < thie...@linux.ibm.com> wrote: On

Bug#918572: check FTBFS on ppc*: test failure

2019-09-20 Thread Thierry fa...@linux.ibm.com
On Mon, 07 Jan 2019 15:54:46 +0200 Adrian Bunk wrote: Source: check Version: 0.12.0-0.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=check ... FAIL: check_check_export FAIL: check_check PASS: test_output.sh PASS: test_check_nofork.sh PASS:

Bug#916145: closure-compiler: Not working with recent JS code

2019-03-21 Thread Thierry fa...@linux.ibm.com
Hello, Is that bug still valid with current version 20130227+dfsg1-10 ? thanks On Mon, 10 Dec 2018 17:42:12 +0100 Roland Gruber wrote: > Package: closure-compiler > Version: 20130227+dfsg1-9 > Severity: important > > Dear Maintainer, > > the current version is so old that it got incompatible

Bug#909750: applications tries to write to /usr/* directories via libfontconfig1

2019-03-21 Thread Thierry fa...@linux.ibm.com
On Sun, 11 Nov 2018 12:04:06 +0100 Jakub Wilk wrote: > * Laurent Bigonville , 2018-11-11, 11:18: > >Do you have any .uuid files in these directories? > > IIRC, I didn't have any back then. > > >Can you try to run "fc-cache -s -f -v" (as root) and see if it helps. > > I think I upgraded some

Bug#876905: qtwebkit should not be release with buster

2019-03-21 Thread Thierry fa...@linux.ibm.com
On Tue, 26 Sep 2017 22:15:12 +0300 Adrian Bunk wrote: > Source: qtwebkit > Version: 2.3.4.dfsg-9.1 > Severity: serious > Tags: buster sid > > qtwebkit should not be release with buster > (RC bugs are already open against all r-deps). > > As version 2.3.4.dfsg-10 is part of buster what do we

Bug#884128: libical: don't release with buster

2019-03-21 Thread Thierry fa...@linux.ibm.com
Hello, As currently we have (for most of the platforms) $ apt-cache madison libical2 libical2 | 2.0.0-4+b2 | http://ftp.fr.debian.org/debian buster/main amd64 Packages libical |2.0.0-4 | http://ftp.fr.debian.org/debian buster/main Sources What do we do with that bug ? Thanks On Wed,

Bug#878843: util-linux: fsck on btrfs /home hangs, stalling boot

2019-03-18 Thread Thierry fa...@linux.ibm.com
On Wed, 18 Oct 2017 08:42:32 -0400 Phil Susi wrote: > On 10/18/2017 3:54 AM, Bernhard Schmidt wrote: > > Accessing /home leads to a blocked process. The reason is that (for > > numerous years, due to reasons I don't remember) I had > > x-systemd.automount in my fstab for /home > > That makes

Bug#864423: Software RAID is not activated at boot time

2019-03-15 Thread Thierry fa...@linux.ibm.com
So what about adding case $Node_Name in /dev/*) Raid_Name=$(dmraid -i -r -cr $Node_Name | grep -vi "No RAID disks" > | grep -vi "formats discovered") break;; esac ou similar ? > > As $Node_Name already contains "/dev", in my case dmraid is called with > parameters /dev/dev/sdb and

Bug#844778: clsync FTBFS on !x86: error: '__NR_select' undeclared here

2019-02-20 Thread Thierry fa...@linux.ibm.com
On Sat, 19 Nov 2016 01:09:28 +0200 Adrian Bunk wrote: > Source: clsync > Version: 0.4.2-1 > Severity: serious > > https://buildd.debian.org/status/package.php?p=clsync=sid > > ... > In file included from privileged.c:64:0: > privileged.c:88:34: error: '__NR_select' undeclared here (not in a

Bug#909861: shark FTBFS on i386 with gcc 8

2019-02-20 Thread Thierry fa...@linux.ibm.com
On Sat, 29 Sep 2018 20:48:49 +0300 Adrian Bunk wrote: > Source: shark > Version: 3.1.4+ds1-1 > Severity: serious > Tags: ftbfs > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/shark.html > > ... > 57/160 Test #67: Trainers_MissingFeatureSvmTrainer ***Failed

Bug#888733: hyantesite FTBFS on most architectures: test failures

2019-02-20 Thread Thierry fa...@linux.ibm.com
On Mon, 29 Jan 2018 11:47:06 +0200 Adrian Bunk wrote: > Source: hyantesite > Version: 1.3.0-2 > Severity: serious > > hyantesite FTBFS on most architectures with varying test failures: > > https://buildd.debian.org/status/package.php?p=hyantesite > > Since the tests are failing because

Bug#917644: FTBFS: segmentation faults in test suite

2019-02-20 Thread Thierry fa...@linux.ibm.com
On Tue, 19 Feb 2019 16:50:00 +0100 "Thierry fa...@linux.ibm.com" wrote: > On Mon, 7 Jan 2019 16:49:41 + Steve McIntyre wrote: > > Hi Matthew, > > > > On Sun, Dec 30, 2018 at 05:38:57PM -0500, Matthew Fluet wrote: > > >If it is just the `

Bug#917644: FTBFS: segmentation faults in test suite

2019-02-19 Thread Thierry fa...@linux.ibm.com
On Mon, 7 Jan 2019 16:49:41 + Steve McIntyre wrote: > Hi Matthew, > > On Sun, Dec 30, 2018 at 05:38:57PM -0500, Matthew Fluet wrote: > >If it is just the `world` regression tests that are failing, then it > >is almost certainly due to save/restore world being incompatible with > >ASLR; see

Bug#922698: kcov: FTBFS on sid : error: 'SIGUNUSED' was not declared in this scope

2019-02-19 Thread Thierry fa...@linux.ibm.com
Package: kcov Version: 25+dfsg-1 Severity: serious Tags: sid buster Compilation usually fails with messages cd /<>/kcov-25+dfsg/obj-i686-linux-gnu/src && /usr/bin/c++ -I/<>/kcov-25+dfsg/src/include -I/usr/include/i386-linux-gnu -std=c++0x -g -Wall -D_GLIBCXX_USE_NANOSLEEP

Bug#870051: qile FTBFS: test_thermalsensor_regex_compatibility failure

2019-02-18 Thread Thierry fa...@linux.ibm.com
Hello, Just wondering why this test seem to have passed in 0.10.6-3 (sid) and not any more ? As this test is failing on most arch, shouldn't we disable it ? Thanks On Sat, 29 Jul 2017 12:43:02 +0300 Adrian Bunk wrote: > Source: qtile > Version: 0.10.7-2 > Severity: serious > >

Bug#853443: hidrd: ftbfs with GCC-7

2019-02-15 Thread Thierry fa...@linux.ibm.com
On Mon, 4 Dec 2017 12:50:24 +0200 Juhani Numminen wrote: > Control: tags -1 patch fixed-upstream > > On Mon, 4 Dec 2017 10:23:34 +0200 Juhani Numminen > wrote: > > Upstream has committed some GCC-7-related fixes. > > https://github.com/DIGImend/hidrd/commit/7e94881 > >

Bug#919189: Fwd: probabel FTBFS on arm64, likely due to Eigen 3 NEON code

2019-02-02 Thread Thierry fa...@linux.ibm.com
Did ppc64el compiled fine for version > 0.5.0+dfsg-1 (without that fix)? > > Kind regards > > Andreas. > > On Fri, Feb 01, 2019 at 04:41:04PM +0100, Thierry fa...@linux.ibm.com wrote: >> Unfortunately the workaround mentioned for arm64 breaks ppc64el arch as >> co

Bug#919189: Fwd: probabel FTBFS on arm64, likely due to Eigen 3 NEON code

2019-02-01 Thread Thierry fa...@linux.ibm.com
Unfortunately the workaround mentioned for arm64 breaks ppc64el arch as compiling on buster fails with following error - what do we do ? Thanks BT check (recess model): prob vs. prob_fv OK 2c2