[buildd-tools-devel] Bug#714733: Bug#714733: Inside a schroot environment renaming directories inside /tmp fails in GNU/Hurd

Mattias Ellert mattias.ellert at fysast.uu.se
Tue Jul 2 11:32:07 UTC 2013


tis 2013-07-02 klockan 11:43 +0100 skrev Roger Leigh:

> What's different about /tmp inside the chroot?  Is it bind mounted
> (or the hurd equivalent) inside the chroot?  What is the configuration
> you are using for this chroot; did you make any particular
> customisations?

If you want to know details about how the schroot is configured on the
porterbox, only the administrators of that machine can tell you. I was
using the porterbox to figure out why one of my packages fails to build
in the Debian build system for gnu/hurd. I did not do any tweaking of
the configuration myself, but I have no idea if the porterbox admin has
done something.

> Can you reproduce this manually without involving schroot?

As mentioned in the bug report, outside the schroot there is no problem
renaming directories in /tmp.

> I strongly suspect that this is a hurd-specific bug or configuration
> issue; while we might be able to work around such issues by avoiding
> it in the default hurd configuration, it would be good to know to
> start with what is actually causing the failure here.

Yes it is hurd specific. The package that fails to build on gnu/hurd due
to this issue builds without problem on all other architectures. This
was the reason I added

User: debian-hurd at lists.debian.org
Usertags: hurd

to the bug report.

> Regarding the default configuration: The schroot source code
> contains system-specific configuration templates
> (etc/profile-templates) for linux and freebsd.  There are currently
> no hurd templates, and if anyone wanted to create them that might
> give a better default experience for hurd users.

This issue is the cause of failed package builds, see e.g.

https://buildd.debian.org/status/fetch.php?pkg=myproxy&arch=hurd-i386&ver=5.9-1&stamp=1358177698

This issue can be seen on both a gnu/hurd debian porter box and four
different gnu/hurd sbuild hosts, so it seems to be a general problem
affecting all gnu/hurd machines.

I am sorry I can not provide more information, but I am no expert in
gnu/hurd. I hope there is some gnu/hurd expert that can provide input.

> Thanks,
> Roger

	Mattias

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20130702/28e15a3f/attachment-0001.sig>


More information about the Buildd-tools-devel mailing list