Bug#921527: cuneiform_1.1.0+dfsg-7 - FTBFS on ppc64el

Package: *cuneiform* Version: *1.1.0+dfsg-7* Severity: important Tags: patch Compile fails with CF_DATADIR=/<>/cuneiform-1.1.0+dfsg/datafiles/ debian/tests/ground-truth obj/cuneiform images/phototest.tif ... FAIL --- images/phototest.tif.txt2011-04-19 12:49:57.0 + +++ /tmp/cuneif

Bug#921629: zeroc-ice - FTBFS on ppc64el

Package: *zeroc-ice* Version: 3.7.2-2 Severity: normal Tags: patch Currently build on ppc64el fails with src/Ice/Network.cpp:451:17: error: declaration of ‘i’ shadows a previous local [-Werror=shadow]     for(int i = 0; i < numaddrs; ++i) ^ src/Ice/Network.cpp:395:13: note:

Bug#921527: cuneiform_1.1.0+dfsg-7 - FTBFS on ppc64el

d therefore not RC. > > On Wed, 6 Feb 2019 14:50:47 +0100 "Thierry fa...@linux.ibm.com" > wrote: >> --- images/phototest.tif.txt 2011-04-19 12:49:57.0 + >> +++ /tmp/cuneiform.test.KgXcP8dD/phototest.tif.out 2018-01-14 >> 03:21:46.536688277 + &

Bug#921724: FTBFS - gcc-m68hc1x doesn't compile on ppc64el

Package: gcc-m68hc1x Version: 1:3.3.6+3.1+dfsg-3+b2 Severity: normal With version 1:3.3.6+3.1+dfsg-3+b2

Bug#922116: tulip - FTBFS - error: there are no arguments to 'memcpy' that depend on a template parameter

Package: tulip Version: *4.8**.0+dfsg-7*10 Severity: important Tags: patch Hello, There is a regression on all platforms for tulip version from 4.8.0dfsg-2+b7  to current (4.8.0dfsg-2+b10 ) The error message is *  error: there are no arguments to 'memcpy' that depend on a template parameter

Bug#922238: rkt: FTBFS on ppc64el - missing function body

Package: *rkt* Version: 1.30.0+dfsg-7 Severity: normal Hello, Currently the ppc64el of rkt on sid fails with following error. ls /<>/rkt-1.30.0+dfsg/_build/src/github.com/rkt/rkt/build-rkt-1.30.0/gopath/src/github.com/rkt/rkt/rkt/*.go | \ grep -vE '_test.go|main.go|_gen.go|_stub.go' | \

Bug#922317: FTBFS - rspamd on ppc64el fails with many errors

Package: rspamd Version: 1.8.1-2 Severity: important Hello, Current build of rspamd on ppc64el fails with messages Run Build Command:"/usr/bin/make" "cmTC_35eec/fast" make[2]: Entering directory '/<>/obj-powerpc64le-linux-gnu/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_35e

Bug#922394: cadvisor - FTBFS - missing package golang.org/x/exp/inotify

Package: cadvisor Version: 0.27.1+dfsg2-4+b10 Severity: important Hello, With this version all arch compilation fails with the error: make[1]: Leaving directory '/<>/cadvisor-0.27.1+dfsg2' dh_auto_build -a -O--buildsystem=golang -O--builddirectory=_build cd _build && go install -gcfl

Bug#922399: isospec : FTBS - -march=native parameter invalid

Package: isospec Version: 1.9.1-2 Severity: important Tag: patch Hello, Current build fails on couple of platforms because  make[2]: Entering directory '/<>/IsoSpec++' g++ -std=c++11 -O0 -g -Wall -pedantic -Wextra -O3 -march=native -mtune=native unity-build.cpp -fPIC -shared -o libIsoSpec++.so

Bug#853443: hidrd: ftbfs with GCC-7

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 > > https://github.com/DIGIme

Bug#922405: pocl : FTBFS on sid - testsuite has failed on ppc64el arch

Package: pocl Version: 1.2-5 Severity: important Hello, Most of the tests fail on ppc64el arch The following tests FAILED:       3 - kernel/test_convert_type_1 (Failed)       4 - kernel/test_convert_type_2 (Failed)       5 - kernel/test_convert_type_4 (Failed)       6 - kernel/test_convert_type_

Bug#922619: mame: FTBFS of version 0.206+dfsg.1-1 on arch ppc64el

Package: mame Version: 0.206+dfsg.1-1 Severity: important Hello, Since version 0.194 (and even earlier) ppc64el compil fails with messages: In file included from ../../../../../src/emu/emu.h:31: ../../../../../src/mame/drivers/flyball.cpp:27:39: in 'constexpr' expansion of 'operator""_MHz_XT

Bug#922620: minimap2: FTBFS on pppc64el - unknown line option '-msse2';

Package: minimap2 Version: 2.15+dfsg-1 Severity: important Hello, Compilation on ppc64el arch fails with message cc -c -g -O2 -fdebug-prefix-map=/<>/minimap2-2.15+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -g -Wall -O2 -Wc++-compat -msse2 -Wdate-time -D_FORTIFY_SOURCE=2

Bug#870051: qile FTBFS: test_thermalsensor_regex_compatibility failure

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 > > https://buildd.de

Bug#922685: octave-tisean FTBFS on ppc64el : mutual.cc test failure

Source: octave-tisean Version: 0.2.3-3 Severity: important https://buildd.debian.org/status/fetch.php?pkg=octave-tisean&arch=ppc64el&ver=0.2.3-3&stamp=1518318632&raw=0 [mutual.cc] > /<>/src/mutual.cc * fail("mutual((1:10),0)"); * fail("mutual((1:10),-4,5)"); * fail("mutual([(1:10)

Bug#922692: galax: FTBFS on ppc64el - ERROR: unable to find camomileLibrary.cmi in /usr/lib/ocaml/camomile

Package: galax Version: 1.1-15 Severity: important Compilation on ppc64el fails with the message ERROR: unable to find camomileLibrary.cmi in /usr/lib/ocaml/camomile However package libcamomile-ocaml-dev contains /usr/lib/ocaml/camomile/*library*/camomileLibrary.cmi on buster. and this pack

