Bug#993957: closed by Christoph Biedl (Re: Bug#993957: (no subject))

2022-05-29 Thread Luke Kenneth Casson Leighton
On Sun, May 29, 2022 at 12:16 PM Debian Bug Tracking System wrote: > #993957: schroot: fails with non-existent subdirectory > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate messa

Bug#993957: (no subject)

2022-05-29 Thread lkcl
On Sun, May 29, 2022 at 11:51 AM Christoph Biedl wrote: > No doubt about that, but my time is too precious for advocacy. > And since I can neither understand nor reproduce the issue, there's > nothing left to do here. you misunderstand. i wasn't speaking of advocacy, merely explaining exactly h

Bug#993957: (no subject)

2022-05-28 Thread lkcl
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. (trans

Processed: Re: Bug#993957: (no subject)

2022-05-28 Thread Debian Bug Tracking System
Processing control commands: > tags 993957 moreinfo Bug #993957 [schroot] schroot: fails with non-existent subdirectory Added tag(s) moreinfo. -- 993957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#993957: (no subject)

2022-05-28 Thread Christoph Biedl
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 subdirec

Bug#993957: (no subject)

2021-09-08 Thread lkcl
Package: schroot Version: 1.6.10-12 Severity: important 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 subdirector