Thanks for your advice. I've disabled apparmor support and everything is fine now.
On Mon, 15 Feb 2016 02:22:37 AM Martin Pitt wrote: > Hello Russell, > > Russell Coker [2016-02-13 20:55 +1100]: > > < libcap-dev (>= 1:2.24-9~), > > --- > > > > > libcap-dev (>= 1:2.24-8), > > > > 28c28 > > This is indeed only relevant for unstable/testing, as that needs > libcap2-udeb. > > > < libapparmor-dev (>= 2.9.0-3+exp2) <!stage1>, > > --- > > > > > libapparmor-dev (>= 2.9.0-3) <!stage1>, > > This is more serious -- libapparmor was moved from /usr/lib to /lib as > pid 1 now depends on it. We got reports about failed boots when having > a separate /usr and no initrd. I'd argue that this is not a supported > use case, but it's something to be aware of at least. > > (Cf. "doing the /usr merge"..) > > > When I tried to build systemd I got the following error: > > /lib64/ld-linux-x86-64.so.2 (0x0000562d6a528000) > > libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 > > > > (0x00007fe3f3f48000) > > > > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 > > (0x00007fe3f3d44000) libattr.so.1 => > > /lib/x86_64-linux-gnu/libattr.so.1 > > > > (0x00007fe3f3b3f000) > > > > libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 > > > > (0x00007fe3f38fc000) > > > > libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 > > > > (0x00007fe3f36f7000) > > debian/rules:164: recipe for target 'override_dh_install' failed > > You cut off the interesting part, but this very much looks like the > safety check that verifies that systemd only links to libraries in > /lib, not in /usr. I suppose this is spotting the libappamor library > in /usr. > > I suggest to either backport libapparmor, or drop the build dependency > and --enable-apparmor completely for your backport. > > Martin -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