Bug#922696: alljoyn-services-1604: FTBFS on sid - build_core/SConscript doesn't allow some linux arch

Package: alljoyn-services-1604 Version: 16.04-5 Severity: important Tags: sid buster Most of the compilation fail with an error similar to mkdir -p /<>/build/linux/powerpc64le/release/dist (cd sample_apps; \ scons BINDINGS=cpp CPU=powerpc64le OS=linux VARIANT=release V=1 GTEST_DIR=/usr/src/gtest

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

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

Bug#917644: FTBFS: segmentation faults in test suite

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 ht

Bug#922767: libemf : FTBFS - mv: cannot stat 'refman.pdf': No such file or directory -

Package: libemf Version: 1.0.11-2 Severity: important Tags: sid buster Current compilation fails with message /This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex) restricted \write18 enabled. entering extended mode (./refman.tex LaTeX2e <2018-12-0

Bug#917644: FTBFS: segmentation faults in test suite

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 `world` re

Bug#922768: haskell-secret-sharing : FTBFS on sid - src/Crypto/SecretSharing/Internal.hs:129:39: error:

Package: haskell-secret-sharing Version: 1.0.0.3-5 Severity: important Tags: sid buster Compilation fails with messages Building test suite 'Main' for secret-sharing-1.0.0.3.. : warning: [-Wmissing-home-modules] These modules are needed for compilation but not listed in your .cabal file's o

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

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 (appare

Bug#922776: libhmsbeagle : FTBFS on ppc64el - cannot convert ‘bool’ to ‘__vector(4) __bool int’ in assignment

Package: libhmsbeagle Version: 3.1.2+dfsg-3 Severity: important Tags: sid buster ppc64el Hello, Compilation on ppc64el fails with following message Apparently this is a known issue mentioned in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58241 I have tested that cusing -std=gnu+11 get rid of t

Bug#922778: libhmsbeagle: FTBFS - find: ‘debian/libhmsbeagle1v5’: No such file or directory

Package: libhmsbeagle Version: 3.1.2+dfsg-3 Severity: important Tags: sid buster Hi, Compilation on couple of systems fails with message dh_install cp --reflink=auto -a debian/tmp/usr/include/libhmsbeagle-1 debian/libhmsbeagle-dev//usr/include/ install -d debian/libhmsbeagle-dev

Bug#922782: dub : FTBFS - gdc : cc1d: warning: command line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for D

Package: dub Version: 1.12.1-160d Severity: important Tags: sid buster Hi, Compilation on couple of arch fails with  Generating version file for 1.12.1-1... Running gdc... + gdc -Wall -obin/dub -fversion=DubUseCurl -Isource -Wl,--push-state,--no-as-needed -lcurl -lz -Wl,--pop-state -g -O2 -f

Bug#909861: shark FTBFS on i386 with gcc 8

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#844778: clsync FTBFS on !x86: error: '__NR_select' undeclared here

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&suite=sid > > ... > In file included from privileged.c:64:0: > privileged.c:88:34: error: '__NR_select' undeclared here (not in

Bug#922782: dub : FTBFS - gdc : cc1d: warning: command line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for D

Hi, Thanks for the explanation. As far as I understand gdc will be part of GCC 9  so you are right , today seems a bit early. On 20/02/2019 19:36, Matthias Klumpp wrote: > Am Mi., 20. Feb. 2019 um 16:51 Uhr schrieb Thierry fa...@linux.ibm.com > : >> Package: dub >> Ve

Bug#922776: libhmsbeagle : FTBFS on ppc64el - cannot convert ‘bool’ to ‘__vector?=(4) bool =?UTF-8?Q?int’ in assignment

ille wrote: > Control: tags -1 help moreinfo > > Hi Thierry, > > thanks for your bug report. > > On Wed, Feb 20, 2019 at 03:46:51PM +0100, Thierry fa...@linux.ibm.com wrote: >> Package: libhmsbeagle >> Version: 3.1.2+dfsg-3 >> Severity: important >> Tags:

Bug#923255: highwayhash: FTBFS on ppc64el due to an entry in debian/libhighwayhash0.symbols.ppc64el

Package: highwayhash Version: 0~git20190222.276dd7b Severity: important Tags: sid buster Hello, On ppc64el compilation fails with following messagesdpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libhighwayh

Bug#926843: debci - environment.sh should point to /usr/share/debci if debci_base_dir not set

Package: debci Version: 2.0 Severity: normal Tags: buster debci Currently default basedir for debci is /usr/share/debci. But environment.sh doesn't handle that path by default and reports 'E: no \$debci_base_dir not set!'. Shouldn't we use the following code instead of the current one relativ

Bug#926945: autopkgtest - autopkgtest-build-qemu on ppc64el

Package: autopkgtest Version: 5.10 Severity: important Tag: autopkgtest qemu patch buster vmdb2 Usertags: ppc64el While using debci, create-tesbed command for backends/qemu launches    autopkgtest-build-qemu unstable /var/lib/debci/qemu/unstable-ppc64el.img http://deb.debian.org/debia

Bug#983843: xrdp FTBFS on several architectures

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 < (define

Bug#933485: auto-multiple-choice - ppc64el - make manual-test hangs

Package: auto-multiple-choice Version: 1.4.0-1 $ make manual-test make -C tests test make[1]: Entering directory '/home/debian/auto-multiple-choice-1.4.0/tests' Using qpdf ./all_tests [ OK ] t/glade-objects-id/test.sh [ OK ] t/standard-directory-name/test.sh hangs for 3 hours on ppc64el

Bug#933505: bamtools - ppc64el -run-unit-test hangs

Package: bamtools Version: 2.5.1+dfsg-3 bamtools-2.5.1+dfsg/debian/tests$ sh run-unit-test 6 _debci reports_ bamtools 2.5.1+dfsg-3 stable

Bug#933506: Fwd: Re: boost1.67- ppc64el -autopkgtest hangs

Package: boost1.67 Version: 1.67.0-13 debci tests hangs for a while when on intel it pass in 30mn. boost1.67 1.67.0-13 stable

Bug#933505: bamtools - ppc64el -run-unit-test hangs

On 7/31/19 3:29 PM, Andreas Tille wrote: > Hi Roger, > > On Wed, Jul 31, 2019 at 12:55:23PM +0200, Roger wrote: >> I have investigated more - the failing test is >> bamtools filter -script tests/filter_script -in sam_spec_example.bam >> -out out.bam > Thanks a lot for your investigation. Do you th

Bug#933506: Fwd: Re: boost1.67- ppc64el -autopkgtest hangs

On 7/31/19 3:57 PM, Giovanni Mascellani wrote: > Hi, > > Il 30/07/19 18:55, Thierry fa...@linux.ibm.com ha scritto: >> Package: boost1.67 >> Version: 1.67.0-13 >> >> debci tests hangs for a while when on intel it pass in 30mn. >> boost1.67 <http://9.101

Bug#944222: acl2 - FTBFS on ppc64el - invalid Unknown reloc type 31

Source: acl2 Version: 8.1dfsg-4 Tags: patch, acl2 FTBFS fails with following message: OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0, Speed=3 Finished compiling /<>/acl2-fns.o. ;; Loading #p"acl2-fns.o" Unknown reloc type 31 This has been already identified in bug #942312 for gc

Bug#926843: debci - environment.sh should point to /usr/share/debci if debci_base_dir not set

On Fri, 19 Apr 2019 11:31:35 +0200 "Thierry fa...@linux.ibm.com" wrote: > Hello, > > Here is a patch for a more complete set of changes. > Regards > Hi, Please discard my previous patch as it was solving issues running directly the debci-* commands - I understand a

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

Package: 3depict Version 0.0.22-1 Severity: normal The error when compiling on ppc64el: g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/freetype2 -I/usr/include/libpng16 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security --s

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

Changing on file side is not enough as there a couple of file impacted > g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/freetype2 -I/usr/include/libpng16 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security --std=gnu++11 -I/u

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

Source: tcpdump Version: 4.9.3-1 Severity: serious https://buildd.debian.org/status/logs.php?pkg=tcpdump&arch=ppc64el&suite=sid --- 1 tests failed 441 tests passed Failed test: ikev2pI2 41c41 < (v2auth: len=196 method=rsasig authdata=(000

Bug#942183: Fwd: memcached : FTBFS on ppc64el - missing ss command

Source: memcached Version: 1.5.19-1 autopkgtest fails on ppc64el with message ss not found. This command coming from package iproute2, I believe it is a missing dependency.

Bug#942312: gcl - FTBFS on ppc64el - invalid relocation type 31

Source: gcl Version: 2.6.12-88 Tags: patch Compilation fails with ;; Loading "../tkl.o" Unknown reloc type 31 The relocation type 31 == R_PPC64_PLT16_HA and apparently it is not yet handled. Similar issue have been found on Fedora  https://lists.gnu.org/archive/html/gcl-devel/2019-07/msg0

Bug#942312: gcl - FTBFS on ppc64el - invalid relocation type 31

On Mon, 14 Oct 2019 15:21:07 +0200 "Thierry fa...@linux.ibm.com" wrote: Source: gcl Version: 2.6.12-88 Tags: patch Compilation fails with >;; Loading "../tkl.o" Unknown reloc type 31 The relocation type 31 == R_PPC64_PLT16_HA and apparently it is not yet handled.

Bug#942432: sagemath FTBFS on ppc64el

Package: sagemath Version: 8.9-1 Severity: high Tests are failing due to programation errors * may be GCC 9 is less permissive * may be default library don't include objects with expected definition but result is a strange message                 Success: 38 tests failed, up to 65 failures a

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

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 s/__POWERPC__/__pow

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

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

Bug#940828: octave-video - FTBFS on ppc64el - AVHandler: Error reading packet after timestamp 0 - knwon failure !

Package: octave-video Version:*1.2.4-1* Severity: important [src/aviread.cc] /home/debian/octave-video-1.2.4/src/aviread.cc * demo * test fn = tmpnam; x = avifile(fn); # Generate some picture I = repmat(0:255, 256, 1)/255; I = cat(3, I, repmat([0:255]', 1, 256)/255); I = cat(3, I

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

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#926945: autopkgtest - autopkgtest-build-qemu on ppc64el

Regarding that issue I have provided 2 patches (copied for reference) - one for vmdb2 (pushed to salsa)) - create a new command called set to set the Prep Flag to the first partition for GRUB2 purpose. - Calls GRUB2 with target powerpc-ieee1275 for arch ppc64el (instead of grub-pc/

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

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 /dev/dev/s

Bug#921527: cuneiform_1.1.0+dfsg-7 - FTBFS on ppc64el

The problem reported was fixed for some arch in version 1.1.0+dfsg-6 but apparently it is not universal. The main question is is the 'Architecture: any all' appropriate ? since readme says >Caveats >There are known limitations in this port. Among these are the following: >- it on

Bug#921099: cpufreqd-2.4.2 on pcc64el doesn't compile

Package: cpufreqd Version: 2.4.2 Severity: important Tags: patch Following bug #889895 - disable building this package for Power architectures cpufrequtils package providing libcpufreq0 is not any more compiled. As such line 41-43 of configure.in are not any more valid and prevent package compila

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

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 <

Bug#862771: sciplot FTBFS on ppc64{,el}: ld: unrecognised emulation mode: minimal-toc

On Tue, 16 May 2017 22:37:53 +0300 Adrian Bunk wrote: > Source: sciplot > Version: 1.36-16 > Severity: important > > https://buildd.debian.org/status/package.php?p=sciplot&suite=sid > > ... > ld -shared -o libsciplot.so.1.36 SciPlot.o SciPlotUtil.o -mminimal-toc > -lXm -lXmu -lXt -lSM

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

c64el. 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 &

Bug#926843: debci - environment.sh should point to /usr/share/debci if debci_base_dir not set

Hello, Here is a patch for a more complete set of changes. Regards >From 4693317d5eef79acd5d36e0c7f99d76c70b6e6d5 Mon Sep 17 00:00:00 2001 From: Thierry Fauck Date: Fri, 19 Apr 2019 11:20:40 +0200 Subject: [PATCH] Work on multiple scripts related to #926843 Signed-off-by: Thierry Fauck --- ba

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

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 sens

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

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, 8

Bug#876905: qtwebkit should not be release with buster

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 do

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

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 fon

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

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#810985: Patch

Hello, As the fix for ppc64el is simple, couldn't it be integrated ... or definitely no interest ?! Thanks On Thu, 21 Sep 2017 15:51:56 +0200 =?UTF-8?B?RnLDqWTDqXJpYw==?= Bonnard wrote: > Hi, > the message "dlopen of .../pl-tai.so failed with error libplstream.so: > cannot open shared object f