summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* add apt-utils Depends apt (= ${binary:Version})David Kalnischkies2015-11-291-1/+1
| | | | | | 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-privateDavid Kalnischkies2015-11-2915-32/+29
| | | | Git-Dch: Ignore
* move 'unmet' handling into libapt-privateDavid Kalnischkies2015-11-293-103/+131
| | | | Git-Dch: Ignore
* accept ../ on the cmdline as start for a deb file as wellDavid Kalnischkies2015-11-292-2/+6
| | | | | | Regression of 14341a7ee1ca3dbcdcdbe10ad19b947ce23d972d. Reported-By: Julian Andres Klode <jak@debian.org>
* tests: fix typos, correct helpmsgs and test testsDavid Kalnischkies2015-11-293-7/+12
| | | | Git-Dch: Ignore
* do not override exact targetrelease matches with lesser matchesAndreas Cadhalpun2015-11-292-7/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 parsingDavid Kalnischkies2015-11-2914-25/+21
| | | | | | | | 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 onlyDavid Kalnischkies2015-11-291-1/+1
| | | | | | | | The implementation changed in 495b7a615a2d8f485beadf88c6ed298f5bbe50c2 Git-Dch: Ignore Reported-By: Julian Andres Klode <jak@debian.org>
* Release 1.1.21.1.2Julian Andres Klode2015-11-2857-58/+292
|
* Revert "Revert "appease adequate with some weak symbols for -private""Julian Andres Klode2015-11-283-2/+8
| | | | This reverts commit 7ac9386cb6e272625490fcf3e8183b45e28bbc43.
* do not use "-Wl,-Bsymbolic-functions" during the build to avoid breakageMichael Vogt2015-11-281-1/+4
|
* Revert "appease adequate with some weak symbols for -private"Julian Andres Klode2015-11-283-8/+2
| | | | | | This reverts commit 28f24d3dad1844af316337d565ba2ebc11c8ce97. This fails on Ubuntu as they build with -Bsymbolic-functions.
* disable privilege dropping for rsh/ssh method by defaultDavid Kalnischkies2015-11-281-0/+4
| | | | | | | | | ssh expects various configuration bits to be usable like known hosts, possibly keys and co. Setting this up needs some user work for probably not a whole lot of benefits, so instead of forcing it upon users on upgrade disable dropping for it by default. Closes: 806511
* fix program name detection in rsh methodDavid Kalnischkies2015-11-282-6/+6
| | | | Regression intoduced in 23e64f6d0facf9610c1042326ad9850e071e8349
* disable privilege-drop verification by default as fakeroot trips over itDavid Kalnischkies2015-11-282-42/+62
| | | | | | | | | | | | | Dropping privileges is an involved process for code and system alike so ideally we want to verify that all the work wasn't in vain. Stuff designed to sidestep the usual privilege checks like fakeroot (and its many alternatives) have their problem with this through, partly through missing wrapping (#806521), partly as e.g. regaining root from an unprivileged user is in their design. This commit therefore disables most of these checks by default so that apt runs fine again in a fakeroot environment. Closes: 806475
* show the group we failed to drop via setgroupsDavid Kalnischkies2015-11-281-6/+11
| | | | | | | | This also deals with the unlikely case of groups being mentioned multiple times or if the effective group isn't mentioned at all. In practice, it is a debugging aid through like for #806475. Git-Dch: Ignore
* autopkgtest: use the quiet mode as for travis and coDavid Kalnischkies2015-11-281-1/+1
| | | | Git-Dch: Ignore
* tests: use id to get user/group instead of environmentDavid Kalnischkies2015-11-281-2/+2
| | | | | | | debci seems to have a cleaner environment now and even if not we could never guess nogroup, so figure it out properly via 'id'. Git-Dch: Ignore
* ignore deprecated method calls in deprecated methodDavid Kalnischkies2015-11-271-0/+2
| | | | Git-Dch: Ignore
* outsmart gcc -O3 over-optimization in pkgCdrom::FindPackagesDavid Kalnischkies2015-11-272-3/+5
| | | | | | | | Seems like a simpler workaround than forcing a lower optimization level just for this for all of apt. See also: https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1473674
* update arch-specific symbols in symbols fileDavid Kalnischkies2015-11-271-11/+17
| | | | Git-Dch: Ignore
* ./prepare-release pre-export1.1.1Michael Vogt2015-11-2713-14/+14
|
* prepare 1.1.1 releaseMichael Vogt2015-11-271-0/+13
|
* say 'master' is default branch in README, tooDavid Kalnischkies2015-11-271-1/+1
| | | | Git-Dch: Ignore
* add messages to our deprecation warnings in libaptDavid Kalnischkies2015-11-2729-111/+101
| | | | Git-Dch: Ignore
* appease adequate with some weak symbols for -privateDavid Kalnischkies2015-11-273-2/+8
| | | | Closes: #806422
* use pre-build hook to check for pre-export executionDavid Kalnischkies2015-11-272-6/+21
| | | | Git-Dch: Ignore
* debian/gbp.conf: point debian-branch to masterMichael Vogt2015-11-271-1/+1
| | | | Git-Dch: ignore
* Check if the Apt::Sandbox::User exists in CheckDropPrivsMustBeDisabled()Michael Vogt2015-11-271-0/+4
| | | | | | | | If it does not exist disabled priv dropping as there is nothing we can drop to. This will unblock people with special chroots or systems that deleted the "_apt" user. Closes: #806406
* Deal with killed acquire methods properly instead of hangingMichael Vogt2015-11-272-6/+24
| | | | | | | | | | | | This fixes a regression caussed by commit 95278287f4e1eeaf5d96749d6fc9bfc53fb400d0 that moved the error detection of RunFds() later into the loop. However this broke detecting issues like dead acquire methods. Instead of relying on the global error state (which is bad) we now pass a boolean value back from RunFds() and break on false. Closes: #806406
* release apt 1.11.1Michael Vogt2015-11-2614-114/+108
|
* Do not run pre*export* functions in the pre*build* hookMichael Vogt2015-11-261-1/+2
| | | | | | | Unfortunately it seems like git-buildpackage does not have a pre-export hook so the hook is disabled for now. Git-Dch: ignore
* Fix missing </literal> in sources.list.5.xml pageMichael Vogt2015-11-261-1/+1
| | | | Git-Dch: ignore
* Merge remote-tracking branch 'donkult/debian/experimental' into ↵Michael Vogt2015-11-261-9/+8
|\ | | | | | | debian/experimental
| * reword Trusted paragraph in sources.list(5)Justin B Rye2015-11-261-9/+8
| | | | | | | | Git-Dch: Ignore
* | Run ./prepare-release pre-exportMichael Vogt2015-11-2556-1947/+1897
| |
* | Prepare release 1.1~exp17Michael Vogt2015-11-251-0/+10
|/
* update manpage last-modified from git via pre-export hookDavid Kalnischkies2015-11-2514-15/+23
| | | | | | | | Never updating this information is wrong, updating it automatically isn't super correct either, but it seems conventional to have it and updating it more often than needed seems better than updating it never. Git-Dch: Ignore
* enforce a slightly more sensible default headerDavid Kalnischkies2015-11-2512-1124/+1445
| | | | | | | | | | | | In 12f7536 I chose to opt for a slightly better text which avoids assigning copyright to the FSF (not because it would be wrong to do it, but is usually not what the contributor intended, but just the default. xgettext has a --foreign flag for avoiding the copyright, but po4a hasn't and an empty copyright-holder doesn't work either, so this little rework of files with sed and cat. Git-Dch: Ignore
* typo: run s#frontend#front-end# on all of src:aptDavid Kalnischkies2015-11-2515-86/+86
| | | | | | The manpages were fixed by Justin B Rye, lets deal with the rest now. Git-Dch: Ignore
* review sources.list(5) manpageJustin B Rye2015-11-251-59/+61
|
* review apt-secure(8) manpageJustin B Rye2015-11-251-12/+11
|
* review apt-mark(8) manpageJustin B Rye2015-11-251-10/+10
|
* review apt(8) manpageJustin B Rye2015-11-251-19/+19
|
* slightly rephrase notice shown for insecure repositoriesJustin B Rye2015-11-254-6/+6
| | | | Git-Dch: Ignore
* releasing package apt version 1.1~exp161.1_exp16Michael Vogt2015-11-241-0/+24
|
* show potentially arch-qualified fullname in 'apt show'David Kalnischkies2015-11-212-9/+27
| | | | | | 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.
* review of new/changed translatable program stringsJustin B Rye2015-11-2171-507/+508
| | | | | Reference mail: https://lists.debian.org/debian-l10n-english/2015/11/msg00006.html
* do not sent Last-Modified if we expect a changed fileDavid Kalnischkies2015-11-212-5/+13
| | | | | | | | | | | | | | | | | | | | In 8d041b4f we made apt figure out based on the last Release file it has if it should request a file or not given that the hashes changed or not. So if we have a last Release file and do a request, do not sent a Last-Modified header as we expect a change so much that a non-change would indeed be an error. The Last-Modified header is therefore at best ignored by the server, so sending it is just wasted effort. In the worst case as time is a fragile thing the server decides against sending us an update with the idea that we already have the latest content, which we know for a fact that we haven't. Given that we sent less information to the server our request is on its own also less identifiable as coming from a returning or new user. The disadvantage is that if we end up getting an old index file after getting a new Release file from another mirror the old mirror will not be able to tell us 'Hit', but instead sends us the complete file we discard, but both lets us end up with the same error class in the end, so the difference isn't big in practice.
* fix a few typos in code-comments/apt manpageDavid Kalnischkies2015-11-2013-24/+24
| | | | | Reported-By: codespell Git-Dch: Ignore
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-01 21:25:16 +0000