Package: mercurial Version: 5.0-1 Severity: wishlist Dear Maintainer,
The Evolve Mercurial extension has a third-party Debian package. It's not packaged or distributed by Debian. It's part of upstream sources. The development version of Evolve is at https://bitbucket.org/octobus/evolve-devel. The Evolve tests are run using Mercurial's test runner, namely the file `tests/run-tests.py` in the Mercurial sources. And the tests are run by default as part of the Evolve Debian build. The current situation is that if a user wants to run the Evolve tests, he/she has to download the Mercurial sources, and point the Debian build to those sources to get access to the test runner. Which is rather manual. Otherwise, the tests will fail to run. So a better solution would be to include `tests/run-tests.py` as part of the Debian package. Since the Evolve Debian package has a runtime dependency on the Debian Mercurial package, the location of tests/run-tests.py in the Debian Mercurial package could then be hard-wired into Evolve's `debian/rules`. It could probably be installed in the mercurial-common package, at `/usr/share/mercurial/tests/run-tests.py`. Regards, Faheem Mitha -- System Information: Debian Release: 10.0 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/6 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mercurial depends on: ii libc6 2.28-10 ii mercurial-common 5.0-1 ii python 2.7.16-1 ii ucf 3.0038+nmu1 Versions of packages mercurial recommends: ii openssh-client 1:7.9p1-10 Versions of packages mercurial suggests: ii kdiff3 1.7.90-3 pn qct <none> -- no debconf information