[From nobody Wed Nov 4 04:07:05 2026 Received: (at submit) by bugs.debian.org; 19 Sep 2022 11:09:49 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.2-bugs.debian.org_2005_01_02 (2018-09-13) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-16.1 required=4.0 tests=BAYES_00,DIGITS_LETTERS, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,HAS_PACKAGE, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP,XMAILER_REPORTBUG autolearn=ham autolearn_force=no version=3.4.2-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 23; hammy, 150; neutral, 246; spammy, 0. spammytokens: hammytokens:0.000-+--XDebbugsCc, 0.000-+--X-Debbugs-Cc, 0.000-+--bookworm, 0.000-+--sk:taint_o, 0.000-+--sk:TAINT_O Return-path: <arnaudr@kali.org> Received: from mail-pj1-x102c.google.com ([2607:f8b0:4864:20::102c]:36540) by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <arnaudr@kali.org>) id 1oaEer-0007h9-8N for submit@bugs.debian.org; Mon, 19 Sep 2022 11:09:49 +0000 Received: by mail-pj1-x102c.google.com with SMTP id s14-20020a17090a6e4e00b0020057c70943so6738814pjm.1 for <submit@bugs.debian.org>; Mon, 19 Sep 2022 04:09:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kali.org; s=google; h=date:message-id:subject:to:from:content-transfer-encoding :mime-version:from:to:cc:subject:date; bh=6bIaVeD74xKGFsTs1M7fRhamaHbHrbyq/7bDJlJ/5eU=; b=kY3BtzYYeOS3AKhXeZAiOoixyGDyCZ8RFgaFf1JjlMQ/Dr/ETrFdnVgUN1IAAjFefQ COVxgebz/gqLUaEQ0ldZq+8IsX4eAXGvjxvlPsRcl+NjcL5QnJF3lw17wdfHY5AgUA1Y In3GrVpJy9Q4Spq4Y4CS2GWpdaY4aWU9PULb9glrWWpOgVVJXtcZE2JBE8fYD2FLeWWu WFNbhUnpHMu82Rp+nA/QAjNfFdqgdyj9TlfphZ/rDY2PepVyzsG8WMFQV8rEuV44Goxg eW4R+40ULPM3FDwfIIIc+pKY+flcpercGoMIg9qhnOBsrPV3ob5EnITcbeMYEHcTzfb/ JHaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=date:message-id:subject:to:from:content-transfer-encoding :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=6bIaVeD74xKGFsTs1M7fRhamaHbHrbyq/7bDJlJ/5eU=; b=Ga548sgCZT03oEf9JzdTxmZMyVCX0Dv4L3alMhOIR8ojJ237EOeir2Hn4fy1QbbIyJ VvFjQJ2IYEeuvv33noFfPHOCbv7gLtNZNt4JKF2Y7NBuyAyxSNSWfDjLUzBnwsV3v+PU LvFrOmosjda2s35lCnx/LMpWxaSZ/4hMxeDPajUyOb+SjqYf5epLPCpj89WpPxbd1As6 MSaYLxXHURdNfXsmDjql2XeDUPLQV0h/ZjdzRPMRfEeSriJHoyIHJDdQ/k2/HJ/Opvyk iPvjo6ghyIYTeaqduPfvzw0JRXy7CBeP94lWeYLp6ktARiIIILcYGtUtqBp3XM0z4W64 sP3w== X-Gm-Message-State: ACrzQf0ta5kGD3lKezS7T+NHwQg5O6IpKWETP61FU/GZ/BWBOuDarFZ/ y1GXUZmWbyQMJ9rQNhTObswJbg6msc7y1TGw X-Google-Smtp-Source: AMsMyM4hlYaKZA9mo6aVeqrswYujFMmU/xNGuVE5r46LNVB14vD1EcbNGZVlQyIPQXdRDmwHhfdgBg== X-Received: by 2002:a17:903:2290:b0:178:272b:e414 with SMTP id b16-20020a170903229000b00178272be414mr12464686plh.120.1663585786958; Mon, 19 Sep 2022 04:09:46 -0700 (PDT) Received: from localhost ([171.249.144.244]) by smtp.gmail.com with ESMTPSA id d4-20020aa797a4000000b0053e3a6f7da4sm20621019pfq.12.2022.09.19.04.09.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 19 Sep 2022 04:09:46 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Arnaud Rebillout <arnaudr@kali.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: debos: unable to resolve host address Message-ID: <166358578402.826466.12671335912107413414.reportbug@carbon> X-Mailer: reportbug 11.5.1 Date: Mon, 19 Sep 2022 18:09:44 +0700 Delivered-To: submit@bugs.debian.org Package: debos Version: 1.0.0+git20210707.c66a48d-2+b2 Severity: important User: devel@kali.org Usertags: origin-kali X-Debbugs-Cc: daissi@debian.org Dear Maintainer, at the moment debos (and fakemachine) is broken in unstable: ~~~~ $ cat debootstrap.yaml architecture: amd64 actions: - action: debootstrap suite: stable $ debos debootstrap.yaml Running /debos --artifactdir /home/arno/kali/proj/vm-images/kali-vm/tmp /home/arno/kali/proj/vm-images/kali-vm/tmp/debootstrap.yaml using kvm backend 2022/09/19 10:49:09 ==== debootstrap ==== 2022/09/19 10:49:09 Debootstrap | W: Unable to read /etc/apt/apt.conf.d/ - DirectoryExists (2: No such file or directory) 2022/09/19 10:49:09 Debootstrap | W: Unable to read /etc/apt/apt.conf.d/ - DirectoryExists (2: No such file or directory) 2022/09/19 10:49:09 Debootstrap | I: Target architecture can be executed 2022/09/19 10:49:09 Debootstrap | I: Retrieving InRelease 2022/09/19 10:49:09 Debootstrap | I: Retrieving Release 2022/09/19 10:49:09 Debootstrap | E: Failed getting release file http://deb.debian.org/debian/dists/stable/Release 2022/09/19 10:49:09 debootstrap.log | amd64: ok 2022/09/19 10:49:09 debootstrap.log | wget: unable to resolve host address 'deb.debian.org' 2022/09/19 10:49:09 debootstrap.log | wget: unable to resolve host address 'deb.debian.org' 2022/09/19 10:49:09 Action `debootstrap` failed at stage Run, error: exit status 1 Powering off. ~~~~ Hostname resolution broke because systemd-resolved was split out of the systemd package, and now it lives in its own package systemd-resolved. On my system, systemd-resolved is not installed, hence the failure above. Apparently systemd-resolved is mandatory for the kvm backend? What about the uml backend? At a first glance, it seems that debos (and fakemachine) should now Depend on systemd-resolved. However it's a bit more complicated. Installing the package systemd-resolved has MAJOR consequences: - the postinst script will remove /etc/resolv.conf, and replace it with a symlink to ../run/systemd/resolve/stub-resolv.conf - the service systemd-resolved will be enabled This behavior makes sense when a user manually installs systemd-resolved (because they want to use it for name resolution). But when installing debos, enabling name resolution via systemd-resolved at the same time is surely an unintended (and unexpected) effect. I don't know how to handle that. I don't know if it would be possible to rework the systemd-resolved package and split it, so that it's possible to install the binaries, without actually enabling it. Maybe we should ask the systemd maintainer, but I wanted to get your impression first. Thanks! Arnaud -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debos depends on: ii busybox 1:1.35.0-2 ii debootstrap 1.0.127 ii libc6 2.34-7 ii libglib2.0-0 2.73.3-3 ii libostree-1-1 2022.5-3 ii qemu-system-x86 1:7.0+dfsg-7+b1 ii qemu-user-static 1:7.0+dfsg-7+b1 ii systemd-container 251.4-3 Versions of packages debos recommends: ii bmap-tools 3.6-1 ii bzip2 1.0.8-5 ii e2fsprogs 1.46.5-2 ii linux-image-amd64 5.19.6-1 ii mount 2.38.1-1 ii ovmf 2022.05-4 ii parted 3.5-1 ii udev 251.4-3 ii xz-utils 5.2.5-2.1 ii zip 3.0-12 debos suggests no packages. -- no debconf information ]