Andreas Henriksson <andr...@fatal.se> writes:

> Could you please try using `dpkg-buildpackage -uc -us`, rather than
> directly invoking debian/rules, and see if it helps you detect any
> misconfigurations in your build environment?

Just tried again in a new debian/testing64 VM (via vagrant).  It still
fails in the same way with "debian/rules binary", and fails in a new way
(dh_missing error) with "dpkg-buildpackage -uc -us".

Exact commands (suspect a current testing schroot would behave
similarly, but haven't tested that yet):

  $ mkdir tmp-mailutils-test
  $ cd tmp-mailutils-test
  $ vagrant init debian/testing64
  $ vagrant up
  $ vagrant ssh
  $ sudo -i
  # apt update
  # apt dist-upgrade
  # apt build-dep mailutils
  # apt source mailutils
  # cd mailutils-3.10
  # dpkg-buildpackage -uc -us
    ...
  make[1]: Entering directory '/root/mailutils-3.10'
  dh_fixperms -Xdotlock.mailutils
  make[1]: Leaving directory '/root/mailutils-3.10'
     dh_missing
  dh_missing: warning: usr/share/emacs/site-lisp/mailutils-mh.el exists in 
debian/tmp but is not installed to anywhere (related file: 
"debian/tmp/usr/share/mailutils/mh/mailutils-mh.el")
  dh_missing: warning: usr/share/emacs/site-lisp/mailutils-mh.elc exists in 
debian/tmp but is not installed to anywhere

          While detecting missing files, dh_missing noted some files with a 
similar name to those
          that were missing.  This error /might/ be resolved by replacing 
references to the
          missing files with the similarly named ones that dh_missing found - 
assuming the content
          is identical.

          As an example, you might want to replace:
           * debian/tmp/usr/share/mailutils/mh/mailutils-mh.el
          with:
           * usr/share/emacs/site-lisp/mailutils-mh.el
          in a file in debian/ or as argument to one of the dh_* tools called 
from debian/rules.
          (Note it is possible the paths are not used verbatim but instead 
directories
          containing or globs matching them are used instead)

          Alternatively, add the missing file to debian/not-installed if it 
cannot and should not
          be used.

          The following debhelper tools have reported what they installed (with 
files per package)
           * dh_install: libmailutils-dev (115), libmailutils7 (36), libmu-dbm7 
(2), mailutils (10), mailutils-common (14), mailutils-comsatd (1), 
mailutils-doc (1), mailutils-guile (2), mailutils-imap4d
  (1), mailutils-mda (3), mailutils-mh (46), mailutils-pop3d (2), 
python3-mailutils (23)
           * dh_installdocs: libmailutils-dev (0), libmailutils7 (0), 
libmu-dbm7 (0), mailutils (0), mailutils-common (0), mailutils-comsatd (0), 
mailutils-doc (6), mailutils-guile (0), mailutils-imap4d (0), mailutils-mda 
(0), mailutils-mh (1), mailutils-pop3d (0), python3-mailutils (0)
           * dh_installexamples: libmailutils-dev (0), libmailutils7 (0), 
libmu-dbm7 (0), mailutils (1), mailutils-common (0), mailutils-comsatd (1), 
mailutils-doc (0), mailutils-guile (1), mailutils-imap4d (1), mailutils-mda 
(0), mailutils-mh (0), mailutils-pop3d (1), python3-mailutils (0)
           * dh_installman: libmailutils-dev (2), libmailutils7 (0), libmu-dbm7 
(0), mailutils (10), mailutils-common (0), mailutils-comsatd (1), mailutils-doc 
(0), mailutils-guile (0), mailutils-imap4d (1), mailutils-mda (3), mailutils-mh 
(0), mailutils-pop3d (2), python3-mailutils (0)
          If the missing files are installed by another tool, please file a bug 
against it.
          When filing the report, if the tool is not part of debhelper itself, 
please reference the
          "Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
            (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
          Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
          If the omission is intentional or no other helper can take care of 
this consider adding the
          paths to debian/not-installed.
  dh_missing: error: missing files, aborting
  make: *** [debian/rules:4: binary] Error 255
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

It's trivial to reproduce with those commands, so happy to gather any
addiitonal information you might like.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Reply via email to