Hi, On Sat, 22 Feb 2020 17:45:36 +0100 Johannes Schauer <jo...@debian.org> wrote: > Quoting Jörg Frings-Fürst (2020-02-22 17:36:10) > > Am Samstag, den 22.02.2020, 17:17 +0100 schrieb Johannes Schauer: > > > Control: severity -1 important > > > > > > Quoting Johannes Schauer (2020-02-22 17:05:47) > > > > Quoting Jörg Frings-Fürst (2020-02-22 16:48:52) > > > > > > please show me evidence of that. > > > > > > > > > > > > Setting a bug severity to serious means that sbuild will be > > > > > > removed from > > > > > > testing in March. You should have evidence before such a > > > > > > drastic measure is > > > > > > taken. > > > > > All packages that directly or indirectly have systemd as build > > > > > depend can no > > > > > longer be compiled. I think that is reason enough. > > > > > > > > Indeed I now see the problem myself. > > > > > > > > Can you confirm something for me? > > > > > > > > Above you quote an sbuild-createchroot command. Could you run the > > > > same command > > > > on your machine again but with --debootstrap=mmdebstrap in it? > > > > > > > > Because for me, that fixes the problem. This suggests that the > > > > problem is not > > > > with sbuild but with the program that creates the chroot: > > > > debootstrap > > > > > > something else you can try: Instead of adding -- > > > debootstrap=mmdebstrap try > > > adding --no-merged-usr to your sbuild-createchroot invocation. This > > > also fixed > > > the problem for me. > > > > > > So it seems whatever it is, and whoever is at fault, this problem is > > > not > > > severity "serious", thus lowering severity accordingly. > > > > > > > No. Also with a schroot build with --no-merged-usr I get: > > did you also try with --debootstrap=mmdebstrap instead of --no-merged-usr?
could you follow up on this? Thanks! cheers, josch
signature.asc
Description: signature
