Your message dated Sun, 13 May 2007 11:20:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#422909: fixed in schroot 1.1.2-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: schroot
Version: 1.1.1-1
Severity: critical
Hi,
I use schroot with 'file' chroots to build packages using sbuild. Since
I upgraded to version 1.1.1-1, things started to go wrong (so I blame
schroot, not sbuild).
The attached log shows the problem. It seems that during the cleanup
phase, the various bind mounts are not unmounted, similarly to what
happened with #401180. So the "real" /home, /tmp, etc are erased during
the cleanup phase.
I haven't found out yet why it's failing. Also, it's failing when I
start builds over ssh, but I couldn't reproduce the failure when
starting builds locally. There might be something different when setting
up my build nodes that causes it not to fail, or it might just be bad
(or good?) luck.
I'll try to investigate it further (probably tomorrow), I just wanted to
report it first, since you are more likely to know what changed and
could break :-)
Thank you,
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
language-support-mr.buildlog.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 1.1.2-1
* Adeodato Simó [Fri, 11 May 2007 21:02:44 +0200]:
> While this addresses the data loss problem, the underlying cause is
> still there, and means that non-plain chroots accessed via ssh, or cron
> (eg. for maintenance tasks), will not be properly cleaned after. I think
> this is a bug worth fixing, do you agree?
As Roger pointed me on IRC, this issue was addressed as well in the last
upload -- only, it didn't get an entry in the Debian changelog (only in
the upstream one).
I've verified it works correctly, so I'm closing this bug.
Thanks!
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
Beauty, brains, availability, personality: pick any two.
--- End Message ---
