apt, branch 1.1.3

release 1.1.3

2015-11-30T08:08:24Z

Git-dch: ignore

add apt-utils Depends apt (= ${binary:Version})

2015-11-29T16:55:02Z

As we ship some tools in apt-utils which depend on our private library we have to ensure that apt-utils depends on a proper apt version. An exact version is probably a bit much, but the simplest way out.

drop some needlessly public declarations in libapt-private

2015-11-29T16:00:11Z

Git-Dch: Ignore

move 'unmet' handling into libapt-private

2015-11-29T14:49:55Z

Git-Dch: Ignore

accept ../ on the cmdline as start for a deb file as well

2015-11-29T13:32:29Z

Regression of 14341a7ee1ca3dbcdcdbe10ad19b947ce23d972d. Reported-By: Julian Andres Klode

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

use function pointers instead of weak symbols for cmdline parsing

2015-11-29T12:12:38Z

Passing function pointers around while working on this was very icky, but if weak symbols are too much to ask for… Reverts "do not use "-Wl,-Bsymbolic-functions" during the build to avoid breakage" aka a5fc9be36211a290a7abc3ca2a8bf98943bc1f57.

doc: VerifyFile checks all hashes instead of best only

2015-11-29T00:08:37Z

The implementation changed in 495b7a615a2d8f485beadf88c6ed298f5bbe50c2 Git-Dch: Ignore Reported-By: Julian Andres Klode

Release 1.1.2

2015-11-28T21:49:07Z