apt/apt-private, branch 1.1.3

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

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.

Revert "Revert "appease adequate with some weak symbols for -private""

2015-11-28T21:36:25Z

This reverts commit 7ac9386cb6e272625490fcf3e8183b45e28bbc43.

Revert "appease adequate with some weak symbols for -private"

2015-11-28T21:27:15Z

This reverts commit 28f24d3dad1844af316337d565ba2ebc11c8ce97. This fails on Ubuntu as they build with -Bsymbolic-functions.

appease adequate with some weak symbols for -private

2015-11-27T13:02:49Z

Closes: #806422

show potentially arch-qualified fullname in 'apt show'

2015-11-21T17:15:22Z

We do not show the architecture as a dedicated field as this is rather technical information, but as packagename it makes sense to show the architecture as other part of apt will refer to it in this way.

apply various suggestions made by cppcheck

2015-11-05T11:21:33Z

Reported-By: cppcheck Git-Dch: Ignore

drop privileges in copy:// method as we do for file://

2015-11-05T11:21:33Z

Continueing on the track of dropping privileges in all methods, lets drop it in copy, too, as the reasoning for it is very similar to file and the interaction between the too quiet interesting as copy kinda surfed as a fallback for file not being able to read the file. Both now show a better error message as well as it was previously claiming to have a hashsum mismatch, given that it couldn't read the file. Git-Dch: Ignore