Bug#964613: liborcus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

2020-09-13 Thread Rene Engelhard
On Sun, Sep 13, 2020 at 11:44:59AM +0200, Rene Engelhard wrote: > Nevermind, I just remembered I have those "Debian Janitor" changes > pending. Will do a source upload. Done now. (And a new liborcus with bumped build-dep.) Regards, Rene

Bug#964613: liborcus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

2020-09-13 Thread Rene Engelhard
On Sun, Sep 13, 2020 at 10:36:26AM +0200, Rene Engelhard wrote: > @-release: please > > nmu libixion . ANY . -m 'rebuild with mdds >= 1.6.0 (closes: #964613)' Nevermind, I just remembered I have those "Debian Janitor" changes pending. Will do a source upload. Regards, Rene

Bug#964613: liborcus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

2020-09-13 Thread Rene Engelhard
Hi, I forwarded it upstream to https://gitlab.com/orcus/orcus/-/issues/124 and it seems that it does not fail if one rebuilds libixion first. So that means that this bug could be solved by bin-NMUing libxion. (mdds is header-only, and you would want to have some way of expressing "if orcus is

Bug#964613: liborcus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

2020-09-12 Thread Rene Engelhard
tag 964613 + pending retitle 964613 liborcus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 when built with mdds 1.6.0 thanks Hi, On Thu, Jul 16, 2020 at 10:08:30PM +0300, Dmitry Shachnev wrote: > On Thu, Jul 09, 2020 at 01:01:01PM +0200, Lucas Nussbaum wrote: > >

Bug#964613: liborcus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

2020-07-09 Thread Lucas Nussbaum
Source: liborcus Version: 0.15.4-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200709 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[6]: Entering directory