Thanks for the bug report! I think it might make sense to disable seccomp when building on that platform until the next upstream release. I've not had access to a mips64 box with seccomp - it may also be a trivial patch and I haven't had any time to look into this specific issue yet.
Could you give me an idea of the timeline within this should be resolved to make sure we can ship a seccomp enabled tlsdate for mips64? Does this happen on any other mips system? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
