I've seen this bug too. It's caused by a binary- and source- incompatible change in e2fslibs, which I reported as #636418. This is also responsible for the FTBFS #634421.
This is, of course, extremely bad form of e2fslibs, which should have changed the soname and package name. -- [mdw] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
