Bug#800112: "Unsupported socketcall: 20" when using apt-get under s390 chroot

2015-12-02 Thread John Paul Adrian Glaubitz
On 12/02/2015 02:46 PM, John Paul Adrian Glaubitz wrote: > Interestingly, we're seeing the same warning on qemu-m68k [1], more > specifically in Laurent Vivier's fork which adds full m68k support > to qemu which normally supports the reduced ColdFire instruction > set only: Oops, forgot the link:

Bug#800112: "Unsupported socketcall: 20" when using apt-get under s390 chroot

2015-12-02 Thread John Paul Adrian Glaubitz
Hi Jeff! Interestingly, we're seeing the same warning on qemu-m68k [1], more specifically in Laurent Vivier's fork which adds full m68k support to qemu which normally supports the reduced ColdFire instruction set only: Download source files with APT ── Reading package

Bug#800112: "Unsupported socketcall: 20" when using apt-get under s390 chroot

2015-10-02 Thread Jeffrey Walton
Hi David, Sorry about the late reply. I just got back on testing that utilizes the Debian QEMU chroot's. Also note that this might be better assigned to qemu-user static (my apologies if it was mis-classified): $ sudo update-binfmts --display ... interpreter = /usr/bin/qemu-s390x-s

Bug#800112: "Unsupported socketcall: 20" when using apt-get under s390 chroot

2015-09-28 Thread Jeffrey Walton
>> 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?) > > Yes, its a chroot

Bug#800112: "Unsupported socketcall: 20" when using apt-get under s390 chroot

2015-09-28 Thread Jeffrey Walton
On Mon, Sep 28, 2015 at 4:58 PM, David Kalnischkies wrote: > 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://http

Bug#800112: "Unsupported socketcall: 20" when using apt-get under s390 chroot

2015-09-28 Thread David Kalnischkies
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://httpr

Bug#800112: "Unsupported socketcall: 20" when using apt-get under s390 chroot

2015-09-28 Thread Andrei POPESCU
Control: reassign -1 apt 1.0.10.2 On Sb, 26 sep 15, 19:21:28, Jeffrey Walton wrote: > Package: apt-get > Version: 1.0.10.2 > Severity: normal > > X-Debbugs-CC: m...@tls.msk.ru > > ** > > # chroot debian-s390x/ > debian-s390:/# apt-get update > 0% [Working]Unsupported socketcall: 20 > 0%

Bug#800112: "Unsupported socketcall: 20" when using apt-get under s390 chroot

2015-09-26 Thread Jeffrey Walton
Package: apt-get Version: 1.0.10.2 Severity: normal X-Debbugs-CC: m...@tls.msk.ru ** # 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