summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* tests: refactor printing of the quiet failure headerDavid Kalnischkies2015-09-141-44/+29
| | | | Git-Dch: Ignore
* tests: store msgmsg message for display in fail as wellDavid Kalnischkies2015-09-141-1/+12
| | | | Git-Dch: Ignore
* tests: -y is the default on travis, but not on other ci'sDavid Kalnischkies2015-09-141-2/+2
| | | | Git-Dch: Ignore
* po: Sort domainsJulian Andres Klode2015-09-141-1/+1
| | | | | | This should make things even more predictable. Gbp-Dch: ignore
* Sort pot input filesMichael Vogt2015-09-122-3/+2
| | | | Git-Dch: ignore
* Use xgettext --no-location in make update-potMichael Vogt2015-09-121-0/+2
| | | | | This avoid the large diff we have that is mostly caused by the line numbers changing in the po/pot files.
* releasing package apt version 1.1~exp12Michael Vogt2015-09-1156-26125/+26962
|
* apt-pkg/tagfile.h: Include stdint.h, fixes rdep build failuresJulian Andres Klode2015-09-111-0/+1
|
* Set APT::FTPArchive::DoByHash to false by defaultMichael Vogt2015-09-072-3/+6
| | | | | | | | "apt-ftparchive release" will create the by-hash files if this mode is enabled. This maybe unexpected by existing users so make it a opt-in. Git-Dch: ignore
* Ensure that no by-hash file for "Release/InRelease is written"Michael Vogt2015-09-072-1/+18
| | | | | | Git-Dch: ignore Brown-paperbag: yes Thanks: Donkult
* Add support for writing by-hash dirs in apt-ftparchiveMichael Vogt2015-09-045-2/+219
| | | | | | | | | This option is enabled via the APT::FTPArchive::DoByHash switch. It will also honor the option APT::FTPArchive::By-Hash-Keep that controls how many previous generation of by-hash files should be kept (defaults to 3). Merged from https://github.com/mvo5/apt/tree/feature/apt-ftparchive-by-hash
* avoid triggering the c++11 erase api change on travisDavid Kalnischkies2015-09-021-2/+2
| | | | Git-Dch: Ignore
* tests: collect more details about failed checkdiffsDavid Kalnischkies2015-09-022-51/+30
| | | | Git-Dch: Ignore
* use clock() as source for SRV randomnessDavid Kalnischkies2015-09-014-46/+50
| | | | | | | | | | | | | | | Initializing a random number generator with the time since epoch could be good enough, but reaches its limits in test code as the 100 iterations might very well happen in the same second and hence the seed number is always the same… clock() has a way lower resolution so it changes more often and not unimportant: If many users start the update at the same time it isn't to unlikely the SRV record will be ordered in the same second choosing the same for them all, but it seems less likely that the exact same clock() time has passed for them. And if I have to touch this, lets change a few other things as well to make me and/or compilers a bit happier (clang complained about the usage of a GNU extension in the testcase for example).
* use unusable-for-security hashes for integrity checksDavid Kalnischkies2015-09-015-26/+85
| | | | | | | We want to declare some hashes as not enough for security, so that a user will need --allow-unauthenticated or similar to get data secured only by those hashes, but we can still us these hashes for integrity checks if we got them.
* Consider md5sum no longer a usable hashMichael Vogt2015-09-0111-39/+52
| | | | | 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.
* improve CheckDropPrivsMustBeDisabled furtherDavid Kalnischkies2015-09-013-16/+40
| | | | | | | Various smaller improvements so that the check deals better with already downloaded files, relative paths and other things. Git-Dch: Ignore
* travis: use -q mode to reduce the verbosity greatlyDavid Kalnischkies2015-08-311-2/+2
| | | | Git-Dch: Ignore
* test: show the highlevel test for lowerranking onesDavid Kalnischkies2015-08-311-1/+68
| | | | | | | | | | testsuccess checks the return code, but it does also some autotests based on the command like grepping for dpkg warnings in a apt-get install call – but if this finds something it is just showing the grep command. With this change it will additionally show the first msgtest which in this case will detail the actual apt-get install call. Git-Dch: Ignore
* tests: store msgtest in -q mode for display in msgfailDavid Kalnischkies2015-08-311-52/+112
| | | | | | | | | | | | Not-quiet output is very verbose and with our growing array of tests generates many many lines which e.g. kills the log display in travis-ci and obscures failures and uncatched output in a wall of details. The -q mode fixed this by callapsing passed tests to a single P and now with some rework we can even get failures properly displayed with the message from msgtest. Git-Dch: Ignore
* fix some unused parameter/variable warningsDavid Kalnischkies2015-08-314-18/+17
| | | | | Reported-By: gcc Git-Dch: Ignore
* tavis: run testcases a second time, but as rootDavid Kalnischkies2015-08-313-16/+24
| | | | Git-Dch: Ignore
* do delay the test for http, too, to make it more reliableDavid Kalnischkies2015-08-311-4/+5
| | | | | | | | | The file method was already slowed down and somehow I thought I had done the same for http, but it turns out that I didn't. Giving it the same delay as file should help in making this test slower and therefore more likely to successfully test what it is supposed to test. Git-Dch: Ignore
* remove Christian Perrier from Uploaders as requestedDavid Kalnischkies2015-08-311-1/+1
| | | | | Closes: #783337 Thanks: Christian for all the l10n, code & social contributions!
* Czech program translation updateMiroslav Kure2015-08-311-75/+83
| | | | Closes: 797329
* fix valid-until-min typo in sources.list(5)David Kalnischkies2015-08-311-1/+1
| | | | Git-Dch: Ignore
* if file is inaccessible for _apt, disable privilege drop in acquireDavid Kalnischkies2015-08-318-66/+60
| | | | | | | | | | | | | | | We had a very similar method previously for our own private usage, but with some generalisation we can move this check into the acquire system proper so that all frontends profit from this compatibility change. As we are disabling a security feature here a warning is issued and frontends are advised to consider reworking their download logic if possible. Note that this is implemented as an all or nothing situation: We can't just (not) drop privileges for a subset of the files in a fetcher, so in case you have to download some files with and some without you need to use two fetchers.
* ignore for _apt inaccessible TMPDIR in pkgAcqChangelogDavid Kalnischkies2015-08-313-5/+31
| | | | | | | | | | | | Using libpam-tmpdir caused us to create our download tmp directory in root's private tmp before changing to _apt, which wouldn't have access to it. By extending our GetTempDir method with an optional wrapper changing the effective user, we can test if a given user can access the directory and ignore TMPDIR if not instead of ignoring TMPDIR completely. Closes: 797270
* detect and deal with indextarget duplicatesDavid Kalnischkies2015-08-306-3/+160
| | | | | | | | | | | | | | | Multiple targets downloading the same file is bad™ as it leads us to all sorts of problems like the acquire system breaking or simply a problem of which settings to use for them. Beside that this is most likely a mistake and silently ignoring it doesn't help the user realizing his mistake… On the other hand, we have 'duplicates' which are 'created' by how we create indextargets, so we have to prevent those from being created to but do not emit a warning for them as this is an implementation detail. And then, there is the absolute and most likely user mistake: Having the same target(s) activated in multiple entries.
* implement $(NATIVE_ARCHITECTURE) substvar for indextargetsDavid Kalnischkies2015-08-302-0/+8
|
* try xz instead of bz2 first for compressed filesDavid Kalnischkies2015-08-293-62/+62
| | | | | | | | | | | | | | | | | | xz has pretty much won "the compressor war" and e.g. the Debian archive doesn't even distribute bz2 anymore in favor of 'xz' and 'gz', so by changing the default order we have a more realistic --print-uris behavior as it will always show the first compressor. In practice this effects repositories without a Release file (very bad, we don't want to support them anymore anyhow) as xz will be tried before bz2 now [which is probably not available, but so might be bz2…] AND repositories which provide both, bz2 and xz (which isn't too common) in sofar as apt will now download xz instead of bz2. Users with special needs can stick with bz2 as first compressor tried with Acquire::CompressionTypes::Order:: "bz2"; (see man apt.conf) – but users with special needs usually prefer "gz" anyhow, so the realworld change is expected to be very low.
* implement indextargets option 'DefaultEnabled'David Kalnischkies2015-08-296-29/+122
| | | | | | | | | | | Some targets like Contents-udeb are special-needs targets. Shipping the configuration snippet for them is okay, but they shouldn't be downloaded by default. Forcing the user to enable targets by uncommenting targets is wrong and this would still not really solve the problem completely as even if you want to download some -udebs it will probably not be for all sources you have enabled, so having the possibility of disabling a target by default, but giving the user the option to enable it on a per-source entry basis is better.
* use c++11 algorithms to avoid strange compiler warningsDavid Kalnischkies2015-08-294-85/+61
| | | | | | | | | | | | | Nobody knows what makes the 'unable to optimize loop' warning to appear in the sourceslist minus-options parsing, especially if we use a foreach loop, but we can replace it with some nice c++11 algorithm+lambda usage, which also helps in making even clearer what happens here. And as this would be a lonely change, lets do it for a few more loops as well where I might or might not have seen the warning at some point in time, too. Git-Dch: Ignore
* implement PDiff patching for compressed filesDavid Kalnischkies2015-08-289-155/+281
| | | | | | | | | | | | | | | | | | Some additional files like 'Contents' are very big and should therefore kept compressed on the disk, which apt-file did in the past. It also implemented pdiff patching of these files by un- and recompressing these files on-the-fly, with this commit we can do the same – but we can do this in both pdiff patching styles (client and server merging) and secured by hashes. Hashes are in so far slightly complicated as we can't compare the hashes of the compressed files as we might compress them differently than the server would (different compressor versions, options, …), so we must compare the hashes of the uncompressed content. While this commit has changes in public headers, the classes it changes are marked as hidden, so nobody can use them directly, which means the ABI break is internal only.
* auto-prefix $(SITE) for indextargets Description fieldDavid Kalnischkies2015-08-271-10/+10
| | | | | | | | This updates the documentation for a change which actually happened in c2a4a8dded2dfb56dbcab9689b6cb4b96c9999b6 already. The acquire system expects the $(SITE) to be there (e.g. for mirror rewriting) so we are better of prefixing it automatically than giving frontends the chance to forget it. There is no point in not showing $(SITE) first anyway.
* sources.list and indextargets option for pdiffsDavid Kalnischkies2015-08-2710-9/+62
| | | | | | | Disabling pdiffs can be useful occasionally, like if you have a fast local mirror where the download doesn't matter, but still want to use it for non-local mirrors. Also, some users might prefer it to only use it for very big indextargets like Contents.
* Release 1.11~exp111.1.exp11Julian Andres Klode2015-08-2756-28274/+28458
|
* Fix test-security-no-remote-statusJulian Andres Klode2015-08-271-3/+3
| | | | Gbp-Dch: ignore
* Do not parse Status fields from remote sourcesJulian Andres Klode2015-08-275-1/+56
| | | | | | | | | | | This could allow an attacker to mark a package as installed in a remote package index, as long as the package was not listed in the dpkg status file. This way, an attacker could force the installation of a package during a dist-upgrade, by providing two packages in an index, an older marked as installed, and a newer - apt would "upgrade" to the newer version.
* Merge branch 'feature/extractar-filefd' into debian/experimentalJulian Andres Klode2015-08-274-64/+61
|\
| * Use compressor support from FileFd for ExtractTar instead of programsJulian Andres Klode2015-08-271-56/+11
| | | | | | | | This way we do not depend on the decompressor programs anymore.
| * Add test for using ExtractTar on compressed filesJulian Andres Klode2015-08-272-2/+43
| | | | | | | | Git-Dch: ignore
| * Always close compressed files in FileFdJulian Andres Klode2015-08-271-6/+7
| | | | | | | | | | | | | | We dup() the file descriptor when opening compressed files, so we always need to close the dup()ed one. Furthermore, not unsetting the d-pointer causes issues when running OpenDescriptor() multiple times on the same file descriptor.
* | install: Set a local deb as the candidate for that packageJulian Andres Klode2015-08-272-0/+30
| | | | | | | | | | This ensures that we can install .deb files that are not the candidate for a given package.
* | cacheset: Prefer the depcache over the policy againJulian Andres Klode2015-08-271-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | By preferring the policy over the depcache, we ignore any changes we made in the depcache, which makes it impossible for code to change the candidate used here. This basically reverts commit 2fbfb111312257fa5fc29b0c2ed386fb712f960e: prefer the Policy if it is built instead of the DepCache and if DepCache is not available as fallback built the Policy But it also cleans the code up a bit, by removing one level of nesting.
* | debian/rules: Only do parallel build if specified in DEB_BUILD_OPTIONSJulian Andres Klode2015-08-271-0/+4
| | | | | | | | | | | | It was not nice to use 2 * number of cores in all cases. Thanks: Jakub Wilk for the suggestion
* | allow explicit dis/enable of IndexTargets in sources optionsDavid Kalnischkies2015-08-274-2/+93
| | | | | | | | | | | | | | While Target{,-Add,-Remove} is available for configuring IndexTargets already, allow Targets to be mentioned explicitely as yes/no options as well, so that the Target 'Contents' can be disabled via 'Contents: no' as well as 'Target-Remove: Contents'.
* | not all targets are deb-src targetsDavid Kalnischkies2015-08-271-1/+1
| | | | | | | | | | | | | | Sometimes too much refactoring can have bad effects. Thanks: Niels Thykier for reporting on IRC Git-Dch: Ignore
* | use always priv-dropping for changelog download as rootDavid Kalnischkies2015-08-273-8/+10
| | | | | | | | | | | | | | First of, the temporary directory we download the changelog to needs to be owned by _apt, but that also means that we don't need to check if we could/should drop privs as the download happens to a dedicated tempdir and only after that it is moved to its final location by a privileged user.
* | fix various typos reported by codespellDavid Kalnischkies2015-08-2718-59/+59
| | | | | | | | Reported-By: codespell
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2026-10-17 10:08:22 +0000