Hello, Johannes Schauer Marin Rodrigues, le dim. 07 sept. 2025 13:46:41 +0200, a ecrit: > Do you think it would make sense to add an extra alias like > --mode=fakeroot-hurd?
That could make sense, yes. > I envision that if the user calls mmdebstrap without > --mode, then the default mode (auto) should be selecting fakeroot(-hurd) on > hurd Yes. > but if the user wants to be explicit, they would run it with fakeroot-hurd > to replace auto-detection with explicit mode selection. Having fakeroot-hurd > as > anothera alias for fakeroot would also slightly help with documenting. What do > you think? That could be useful, yes. > That being said, I think we got to the bottom of the misunderstanding (I hope) It seems so, yes. > and the next thing to do is for me to create a QEMU VM with hurd and try this > out myself. As I said, since the mmdebstrap testsuite runs inside qemu, I > could > even add hurd tests to the mmdebstrap testsuite to avoid regressions in the > future. Good :) thanks! > As far as I'm concerned, running this on hurd should *just work* and create a > usable tarball: > > mmdebstrap unstable chroot.tar Ideally, yes, but that means it'd automatically enable the debian-ports-archive keyring and the unreleased suite? > > > > and chroot is just the normal chroot as one would use it on linux. > > > > > > And here you mean the chroot *binary* in /usr/sbin, right? > > > > Yes. Or the chroot() function: both will work fine as non-root. > > Perfect. Next on my todo list is to fix img2pdf, then mmdebstrap, then sbuild > and *then* I'll have time for this. Good :) Thanks a lot for this, Samuel
