Bug#789694: schroot: Please consider patch to fix it on hurd-i386

Control: tags 789694 moreinfo Gabriele Giacone wrote... > attached patch makes schroot working on hurd, has been being tested on > exodar porterbox since many months. > It works around #763932 bug. > > More info in threads at > https://lists.debian.org/debian-hurd/2014/09/msg00058.html >

Processed: Re: Bug#789694: schroot: Please consider patch to fix it on hurd-i386

Processing control commands: > tags 789694 moreinfo Bug #789694 [schroot] schroot: Please consider patch to fix it on hurd-i386 Added tag(s) moreinfo. -- 789694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#763896: marked as done (schroot: infinite allocation on uid/gid entry errors.)

Your message dated Sun, 29 May 2022 21:15:56 + with message-id and subject line Bug#763896: fixed in schroot 1.6.10-13 has caused the Debian Bug report #763896, regarding schroot: infinite allocation on uid/gid entry errors. to be marked as done. This means that you claim that the problem

Bug#984768: marked as done (schroot: fails chrooting in qemu-debootstrap rootfs)

Your message dated Sun, 29 May 2022 20:45:31 +0200 with message-id <1653849...@msgid.manchmal.in-ulm.de> and subject line Re: Bug#984768: schroot: fails chrooting in qemu-debootstrap rootfs has caused the Debian Bug report #984768, regarding schroot: fails chrooting in qemu-debootstrap rootfs to

Bug#681884: marked as done (schroot: Does not always clean up after itself.)

Your message dated Sun, 29 May 2022 20:45:26 +0200 with message-id <1653846...@msgid.manchmal.in-ulm.de> and subject line Re: Bug#681884: Cleaning up has caused the Debian Bug report #681884, regarding schroot: Does not always clean up after itself. to be marked as done. This means that you claim

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

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

Bug#993957: (no subject)

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

Bug#993957: marked as done (schroot: fails with non-existent subdirectory)

Your message dated Sun, 29 May 2022 12:51:42 +0200 with message-id <1653821...@msgid.manchmal.in-ulm.de> and subject line Re: Bug#993957: (no subject) has caused the Debian Bug report #993957, regarding schroot: fails with non-existent subdirectory to be marked as done. This means that you claim

Bug#785567: marked as done (schroot.conf manpage: typo: rootr -> root)

Your message dated Sun, 29 May 2022 12:51:53 +0200 with message-id <1653821...@msgid.manchmal.in-ulm.de> and subject line Re: Bug#785567: schroot.conf manpage: typo: rootr -> root has caused the Debian Bug report #785567, regarding schroot.conf manpage: typo: rootr -> root to be marked as done.

Processed: found 987278 in 0.99.beta19-2.2

Processing commands for cont...@bugs.debian.org: > found 987278 0.99.beta19-2.2 Bug #987278 {Done: Fabio Fantoni } [src:libcaca] CVE-2021-30498 CVE-2021-30499 Marked as found in versions libcaca/0.99.beta19-2.2. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: found 987278 in 0.99.beta19-2.1

Processing commands for cont...@bugs.debian.org: > found 987278 0.99.beta19-2.1 Bug #987278 {Done: Fabio Fantoni } [src:libcaca] CVE-2021-30498 CVE-2021-30499 Marked as found in versions libcaca/0.99.beta19-2.1. > thanks Stopping processing here. Please contact me if you need assistance. --