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

[Roger Leigh]

On Tue, Jul 02, 2013 at 01:32:07PM +0200, Mattias Ellert wrote:
> 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.

Could the hurd buildd people possibly take a look here?

> > 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.

Sure, but what I mean here is this: can you recreate the mounts which
schroot sets up without involving schroot.  schroot itself just
mounts some filesystems and executes a chrooted program/shell; it's
not doing any magic.  If "mv" is failing then there's a fault in
the system itself, though the way schroot set up the mounts may
trigger it.

> > 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.

CCing the hurd porters.  I would certainly appreciate some help
investigating the above issue, and getting some hurd-specific
templates into schroot will hopefully result in a decent default
setup for hurd schroot/sbuild/buildd users.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux    http://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-    GPG Public Key      F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800