Bug#993957: (no subject)

[lkcl <luke.leighton@gmail.com>]

i think i know what rhat might be. i flat-out refuse to let a mission critical piece of software developed by pottering run on systems that i manage, particularly after seeing the persistent generation of CVEs on mitre.org, and also in interactions with him where he just does not listen.

(translation: i was not running systemd.  sysvinit is still a supported option in debian, apt-get install sysvinit, and it is available via a grub boot menu option)

l.

On May 28, 2022 4:42:41 PM GMT+01:00, Christoph Biedl <debian.axhn@manchmal.in-ulm.de> wrote:

Control: tags 993957 moreinfo

lkcl wrote...

schroot 1.6.10 (04 May 2014) fails with a continuous attempt to read
a non-existent subdirectory, /run/systemd/userdb, when operating a
type "directory" schroot.

a type "plain" does not have this same issue.

creating the missing subdirectory manually "allows" the schroot to "proceed"
without errors.

As asked earlier, please provide more details about your setup, also the
schroot.conf snippet. Since I couldn't reproduce your issue here, but
based on the few information avaiable I might have done things slightly
different.

From reading the Ubuntu bug (also #763896) I assume this was fixed
upstream, we'll include that commit in the next uploads.

    Christoph