apt/debian/tests, branch 1.3_exp2Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.3_exp22016-03-15T17:55:02ZFix bug where the problemresolve can put a pkg into a heisenstate2016-03-15T17:55:02ZMichael Vogtmvo@ubuntu.com2016-03-15T12:13:54Zurn:sha1:0390edd5452b081f8efcf412f96d535a1d959457
The problemresolver will set the candidate version for pkg P back
to the current version if it encounters an impossible to satisfy
critical dependency on P. However it did not set the State of
the package back as well which lead to a situation where P is
neither in Keep,Install,Upgrade,Delete state.
Note that this can not be tested via the traditional sh based
framework. I added a python-apt based test for this.
LP: #1550741
[jak@debian.org: Make the test not fail if apt_pkg cannot be
imported]
tests: Depend on libfile-fcntllock-perl to shut up dpkg-gencontrol2015-12-14T09:00:32ZJulian Andres Klodejak@debian.org2015-12-14T08:58:59Zurn:sha1:369ddff642effc810129c9b28b3fbbc0976c46e9
Ubuntu's autopkgtest server always prints
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe
which is somewhat annoying. Work around that by depending on that
perl stuff for the test suite.
Gbp-Dch: ignore
autopkgtest: use the quiet mode as for travis and co2015-11-28T12:27:06ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-28T00:30:53Zurn:sha1:052a7f48e769c10fb25d5b8adbc71dc085913add
Git-Dch: Ignore
tests: don't use hardcoded port for http and https2015-09-15T08:16:09ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-14T22:33:12Zurn:sha1:6c0765c096ffb4df14169236c865bbb2b10974ae
This allows running tests in parallel.
Git-Dch: Ignore
sync TFRewrite*Order arrays with dpkg and dak2015-05-11T15:22:32ZDavid Kalnischkiesdavid@kalnischkies.de2015-05-09T16:55:41Zurn:sha1:e8fb1cdfdd13e45f2b3abbd57a28b57ae6137f14
dpkg and dak know various field names and order them in their output,
while we have yet another order and have to play catch up with them as
we are sitting between chairs here and neither order is ideal for us,
too.
A little testcase is from now on supposed to help ensureing that we do
not derivate to far away from which fields dpkg knows and orders.
streamline display of --help in all tools2014-11-09T00:26:07ZDavid Kalnischkiesdavid@kalnischkies.de2014-11-08T17:14:46Zurn:sha1:ad7e0941b376d792911f240377094a2e78ca8756
By convention, if I run a tool with --help or --version I expect it to
exit successfully with the usage, while if I do call it wrong (like
without any parameters) I expect the usage message shown with a non-zero
exit.
add gnupg and gnupg2 as test-dependency2014-09-26T22:12:15ZDavid Kalnischkiesdavid@kalnischkies.de2014-09-26T21:09:01Zurn:sha1:98f0d7b3d9d7ed0a5cf11d8f9327a021954816b6
apt can work with both, so it has an or-dependency on them,
but the tests want to play with both of them.
Git-Dch: Ignore
Run autopkgtest tests with "env -i" to avoid pollution from the host env2014-09-03T14:41:29ZMichael Vogtmvo@ubuntu.com2014-09-02T15:30:45Zurn:sha1:74c3db656df9e6cd02c60b8ee3155f9158f13708
Closes: #759655
Use @builddeps@ in the debian/tests/control file2014-07-17T07:59:01ZMichael Vogtmvo@debian.org2014-07-17T07:59:01Zurn:sha1:7ff5ce11ec241311a5520499a6cc09abcbb45307build: Convert from DebianDoc SGML to DocBook XML2014-07-08T11:14:22ZGuillem Joverguillem@debian.org2014-07-02T02:10:37Zurn:sha1:a034d8528bc98e9caf12e024a0d5eeb25f87a500