Re: sparc64 pbuilder/cowbuilder setup with qemu

2022-12-26 Thread John Paul Adrian Glaubitz
Hi Gregor! On 12/26/22 11:01, Gregor Riepl wrote: Since gcc102 is available right now, I tested the libnss build on that machine. libnspr4-dev isn't installed, but the build got sufficiently far to compare output with the Debian build machines. We should probably set up schroot on these

Re: sparc64 pbuilder/cowbuilder setup with qemu

2022-12-26 Thread Gregor Riepl
As I mentioned earlier in this thread, you can just configure apt to run as root to avoid this problem. Ah, I missed that. Thanks for the hint. Unfortunately, the "uname: Bad address" doesn't appear in qemu. Looks like I'll have to debug this on the actual hardware after all. Is this a

Re: sparc64 pbuilder/cowbuilder setup with qemu

2022-12-25 Thread John Paul Adrian Glaubitz
On 12/25/22 14:38, Gregor Riepl wrote: I suggest reporting this as a QEMU bug first and they'll tell you whether you're at the right address or need to forward this to the kernel or glibc people. Done: https://gitlab.com/qemu-project/qemu/-/issues/1394 Exemplary bug report, thanks a lot!

Re: sparc64 pbuilder/cowbuilder setup with qemu

2022-12-25 Thread Gregor Riepl
I suggest reporting this as a QEMU bug first and they'll tell you whether you're at the right address or need to forward this to the kernel or glibc people. Done: https://gitlab.com/qemu-project/qemu/-/issues/1394 I'll create an appropriate Debian bug when I have more information (i.e. which

Re: sparc64 pbuilder/cowbuilder setup with qemu

2022-12-24 Thread John Paul Adrian Glaubitz
Hi Gregor! On 12/23/22 17:13, Gregor Riepl wrote: Where should I report this bug, then? On the glibc Bugzilla, or on https://gitlab.com/qemu-project/qemu/-/issues ? Or is this a kernel bug? I suggest reporting this as a QEMU bug first and they'll tell you whether you're at the right address

Re: sparc64 pbuilder/cowbuilder setup with qemu

2022-12-23 Thread Gregor Riepl
Hi Adrian, Where should I report this bug, then? On the glibc Bugzilla, or on https://gitlab.com/qemu-project/qemu/-/issues ? Or is this a kernel bug? It looks like another case of values not properly passed between the host and guest in a qemu-user setup. Another very prominent case are

Re: sparc64 pbuilder/cowbuilder setup with qemu

2022-12-23 Thread John Paul Adrian Glaubitz
Hi Gregor! On 12/23/22 13:52, Gregor Riepl wrote: Comparing these two values: 42 0x2A 2752512 0x2A uid_t is defined as: /usr/include/sparc64-linux-gnu/sys/types.h:typedef __uid_t uid_t; /usr/include/sparc64-linux-gnu/bits/types.h:__STD_TYPE __UID_T_TYPE __uid_t; /* Type of

Re: sparc64 pbuilder/cowbuilder setup with qemu

2022-12-23 Thread Gregor Riepl
After a lot of yak shaving, I managed to add some debugging to apt: apt/apt-pkg/contrib/fileutl.cc:3364 return _error->Error("Could not switch saved set-user-ID (expected %lu got %lu)", (unsigned long) pw->pw_uid, (unsigned long) suid); (added the typecast to be sure printf isn't doing

Re: sparc64 pbuilder/cowbuilder setup with qemu

2022-12-19 Thread Gregor Riepl
[pid 102267] setgroups(1, [0] [pid 102267] <... setgroups resumed>)   = 0 ... [pid 102267] setresgid(65534, 65534, 65534) = 0 [pid 102267] setresuid(42, 42, 42)  = 0 [pid 102267] getgid()   = 65534 [pid 102267] getegid()  = 65534 [pid 102267] getuid()  

Re: sparc64 pbuilder/cowbuilder setup with qemu

2022-12-18 Thread Gregor Riepl
E: Method gave invalid 400 URI Failure message: Could not switch saved  set-user-ID E: Method http has died unexpectedly! E: Sub-process http returned an error code (112) This seems to be the problem and related to apt. For some reason, apt is not  able to switch its user id to "_apt". I'm not 

Re: sparc64 pbuilder/cowbuilder setup with qemu

2022-12-18 Thread John Paul Adrian Glaubitz
Hello Gregor! On 12/18/22 18:11, Gregor Riepl wrote: E: Method gave invalid 400 URI Failure message: Could not switch saved set-user-ID E: Method http has died unexpectedly! E: Sub-process http returned an error code (112) This seems to be the problem and related to apt. For some reason, apt