Bug#954312: systemd: FTBFS on riscv64: test-seccomp fails: Assertion 'name' failed at src/test/test-seccomp.c:49

Aurelien Jarno aurel32 at debian.org
Sat Apr 4 19:28:51 BST 2020


On 2020-04-02 12:10, Michael Biebl wrote:
> Control: retitle -1 Enable seccomp support on riscv64
> Control: severity -1 wishlist
> Hi Aurelien,
> I decided to disable seccomp support again for riscv64 for the time
> being. This will make backports easier.
> Once we have a libseccomp in stable which does have support for riscv64,
> I'll re-enable support for it (which means bullseye+1), I'll re-enable
> support. Retitling the bug report accordingly.

Thanks, that make sense and will avoid to have to clutter the upstream
patch with #ifdef. There is no urgency in getting libseccomp support on
in systemd for riscv64, my goal was mostly to fix the FTBFS. At least we
learned that it works, or rather that it is not completely broken.

> By then, we should have an official libseccomp release with riscv64
> support and your patch might have a chance to be applied upstream.

libseccomp releases are not really predictable, but it seems there are
currently people working towards a release, so it might happens in the
next months.


Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien at aurel32.net                 http://www.aurel32.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200404/c3a6bfa2/attachment-0001.sig>

More information about the Pkg-systemd-maintainers mailing list