On Mon, Sep 28, 2015 at 10:12:30PM +0300, Andrei POPESCU wrote: > > # chroot debian-s390x/ > > debian-s390:/# apt-get update > > 0% [Working]Unsupported socketcall: 20 > > 0% [Working]Unsupported socketcall: 20 > > Get:1 http://httpredir.debian.org unstable InRelease [236 kB] > > Get:2 http://httpredir.debian.org unstable/main Translation-en/DiffIndex [926 B] > > Get:3 http://httpredir.debian.org unstable/main s390x Packages [7,305 kB] > > Get:4 http://httpredir.debian.org unstable/main Translation-en [5,087 kB] > > ... I assume we are talking about a foreign chroot setup with qemu rather than real hardware as I can't see such output in the buildlogs on real hardware, but some searching suggests that it happens in emulation. (In which case: which qemu setup and in which version?) May I further assume that appart from this message everything behaves as expected as you didn't mention anything failing in particular? Is this a new problem or did you just notice it now as I don't remember anything in particular changing recently in terms of sockets, so I would expect it to effect 'all' versions. It would be nice if you could provide a complete set of steps to reproduce this, preferably starting with the setup of the chroot itself. Best regards David Kalnischkies
Attachment:
signature.asc
Description: PGP signature