Bug#746085: patch

Hi, same on ppc64el. The failing command is : pkg-config --atleast-version=2.99.3 gtk+-3.0 gthread-2.0 Checking the configure.ac on upstream ardesia, they changed it to remove gthread-2.0 which fixes the issue Here is the patch from upstream. F. --- ardesia-1.1.orig/configure.ac +++

Bug#728955: libatomic-ops: patch from Ubuntu

Package: libatomic-ops Version: 7.4.2-1 Followup-For: Bug #728955 User: debian-powe...@lists.debian.org Usertags: ppc64el Dear Maintainer, the same problem occurs on ppc64el and here is a patch that provides : - a fix from Ubuntu - support for quilt patches with debian/source/format Hope that

Bug#865132: some analysis

Hi, the main problem here is that on ppc64el optimization (>= O2) seems to make the symbol disappear : $ nm ./obj-powerpc64le-linux-gnu/CMakeFiles/diamond.dir/src/dp/needleman_wunsch.cpp.o|c++filt |grep needle 1b50 T needleman_wunsch(sequence, sequence, int, int, int, int, unsigned

Bug#865776: Let cmake go on for ppc64el

Hi, I just added ppc64el in the list of supported archs in CMakeLists.txt : --- hardinfo-0.5.1+git20170620.orig/CMakeLists.txt 2017-06-21 17:34:54.0 + +++ hardinfo-0.5.1+git20170620/CMakeLists.txt 2017-06-29 07:54:40.606721876 + @@ -21,7 +21,7 @@ set(HARDINFO_ARCH "x86")

Bug#873341: Any news for this issue?

Hi Andreas/all, I'm still out of time at the moment on the sbt front. The new packaging way I was investigating is idle at the moment. The other way I was thinking of is to push things in non-free, but then I'm not sure we could drag things back in main and also I think people relying on sbt

Bug#873341: Scala Build Tool (sbt) status ?

Hi Adam, sbt packaging is not yet ready. That last piece i.e. "scala-tools-sbinary" package was refused by ftpmasters. That outlined several weaknesses in the way I did the packaging for the components I pushed in experimental, and I'm not sure at this point, if I want to pursue the packaging this

Bug#899395: [PATCH] mono: FTBFS on various architectures

Tags: patch pending Dear maintainer, a similar bug was fixed on redhat/fedora ( https://bugzilla5.redhat.com/show_bug.cgi?id=1484149 ) : --- * Wed Sep 20 2017 Than Ngo - 4.8.0-12 - fixed the build failure on s390x/ppc64/ppc64le/aarch64 against new glibc which drops the tag struct ucontext

Bug#903195: libsass-python FTBFS with new libsass

Thanks Peter for letting know about that! I prepared an upload to fix this with a libsass-python in sync with libsass 3.5.4 . F. On Sat, 7 Jul 2018 12:49:41 +0100, peter green wrote: > Package: libsass-python > Severity: serious > Version: 0.13.4-1 > > A new version of libsass was recently

Bug#892108: Patch for several FTBFS

on ppc64, ppc64el, arm64 and re-enable mips64el + + -- Frédéric Bonnard <fre...@debian.org> Wed, 07 Mar 2018 19:06:24 +0100 + nim (0.18.0-1) unstable; urgency=medium * New upstream release diff -Nru nim-0.18.0/debian/control nim-0.18.0/debian/control --- nim-0.18.0/debian/control 2018-03-03

Bug#889877: Not reproduceable

Hi, it seems that we can't reproduce this bug anymore as golang went from 1.9 to 1.10 now. Well, it fails on another issue on ppc64el, but it seems to be the same on amd64 . Should we close that bug ? F. pgpzgP_flZJ8n.pgp Description: PGP signature

Bug#893442: lynkeos.app: FTBFS on ppc64el: AltiVec argument passed to unprototyped function

Hi Yavor, On Thu, 22 Mar 2018 12:04:33 +0200, Yavor Doganov <ya...@gnu.org> wrote: > Frédéric Bonnard wrote: > > I'm not an altivec expert but I was interested to look into this and > > maybe help. > > Many thanks for taking the time and effort, this is exactly

Bug#893442: lynkeos.app: FTBFS on ppc64el: AltiVec argument passed to unprototyped function

Hi Yavor, thanks for already digging into this issue. I'm not an altivec expert but I was interested to look into this and maybe help. On Sun, 18 Mar 2018 22:33:16 +0200, Yavor Doganov wrote: > Source: lynkeos.app > Version: 2.10+dfsg1-2 > Severity: serious > Tags: patch > User:

Bug#891249: linux: unstable kernel/data corruption on ppc64el

and I could do some heavy linux compilation without issue. The latest upstream 4.9.84 has that fix. F. On Mon, 26 Feb 2018 12:33:56 +0100, Frédéric Bonnard <fre...@debian.org> wrote: > Hi, > I got this as well, not immediatly though but adding some > parallelization to the build he

Bug#891249: linux: unstable kernel/data corruption on ppc64el

Hi, I got this as well, not immediatly though but adding some parallelization to the build helped. I'll look into this as well. F. On Fri, 23 Feb 2018 19:52:35 +0100, Aurelien Jarno wrote: > Source: linux > Version: 4.9.82-1+deb9u2 > Severity: critical > Justification:

Bug#895723: Patch

Tags: patch pending User: debian-powe...@lists.debian.org Usertags: ppc64el -- Hi, I noticed that the link failure does not happen when not using --release with cargo. Playing a bit with cargo's dev and release profile (

Bug#909442: outguess: patch for #909442

Tags: patch pending -- Hi, it seems there's a race condition that happens when trying to build libjpeg.a in directory jpeg-6b-steg (seen with make -j8). libjpeg.a: ansi2knr $(LIBOBJECTS) launches both compilation of ansi2knr and $(LIBOBJECTS) but the latter needs ansi2knr before it's compiled.

Bug#909442: outguess: patch for #909442

on amd64 and power arches. F. On Tue, 30 Oct 2018 22:41:11 -0300, Eriberto wrote: > Em ter, 30 de out de 2018 às 13:03, Frédéric Bonnard > escreveu: > > > > Tags: patch pending > > > > -- > > > > Hi, > > > > it seems there's a race con

Bug#909442: outguess: patch for #909442

as it worked well on arm64 and all other archs already built in knr style and it should work in ansi too. F. On Fri, 2 Nov 2018 19:43:20 -0300, Eriberto wrote: > Em qua, 31 de out de 2018 às 06:33, Frédéric Bonnard > escreveu: > > > > Hi Eriberto, > > > > the errors yo

Bug#911763: [Debichem-devel] Bug#911763: Patch

ot; wrote: > Hi Frédéric, > > On Wed, Oct 24, 2018 at 04:47:22PM +0200, Frédéric Bonnard wrote: > >> here is a merge request for the patch I did : >> >> https://salsa.debian.org/debichem-team/espresso/merge_requests/1 > > Are you interested in helping

Bug#857299: Package builds again

Hi Helmut, does this bug still appear for rebootstrap ? How can I simply reproduce it within rebootstrap ? Building inside sbuild works. F. pgp8Kk03uKkWZ.pgp Description: PGP signature

Bug#863511: Build now works

Hi, I saw that the build for version 0.39 now works : https://buildd.debian.org/status/fetch.php?pkg=numba=ppc64el=0.39.0-1=1533813201=0 Probably because llvm6.0 is now at level 6.0.1-2 . So I guess the bug can be closed in next Debian release. F. pgppaqhRkbxBL.pgp Description: PGP signature

Bug#870267: #870267 : still relevant ?

Wed, Mar 20, 2019 at 4:03 PM Frédéric Bonnard wrote: > > is this bug still relevant ? > It was never a bug in GraphicsMagick, see the discussion starting > about it[1]. A buildd admin later confirmed it's (it was) a bug on > their side only with the ppc64el-unicamp-01 b

Bug#870267: #870267 : still relevant ?

Hi, is this bug still relevant ? Version 1.3.26 is not used anymore and I didn't see this happening since a long time in all the builds since then (including on the ppc64el-unicamp-01 builder) : : https://buildd.debian.org/status/logs.php?pkg=graphicsmagick Furthermore, this bug is RC, so may we

Bug#919481: Fix for RC #919481

eparator" which, in this case, is a non-breaking space. This string is compared to the hardcoded expected result which contains a standard space (UTF8 hex. 20) As the file is UTF8, this patch replace the bad space with the UTF8 non-breaking space equivalent hex. C2 A0 . Author: Frédéric Bonnard -

Bug#919481: Fix for RC #919481

Package: src:guile-2.0 Version: 2.0.13+1-5 Control: tags -1 patch pending -- I forgot to mention, the issue now appears because schroots seem to have all locale created which was not the case before and the tests were just skipped as UNRESOLVED (see the build log history). Now they run.. and

Bug#923592: also break in Buster

to be put in debian/patches Regards, F. Description: Fix FTBFS due to missing comment/description After that commit https://phabricator.kde.org/D16867, a description is needed in .desktop files. The keyword actually looked for by desktoptojson converter utility is "Comment=" . Author

Bug#925831: Fixed : skiboot: ftbfs with GCC-9

Hi Matthias, new upstream skiboot 6.5 fixed that bug and I released a package of it : https://buildd.debian.org/status/fetch.php?pkg=skiboot=amd64=6.5-1=1566396860=0 > Please keep the issue open until the package can be built in > a follow-up test rebuild. Is the previous buildd build enough or

Bug#935289: quick checks and possible patch

Hi, from my tests the test works with gcc-8 and fails now with gcc-9. With gcc-9 and O1, the test passes and fails with O2. I expanded the options (c++ -S) added by O2 compared to O1 in gcc-9 to compile qd_test.cpp and got : -falign-functions -falign-jumps -falign-labels -falign-loops

Bug#942022: works with rustc 1.36

Hi, I see 2.44.14 which previously built, does not built in the very same build environment where 2.44.15 fails. Looking at the differences and trying downgrading some build deps, I found that replacing rustc 1.37 with 1.36 makes 2.44.14 and 2.44.15 build again in that latest schroot. Any idea

Bug#943602: os-autoinst : fix merge request

Dear maintainer, I submitted a merge request to fix that FTBFS : https://salsa.debian.org/debian/os-autoinst/merge_requests/1 Can you have a look at it ? Regards, F. pgphkIUpUl93j.pgp Description: PGP signature

Bug#952759: libsass-python 0.18.0 FTBFS with libsass 3.6.3, please upgrade to 0.19.4

Hi Anthony March 9, 2020 8:30 AM, "Anthony Fok" wrote: > Control: severity -1 serious > Control: tags -1 + ftbfs sid > Control: found -1 0.18.0-1 > > On Fri, 28 Feb 2020 17:38:13 +0100 Michael Fladischer > wrote: > >> Source: libsass-python >> Severity: wishlist >> >> -BEGIN PGP SIGNED

Bug#960354: ytcc: diff for NMU version 1.8.1-1.1

Hi Boyuan, thanks for the NMU, no problem with the delay. There's a new upstream release, but I won't package it right away. So all good! F. May 17, 2020 5:48 PM, "Boyuan Yang" wrote: > Control: tags 960354 + patch > Control: tags 960354 + pending > > Dear maintainer, > > I've prepared an

Bug#962402: haskell-text-icu built

Hi, I wanted to check that FTBFS but it actually built, on different setup. After a give back on ppc64el and s390x, everything went fine. Very few changes between the failing and succeeding build. Same ghc, kernel. For the record, linux-libc-dev, libgmpxx4ldbl, libgmp-dev, libkrb5support0,

Bug#976906: Possible lex issue for ppc64el (Was: Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

Here is a patch based on this : https://www.gnu.org/software/automake/manual/html_node/Yacc-and-Lex.html Tested on a power machine (where the build failed) and it seems to work. F. Description: Fix parallel build This happened here : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976906

Bug#980628: libsass-python FTBFS: possible issue in libsass_3.6.4+20201122-1

Control: forwarded -1 https://github.com/sass/libsass-python/issues/331 -- Hi, as build log shows, the very same version of libsass-python built successfully some time ago (using libsass_3.6.4-4) : https://buildd.debian.org/status/logs.php?pkg=libsass-python=amd64=sid but with latest build dep

Bug#979609: swt4-gtk segfaults on ppc64el

Hi there, I tried to bisect between 4.17.0 and 4.18.0 (4.19.0 didn't work either) and found the first offending commit 64ceb09e3297259b58a78b5d6486b1724070a4c9 that makes tracecompass fail and playing with -DNO_gtk_1check_1button_1set_1inconsistent makes it work. Soon after

Bug#977990: os-autoinst: FTBFS on i386: 3/3 Test #3: test-perl-testsuite ..............***Failed 332.81 sec

Hi, sorry for the delay. Initially I wanted to include all tests in the packaging as they just didn't fail for me on ppc64el, amd64 and i386. Having a look at the .spec file upstream, they skip some of the tests, amongst them, the one we have an issue with. --- # don't require qemu within OBS #

Bug#980628: libsass-python FTBFS: possible issue in libsass_3.6.4+20201122-1

Control: severity -1 important -- As explained upstream, the behaviour of the tests changed after libsass's commit "fix how we count unicode characters" that libsass_3.6.4+20201122-1 pulled. But upstream's libsass-python doesn't not support non-release of libsass and they wouldn't help on our

Bug#977990: os-autoinst: FTBFS on i386: 3/3 Test #3: test-perl-testsuite ..............***Failed 332.81 sec

Hi, indeed Paul, the test is flaky, probably a timing issue. I had already changed some related parameter that made the tests pass reliably on my i386 builder, but saw afterward that it still failed on debian's builder and couldn't reproduce it :

Bug#984097: closing 984097

close 984097 1.0.16-1 thanks

Bug#1004511: luajit SEGFAULTS on ppc64el

Hi Paul, sorry for the late reply. As I said on debian-devel, I've not enough expertise nor hope on that topic. Switching to lua is the way I went a few times, instead on relying on luajit. F. On Mon, 02 May 2022 07:55:50 +0200 Paul Gevers wrote: > Hi, > > On 24-04-2022 12:00, Paul Gevers

Bug#1012638: issue in rocksdb on ppc64

Control: reassign -1 rocksdb Hi, this is actually an issue in latest rocksdb 7.2.2-3 that got compiled with -mcpu=power9 -mtune=power9 which is not good in Debian, because we want to be power8 compatible (Debian's gcc defaults). (which is not the case in Ubuntu which optimize for Power9 and thus

Bug#1012638: Patch proposal

rent story, as it is enabled by default on ppc64el but not + on ppc64. So leaving it for now. +Author: Frédéric Bonnard +Forwarded: no +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/CMakeLists.txt b/CMakeLists.txt +@@ -203,17 +203,6 @@ + + include(CheckCCo