upstream has strange detection of prtfs-progs presence: configure.ac fails if there is no `btrfsctl' executable found. I don't know what is this, but there is no such binary in my system. moreover, that binary is not used actually by the `/etc/schroot/setup.d/05btrfs' script anyway. Reproducible: Always Steps to Reproduce: 1.USE=brtfs emerge schroot 2.configure script fails 3. in attach there is a pathc for ebuild and configure.ac to fix that problem
Created attachment 354584 [details] schroot-1.6.5-r1.ebuild
Created attachment 354586 [details, diff] patch to fix schroot's configure
Created attachment 354588 [details, diff] patch to schroot-1.6.5.ebuild (make it -r1)
Comment on attachment 354584 [details] schroot-1.6.5-r1.ebuild --- schroot-1.6.5.ebuild 2013-03-10 20:39:27.961366292 +0100 +++ - 2013-07-30 15:01:25.252841663 +0200 @@ -49,6 +49,7 @@ PATCHES=( "${FILESDIR}/${PN}-1.6.3-tests.patch" + "${FILESDIR}/${PN}-1.6.5-fix-btrfs-detection.patch" ) src_unpack() {
Comment on attachment 354586 [details, diff] patch to fix schroot's configure Why stop there? It doesn't need to know about /sbin/btrfs at build time either.
Apparently you shouldn't even be seeing this configure failure, since sys-fs/btrfs-progs provides /sbin/btrfs{,ctl} and since that package is properly listed in dev-util/schroot's DEPEND. Now, whether it should be in DEPEND at all is another issue, but it's the one you ended up with. Did the btrfs-progs executables move to /usr/sbin recently?
(In reply to Jeroen Roovers from comment #6) > Apparently you shouldn't even be seeing this configure failure, since > sys-fs/btrfs-progs provides /sbin/btrfs{,ctl} and since that package is > properly listed in dev-util/schroot's DEPEND. Now, whether it should be in > DEPEND at all is another issue, but it's the one you ended up with. Did the > btrfs-progs executables move to /usr/sbin recently? I don't know. Here is a list of executables from `btrfs-progs` I've got in my system: root@gentop ~ # cave executables btrfs-progs /sbin/mkfs.btrfs /sbin/btrfs-debug-tree /sbin/btrfsck /sbin/btrfs /sbin/btrfs-map-logical /sbin/btrfs-image /sbin/btrfs-zero-log /sbin/btrfs-convert /sbin/btrfs-find-root /sbin/btrfstune /sbin/btrfs-show-super and there is no `btrfsctl`! (probaply it is smth outdated)
(In reply to Jeroen Roovers from comment #5) > Why stop there? It doesn't need to know about /sbin/btrfs at build time > either. Yeah, really... schroot do not use detected executable path anyway... as well as lvm binaries... So, I suppose it must be RDEPEND only (lvm2 and ptrfs-progs), but I've got some uncertain feeling about this solution, cuz it require to patch configure.ac (just remove few lines) and I'm in doubt that upstream will accept this patch... so we have to apply it for all future releases, which is (slightly) harder that doing just version bump :)
I just ran into this, too.
Confirmed that it cannot find `btrfsctl` in the latest version (~1.6.5-r1). Any plans on including a patch in the ebuild?
*** Bug 524902 has been marked as a duplicate of this bug. ***
This should have been fixed as of the latest stable, 1.6.10-r3.