Bug#526081: [buildd-tools-devel] Bug#526081: schroot: not enough warning for missing chroot

2009-04-29 Thread Adeodato Simó
+ Roger Leigh (Wed, 29 Apr 2009 09:21:09 +0100):

> The only create_directory call is in
> bin/schroot-mount/schroot-mount-main.cc
> which creates mountpoints inside the chroot.  Are you mounting
> in a directory path which has more than two levels nonexistent?
> It might be that mkdir is failing due to create_directory not
> behaving like "mkdir -p", in which case we should add the
> functionality.

> Regarding errors, the useless error is coming from boost.  I'll need
> to reproduce it and see what it's doing, and then file a bug against
> boost if it's at fault.

I'm just using a chroot definition as follows:

[foo]
type=lvm-snapshot
location=/nonexistant
device=/dev/vg/chroot
lvm-snapshot-options=--size 1G

And then:

% sudo schroot -c foo-source
E: boost::filesystem::create_directory
E: foo-source: Chroot setup failed: stage=setup-start

I hope that, with that, you can reproduce.

-- 
- Are you sure we're good?
- Always.
-- Rory and Lorelai




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#526081: [buildd-tools-devel] Bug#526081: schroot: not enough warning for missing chroot

2009-04-29 Thread Roger Leigh
On Wed, Apr 29, 2009 at 08:34:11AM +0200, Adeodato Simó wrote:

> I had a bunch of LVM type chroots, and after removing one of them, a
> script that tried to make use of it started emitting the following
> output:
> 
> E: boost::filesystem::create_directory
> 
> That's all. As you can see, it's not very descriptive of the problem. It
> is true the script rus schroot with -q. Without -q, one gets:
> 
> E: boost::filesystem::create_directory
> E: etch-i386-source: Chroot setup failed: stage=setup-start
> 
> Which is also not indicative at all of what the exact problem was
> ("Could not find location /lvm-etch_i386 in device /dev/vg/chroot").
> It be nice if something to that could be printed, even with -q.

The only create_directory call is in
bin/schroot-mount/schroot-mount-main.cc
which creates mountpoints inside the chroot.  Are you mounting
in a directory path which has more than two levels nonexistent?
It might be that mkdir is failing due to create_directory not
behaving like "mkdir -p", in which case we should add the
functionality.

Regarding errors, the useless error is coming from boost.  I'll need
to reproduce it and see what it's doing, and then file a bug against
boost if it's at fault.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please GPG sign your mail.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org