[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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 <1653846180@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 that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
681884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681884
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: schroot
Version: 1.6.0-1
Severity: important

Hi,

I've set up a schroot of type=directory and pointed directory to
the right place, but when I then call schroot to get into that,
and then left it, it reguarly fails with:
E: 10mount: umount: /var/lib/schroot/mount/i386-sid-8850e601-cd43-4a82-b87c-08a8120619bd/home: device is busy.
E: 10mount:         (In some cases useful info about processes that use
E: 10mount:          the device is found by lsof(8) or fuser(1))
E: i386-sid-8850e601-cd43-4a82-b87c-08a8120619bd: Chroot setup failed: stage=setup-stop



Kurt

--- End Message ---
--- Begin Message --- 
Raphael Hertzog wrote...

> I'm not sure everybody had the same underlying problem in this
> bug report but I just uploaded 1.6.10-3 which fixes multiple
> problems that could make the cleanup process fail.
>
> If you still have problem on a stretch system with that schroot version,
> feel free to open a new bug.

Five years later I assume this is really no longer an issue, hence
closing. And still, if you encouter problems like the one in this bug,
please reopen and provide the bits needed to reproduce it.

    Christoph

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: