apt/test/integration/test-apt-get-source, branch 1.2_exp1

tests: support spaces in path and TMPDIR

2015-12-19T22:04:34Z

This doesn't allow all tests to run cleanly, but it at least allows to write tests which could run successfully in such environments. Git-Dch: Ignore

tests: fix typos, correct helpmsgs and test tests

2015-11-29T13:05:38Z

Git-Dch: Ignore

do not override exact targetrelease matches with lesser matches

2015-11-29T12:36:28Z

The relevant testcases are in test/integration/test-apt-get-source. There is a test for #731853 that is supposed to "ensure that apt will pick the higher version number" of 0.0.1 (stable) and 0.1 (stable). However, this works by pure chance, as simply reversing the order of the two insertsource lines makes the test fail. So #731853 isn't really fixed, yet. Actually, that's related to the problem I reported, as the underlying issue for both is the same: In the FindSrc function apt chooses a new 'best hit', if either * there is a target release and it matches the release of the package, * or the version of the package is higher than the last best hit. Consider having 1.0 (stable), 2.0 (unstable) and 1.5 (unstable), in this order. Looking for the version in stable, apt first selects 1.0, because the release matches the target release, but then subsequently selects 2.0, because the version is higher. Looking for the version in unstable, apt first selects 2.0, because the release matches the target release, but then subsequently selects 1.5, because the release also matches the target release. The correct way would be to choose a new 'best hit', if either * there is a target release and it matches the release of the package, * or there is no target release and the version is higher than the last best hit. Closes: 746412 Mail-Reference: <565A604B.7090104@googlemail.com> Mail-Archive: https://lists.debian.org/debian-devel/2015/11/msg00470.html

implement apt-get source msg 'Please use: $vcs' for git

2015-09-14T13:22:18Z

A bit unfair that only Bzr had this message. Lets at least print it for git as well with the option of adding more later without string changes.

Consider md5sum no longer a usable hash

2015-09-01T09:29:49Z

The md5sum hash is broken since some time and we should no longer consider it a usable hash. Also update the tests to reflect this.

tests: check apt-get source release name switching with -t

2015-08-27T09:24:07Z

Git-Dch: Ignore

condense parallel requests with the same hashes to one

2015-06-15T21:35:55Z

It shouldn't be too common, but sometimes people have multiple mirrors in the sources or otherwise repositories with the same content. Now that we gracefully can handle multiple requests to the same URI, we can also fold multiple requests with the same expected hashes into one. Note that this isn't trying to find oppertunities for merging, but just merges if it happens to encounter the oppertunity for it. This is most obvious in the new testcase actually as it needs to delay the action to give the acquire system enough time to figure out that they can be merged.

test exitcode as well as string equality

2015-03-16T17:01:54Z

We use test{success,failure} now all over the place in the framework, so its only consequencial to do this in the situations in which we test for a specific output as well. Git-Dch: Ignore

reenable support for -s (and co) in apt-get source

2014-10-20T08:37:46Z

The conversion to accept only relevant options for commands has forgotten another one, so adding it again even through the usecase might very well be equally good served by --print-uris. Closes: 742578

Fix typos in documentation (codespell)

2014-02-22T17:34:33Z