Bug#1037851: (no subject)

Btw, why does this bug not appear when searching for bugs against the package? https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=rumur

Bug#1002186: rumur: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 check ARGS\+=--verbose ARGS\+=-j4 returned exit code 2

Thanks for reporting! It looks like there are now libc calls to `newfstatat` which is not in Rumur’s sandbox’s list of safe allowed syscalls. I’ll fix this upstream and then package a new release for Debian.

Bug#969156: rumur FTBFS on armel/armhf/mipsel/mips64el: test failures

Thanks for reporting this, Adrian. I noticed this some time after upload and fixed it upstream: https://github.com/Smattr/rumur/commit/68683c4742b380421936a703c4b9262dac1e68dc I hadn’t uploaded a fixed version to

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

> One small issue... Valgrind recommends -O0 or -O1 TIL :) Thanks, Jeff! > You can sometimes locate a bus error at build time with -Wcast-align. > At runtime you can usually locate them with -fsanitize=undefined. I had previously tried UBSan and, while it turned up a number of shifting and stri

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

> On Apr 30, 2020, at 00:31, Andreas Tille wrote: > > On Wed, Apr 29, 2020 at 05:51:26PM -0700, Matthew Fernandez wrote: > >> The other option I suggested was Valgrind, but if you can’t run apt-file you >> probably can’t install Valgrind either. > > Well, I

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

> On Apr 29, 2020, at 09:04, Andreas Tille wrote: > > On Wed, Apr 29, 2020 at 07:14:30AM -0700, Matthew Fernandez wrote: > >> For those on this thread who have access to mipsel hardware or can shell in >> to one of the mipsel build machines, I would suggest running

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

> On Apr 29, 2020, at 02:12, Andreas Tille wrote: > > Hi, > > On Wed, Apr 29, 2020 at 10:30:35AM +0800, 黄佳文 wrote: >> I am a developer from Loongson company (R & D CPU/mip64el), I've been >> looking at this recently. > > Very nice to see mips developers to care for biological software. :-) >

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

> On Apr 17, 2020, at 22:39, Andreas Tille wrote: > > Hi Matthew, > > thanks a lot for your detailed investigation. > > On Fri, Apr 17, 2020 at 04:28:23PM -0700, Matthew Fernandez wrote: >>> Program received signal SIGBUS, Bus error. >>> 0x5556a1b8 in

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

> On Apr 17, 2020, at 13:18, Andreas Tille wrote: > > Hi Matthew, > > On Fri, Apr 17, 2020 at 08:18:29AM -0700, Matthew Fernandez wrote: >>> Thanks for the patch which I applied to packaging Git. I assume you >>> want to express that while these fixes are de

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

On Fri, 17 Apr 2020 at 08:09, Andreas Tille wrote: > Hi Matthew, > > On Fri, Apr 17, 2020 at 07:40:54AM -0700, Matthew Fernandez wrote: > > > > As a jumping off point, the attached patch fixes some issues with > logging calls in the upstream 1.2.4 source release. > >

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

> On Apr 17, 2020, at 04:20, Andreas Tille wrote: > > Control: tags -1 help > > Hi, > > as it can be seen on the recent build log of clustalo on mips[1] the > build fails with > > > # Run additional test from python-biopython package to verify that > # this will work as well > src/clustalo -

Bug#949542: C++ help needed for pbdagcon

> On Jan 22, 2020, at 11:56, Andreas Tille wrote: > > Control: tags -1 help > > I have fixed Python2->Python3 migration as well as the FTBFS with > pbseqlib 5.3.3+dfsg-1 issue in Git[1]. Unfortunately there is another > build issue in the C++ code which I have no idea how to fix: > > > ... >

Bug#939506: expected primary-expression before ‘{’ token (Was: Bug#939506: unanimity ftbfs in unstable)

gt; On Wed, Jan 15, 2020 at 09:27:16AM +0100, Andreas Tille wrote: >> Hi Matthew, >> >> On Tue, Jan 14, 2020 at 07:00:02PM -0800, Matthew Fernandez wrote: >>> >>> Offhand I don’t know the fix to the error message you quoted, but I just >>> t

Bug#939506: expected primary-expression before ‘{’ token (Was: Bug#939506: unanimity ftbfs in unstable)

Hi Andreas, This is not related to aghermann, correct? Offhand I don’t know the fix to the error message you quoted, but I just tried to reproduce the build error on Debian 10.2. This repository has multiple build systems in the root directory and no build instructions in the README, so I guess

Bug#925629: aghermann: ftbfs with GCC-9

Thanks for being clear, Andrei. And thanks for your work building and maintaining this package. I jumped into this thread knowing nothing about this package but merely recognizing a compiler error. Now that I look up what it does, I don’t have the necessary background to fully understand its fu

Bug#925629: aghermann: ftbfs with GCC-9

Sorry, I didn’t have much context for the original issue and was probably too terse in my responses. Some more elaboration inline below. > On Jan 13, 2020, at 01:14, Andreas Tille wrote: > > On Sun, Jan 12, 2020 at 02:08:56PM -0800, Matthew Fernandez wrote: >> >>> O

Bug#925629: aghermann: ftbfs with GCC-9

> On Jan 12, 2020, at 12:49, Andreas Tille wrote: > > Hi, > > I'm wondering how this bug > > > rk1968/rk1968.cc: In lambda function: > rk1968/rk1968.cc:237:103: error: expected '{' before '->' token > 237 | auto make_error_return = [&L] ( const char* fmt, ...) > __attribute__ ((for