Source: ceph
Version: 0.80.11-1.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of ceph for architectures other than amd64 have been failing, mostly
with errors along the lines of

  dh_install --fail-missing
  dh_install: lib/systemd/system/rbdmap.service exists in debian/tmp but is not 
installed to anywhere
  dh_install: lib/systemd/system/ceph-disk@.service exists in debian/tmp but is 
not installed to anywhere
  dh_install: lib/systemd/system/ceph-rbd-mirror@.service exists in debian/tmp 
but is not installed to anywhere
  [...]
  dh_install: lib/systemd/system/ceph.target exists in debian/tmp but is not 
installed to anywhere
  dh_install: usr/lib/i386-linux-gnu/libcephfs_jni.a exists in debian/tmp but 
is not installed to anywhere
  dh_install: usr/lib/i386-linux-gnu/ceph/compressor/libceph_example.a exists 
in debian/tmp but is not installed to anywhere
  dh_install: usr/lib/i386-linux-gnu/ceph/compressor/libceph_snappy.a exists in 
debian/tmp but is not installed to anywhere
  [...]
  dh_install: usr/lib/i386-linux-gnu/ceph/compressor/libceph_zlib.so.2.0.0 
exists in debian/tmp but is not installed to anywhere
  dh_install: missing files, aborting
  debian/rules:66: recipe for target 'override_dh_install' failed
  make[1]: *** [override_dh_install] Error 255

(Builds on a few architectures failed earlier, due to errors I'll report
separately.)

I'm not sure offhand what's up with the lib/systemd paths -- perhaps a
systemd update while ceph was in NEW?  As for the files under /usr/lib, the
issue appears to be the presence of hardcoded /usr/lib/x86_64-linux-gnu
paths in debian/not-installed, which is documented not to support
wildcards. :-/ I suppose you could, prior to running dh_install, arrange
either to generate debian/not-installed or to remove up the unwanted files
altogether.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Reply via email to