13.04.2020 20:55, Tom Turelinckx wrote:
> Instead of enabling seccomp on linux-any, maybe it could be enabled on
> something like this:
>
> [!alpha !ia64 !m68k !sh4 !sparc64 !hurd-any !kfreebsd-any]
Uh.. :) We use another simple "parser" for --enable-foo which
goes parallel with this Build-Dep
> Commit 63f51933 resolved bug #900055 by enabling seccomp on linux-any.
>
> Since version 1:2.12+dfsg-2 qemu FTBFS due to this dependency, while it was
> building successfully before:
>
> https://buildd.debian.org/status/logs.php?pkg=qemu&arch=sparc64
>
> Instead of enabling seccomp on linux-a
13.04.2020 20:55, Tom Turelinckx wrote:
> Source: qemu
> Severity: normal
> User: debian-sp...@lists.debian.org
> Usertags: sparc64
>
> Hello,
>
> Commit 63f51933 resolved bug #900055 by enabling seccomp on linux-any.
>
> Since version 1:2.12+dfsg-2 qemu FTBFS due to this dependency, while it wa
Source: qemu
Severity: normal
User: debian-sp...@lists.debian.org
Usertags: sparc64
Hello,
Commit 63f51933 resolved bug #900055 by enabling seccomp on linux-any.
Since version 1:2.12+dfsg-2 qemu FTBFS due to this dependency, while it was
building successfully before:
https://buildd.debian.org/
4 matches
Mail list logo
