Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2022-04-26 Thread Jochen Sprickerhof
Hi, I've send an updated version of autopkgtest-virt-unshare as a merge request: https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/138 Cheers Jochen * Jochen Sprickerhof [2022-04-17 22:10]: Hi, * Martin Pitt [2016-11-16 13:37]: Johannes Schauer [2016-11-16 1:12 +0100]: in

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2022-04-17 Thread Jochen Sprickerhof
Hi, * Martin Pitt [2016-11-16 13:37]: Johannes Schauer [2016-11-16 1:12 +0100]: in the context of #833407 I told you about my plan of adding a virtualization backend which would allow completely unprivileged chroot operation by using linux user namespaces. Nice! In contrast to what I

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-12-11 Thread Johannes Schauer
Hi again, Quoting Johannes Schauer (2016-12-08 18:10:18) > Firstly, because the autopkgtest-virt-* program is in the same process group > it will also receive the Ctrl+C sent by the user and will immediately clean > up and exit. The problem with autopkgtest doing that from the sbuild point of >

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-12-08 Thread Johannes Schauer
Hi Martin, Quoting Martin Pitt (2016-12-08 17:59:44) > Johannes Schauer [2016-11-16 17:32 +0100]: > > For example, most notably, "mount -t proc proc /proc" never worked without > > doing the systemcalls manually using the perl script I present there. This > > problem of course might also have

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-12-08 Thread Johannes Schauer
Hi, Quoting Martin Pitt (2016-12-08 17:43:39) > Maybe I misunderstood you above, but you said that sbuild was creating the > "session", which I assumed was the schroot session that it uses to build the > package and run its autopkgtest in. > > If sbuild *does* control the schroot session, then

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-12-08 Thread Martin Pitt
Hello Josch, Johannes Schauer [2016-11-16 17:32 +0100]: > For example, most notably, "mount -t proc proc /proc" never worked without > doing the systemcalls manually using the perl script I present there. This > problem of course might also have been due to remaining bugs in the tools I > used

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-12-08 Thread Martin Pitt
Johannes Schauer [2016-12-08 16:53 +0100]: > > > Should sbuild expect that > > > after the user presses Ctrl+C, the autopkgtest backend takes care to > > > completely > > > shut down the backend by itself? I don't think this is a viable option > > > because > > > the autopkgtest backend used by

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-12-08 Thread Johannes Schauer
Hi Martin, Quoting Martin Pitt (2016-12-08 16:37:58) > Johannes Schauer [2016-11-26 6:03 +]: > > I don't know what the best course of action here is. Should sbuild expect > > that > > after the user presses Ctrl+C, the autopkgtest backend takes care to > > completely > > shut down the

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-12-08 Thread Martin Pitt
Hello Johannes, Johannes Schauer [2016-11-26 6:03 +]: > I don't know what the best course of action here is. Should sbuild expect that > after the user presses Ctrl+C, the autopkgtest backend takes care to > completely > shut down the backend by itself? I don't think this is a viable option

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-11-26 Thread Johannes Schauer
Hi, Quoting Johannes Schauer (2016-11-26 06:03:45) > So if I use sbuild with the autopkgtest schroot backend, and then press > Ctrl+C during dpkg-buildpackage, the following will happen: > > - the hook_cleanup() of autopkgtest-virt-schroot is called > - schroot is unable to close the session

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-11-25 Thread Johannes Schauer
Hi, Quoting Johannes Schauer (2016-11-16 16:32:05) > Quoting Martin Pitt (2016-11-16 16:17:29) > > Johannes Schauer [2016-11-16 14:13 +0100]: > > > I have another autopkgtest-specific question. Currently, when using this > > > code with sbuild and I hit Ctrl+C to send a SIGINT, it appears as if >

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-11-16 Thread Johannes Schauer
Hi, Quoting Martin Pitt (2016-11-16 16:17:29) > Johannes Schauer [2016-11-16 14:13 +0100]: > > Unfortunately, I was unable to achieve the same I'm currently doing with > > lxc-usernsexec and lxc-unshare with unshare and nsenter. > > Interesting; now you sparked my curiosity :-) Do you happen to

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-11-16 Thread Martin Pitt
Hey Josch, Johannes Schauer [2016-11-16 14:13 +0100]: > Unfortunately, I was unable to achieve the same I'm currently doing with > lxc-usernsexec and lxc-unshare with unshare and nsenter. Interesting; now you sparked my curiosity :-) Do you happen to remember the details what isn't working? >

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-11-16 Thread Johannes Schauer
Hi, Quoting Martin Pitt (2016-11-16 13:37:50) > > - the lxc package installed for lxc-usernsexec and lxc-unshare > > I'd like to eliminate this even. util-linux' unshare has known about > --user/-U for a while now, and thus replaces lxc-unshare and > lxc-usernsexec: > > $ unshare -rmU sh -c

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-11-16 Thread Martin Pitt
Hello Josch, Johannes Schauer [2016-11-16 1:12 +0100]: > in the context of #833407 I told you about my plan of adding a > virtualization backend which would allow completely unprivileged chroot > operation by using linux user namespaces. Nice! > In contrast to what I thought was required back

Bug#844459: autopkgtest: Please add autopkgtest-virt-uchroot

2016-11-15 Thread Johannes Schauer
Package: autopkgtest Version: 4.2 Severity: wishlist Tags: patch Hi Martin, in the context of #833407 I told you about my plan of adding a virtualization backend which would allow completely unprivileged chroot operation by using linux user namespaces. In contrast to what I thought was required