blob: 495148cf27a162f5ca46bd8fc9776bdee8359a0e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
dh-elpa (1.12) experimental; urgency=medium
This version of dh_elpa uses a more restricted load-path for
byte-compilation than previous versions. In particular by default it
only looks at the directories searched by emacs --quick, and installed
dh_elpa based packages. There are two solutions for maintainers of
packages with non-elpa-* dependencies. A long term solution is to
convince the maintainers of your dependencies to use dh_elpa; a local
fix is to add an --emacs-loadpath option to debian/rules. See
dh_elpa(1) for details.
-- David Bremner <bremner@debian.org> Sun, 21 Jan 2018 22:42:56 -0400
dh-elpa (0.0.20) unstable; urgency=medium
This version of dh_elpa will try to run any ERT and Buttercup test
suites that it can find if you set the debhelper compat level to 10
or above. If you are currently running your package's test suite
with a override_dh_auto_test stanza in debian/rules, or if there
exists an upstream test suite that you are not running, dh_elpa will
override any override_dh_auto_test stanza and try to run the test
suite. If it can't run it in its default configuration, this will
lead to your package failing to build from source.
The easy fix is to add a line like this to the top of your debian/rules:
export DH_AUTO_TEST_DISABLE
If instead you would like to migrate to have dh_elpa run your test
suite and it fails to do so in its default configuration, see
dh_elpa_test(1) for how to configure dh_elpa_test to run the test
suite successfully.
-- Sean Whitton <spwhitton@spwhitton.name> Sun, 1 May 2016 10:46:33 -0700
|
