Also, it DOES NOT DEPEND on lockdev
(no need to wait for endless resolution of bug #600636)

To help Zach move it, here are proposed .spec and srpm:
Spec URL: http://oron.fedorapeople.org/deb-package/schroot.spec
SRPM URL: http://oron.fedorapeople.org/deb-package/schroot-1.7.0-1.fc18.src.rpm

Other highlights:
 * Full 'make check' run
 * Supports both lvm-snapshot and lvm-btrfs

Notes regarding libsbuild:
 * Had to use default linking (dynamic) with included libsbuild
 * That's what upstream does -- and it works.
 * Trying --enable-static --disable-dynamic creates non-functional scrhoot.
 * Even trivial self-tests fails due to "unknown" facets (e.g: "directory")
 * Trying to debug this, shows that the "missing" facets are linked into
     libsbuild.{a,so}:
            nm -C lib/sbuild/.libs/libsbuild.a | \
                  grep 'T sbuild::chroot::facet::directory\>'

 * However, these facets do not appear in the static test binary:
            nm -C test/sbuild/chroot/config | \
                  grep 'T sbuild::chroot::facet::directory\>'

 * So I gave up on static linking (should we insist on this?)

Thanks Oron, I will take a look at your changes and try them on my system.

I'm a little bit concerned that 1.7 is an odd-numbered (and therefore unstable) release.

So if we update to it, some extra testing effort might be in order.   

The original package review contains some information about why the static compile is set up:

https://bugzilla.redhat.com/show_bu.cgi?id=447368

I am getting this build error from the test suite in 1.7.0.  I got the same error when I tried schroot-1.6.5 a few weeks ago:

1) test: test_run_parts::test_run2 (E) 
uncaught exception of type N5boost10filesystem16filesystem_errorE
- boost::filesystem::directory_iterator::construct: No such file or directory: "test/testdata/run-parts.ex2"

The error message is not meaningful to me.  If you have any ideas, please let me know.

Something weird is happening:
 * The upstream tarball is *different* than the one I used few weeks ago
   when testing this.
 * The new file really miss this directory. While the old-one (in my SRPM) has it.
 * However, nobody changed the version of the upstream tarball.
 * I think upstream should be notified about it.

Upstream bug for tarball inconsistency and unit test problem:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711277

(In reply to Zach Carter from comment #3)
> I am getting this build error from the test suite in 1.7.0.  I got the same
> error when I tried schroot-1.6.5 a few weeks ago:
> 
> 1) test: test_run_parts::test_run2 (E) 
> uncaught exception of type N5boost10filesystem16filesystem_errorE
> - boost::filesystem::directory_iterator::construct: No such file or
> directory: "test/testdata/run-parts.ex2"
> 
> The error message is not meaningful to me.  If you have any ideas, please
> let me know.

This is failing because upstream tarball (1.7.0 and 1.6.x) is missing this empty directory:
schroot-<version>/test/run-parts.ex2

(In reply to Slawomir Czarko from comment #6)

> This is failing because upstream tarball (1.7.0 and 1.6.x) is missing this
> empty directory:
> schroot-<version>/test/run-parts.ex2

Thanks...I added the empty directory with mkdir and now the build is at least working, updated to 1.6.5 in rawhide.

This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

*** This bug has been marked as a duplicate of bug 1096761 ***