Andreas Henriksson <andr...@fatal.se> writes: > Thanks for this info, it made it much easier to know where to look for > the problem which is caused by having emacs installed in the build > environment (which it isn't in a clean buildd chroot).
Ahh, sorry, clearly forgot to mention that I'd also run "apt install emacs-nox" to do some editing. Glad you figured it out. > I see these potential theoretical solutions: No strong opinion, fwiw -- I was originally just concerned about the build failure. > 2. just `rm -rf debian/tmp/usr/share/emacs` before dh_missing is ran. ...or maybe a dh_missing debian/not-installed override or -X if that'll work. > 4. Try to convince configure to enable emacs/lispdir without having > emacs necessarily installed (possibly by passing --with-lispdir) > and install the emacs/site-lisp files. > (Probably a better idea than 3 if possible.) Seems like in the short run, we didn't have those bits before, so perhaps fine to leave it that way for now. And in the longer run, if we decide we do want those files, and if there's much elisp code, it might ought to be compiled at install time as with dh-elpa or other emacsen-related packages, which might or might not suggest a mailutils-el package or something. If you do decide to head that route, I'd highly recommend #debian-emacs on oftc. Plenty of expertise there. Thanks again -- 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
