Hi, Quoting Santiago Vila (2024-04-04 20:03:08) > El 4/4/24 a las 19:29, Johannes Schauer Marin Rodrigues escribió: > > Also I'm curious: what is your motivation for using unshare mode if you are > > creating your chroots using superuser privileges? > > > > And are you really storing your chroots in /srv instead of letting them get > > picked up automatically in ~/.cache/sbuild/unstable-arm64.tar? > > I am testing the unshare backend at the request of Jochen.
I now also talked with Jochen on IRC. :) > As we speak, I am building all packages in bookworm using unshare. Thank you for doing that! I'd assume that quite a few testsuites break in that environment. > I already had a working setup for building packages using the other backends. > In my setup, I run debootstrap in a master server, create the tarballs there, > and the build nodes retrieve those tarballs using wget before they start to > build packages. > > So in my setup the logical thing to do to test the unshare backend > was to make symlinks to the already existing tarballs at /srv, since the > nodes are not creating any tarballs. That makes sense, yes. I think it makes sense for sbuild to accept tarballs without the leading ./. I think the best way to achieve this, is to filter out the device nodes from the input tarball. The utility that I know that can do this is mmtarfilter like this: mmtarfilter --type-exclude CHRTYPE --type-exclude BLKTYPE Unfortunately, that utility is written in Python and sbuild currently does not depend on Python. I wonder if the same can be done in Perl? Maybe I should write a very crude tarball parser that is able to do just enough parsing...
signature.asc
Description: signature
