[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#879814: apt: debian-installer FTBFS: missing syscalls for seccomp [mips,mipsel,ppc64el]



Hi,

On 26/10/17 10:53, Cyril Brulebois wrote:
> Package: apt
> Version: 1.6~alpha2
> Severity: serious
> Tags: d-i
> Justification: FTBFS
> 
> [ X-D-Cc: debian-boot@, debian-mips@, debian-powerpc@ ]
> 
> Hi,
> 
> Following the bump from alpha1 to alpha2, the situation improved quite a
> bit for the d-i daily builds (see #879662 for context). I've triggered a
> manual build for all archs, and if my copying/pasting is correct, the
> results are as follows:
> 
>     armel:    alpha2, OK
>     armhf:    alpha1, KO ← the apt alpha2 build came in late, wasn't available yet.
>     arm64:    alpha2, OK
>     amd64:    alpha2, OK
>     i386:     alpha2, OK
>     mips:     alpha2, **** Seccomp prevented execution of syscall 0000004117 on architecture mips ****
>     mipsel:   alpha2, **** Seccomp prevented execution of syscall 0000004117 on architecture mipsel ****
>     mips64el: alpha2, OK
>     powerpc:  alpha2, OK
>     ppc64el:  alpha2, **** Seccomp prevented execution of syscall 0000000117 on architecture ppc64el ****
>     s390x:    alpha2, OK

Syscall 4117 on 32-bit mips, and syscall 117 on ppc64el is the sysv IPC
syscall. On these architectures there is one syscall for all sysv IPC
instead of individual syscalls for each operation.

This is probably needed for fakeroot like the other syscalls in #879662.

James

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: