Bug#714733: [buildd-tools-devel] Bug#714733: Inside a schroot environment renaming directories inside /tmp fails in GNU/Hurd
Hi, Alle mercoledì 3 luglio 2013, Roger Leigh ha scritto: 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? The difference here (at least on exodar' setup, but I guess it is the same on the buildds) is that /tmp in the chroot is done using the firmlink translator to the system /tmp, which creates a link much similar to a bind mount. Indeed, setting up a firmlink translator and trying the commands earlier mentioned in this bug (#714733) gives the same failure, while they work when the root directory of both source and destination is not under a firmlink-ed node. Though, I have not investigated further whether the problem is in firmlink itself, in the libraries it uses or somewhere else. -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#714733: [buildd-tools-devel] Bug#714733: Inside a schroot environment renaming directories inside /tmp fails in GNU/Hurd
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=myproxyarch=hurd-i386ver=5.9-1stamp=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/Linuxhttp://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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714733: [buildd-tools-devel] Bug#714733: Inside a schroot environment renaming directories inside /tmp fails in GNU/Hurd
On Tue, Jul 02, 2013 at 12:00:03PM +0200, Mattias Ellert wrote: Package: schroot Version: 1.6.5-1 Severity: important User: debian-h...@lists.debian.org Usertags: hurd Inside a schroot environment renaming directories inside /tmp fails with Resource temporarily unavailable. This true not only for directories directly under /tmp, but also for directories further down a hierarchy within /tmp. Renaming directories in /tmp outside the schroot works fine. Renaming ordinary files in /tmp works fine also inside the schroot. Renaming directories outside of /tmp (e.g. in $HOME) works fine also inside the schroot. 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? Can you reproduce this manually without involving schroot? 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. 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. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714733: [buildd-tools-devel] Bug#714733: Inside a schroot environment renaming directories inside /tmp fails in GNU/Hurd
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-h...@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=myproxyarch=hurd-i386ver=5.9-1stamp=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 signature.asc Description: This is a digitally signed message part
