summaryrefslogtreecommitdiff
path: root/doc/apt.conf.5.xml
Commit message (Collapse)AuthorAgeFilesLines
* Release 1.4~beta11.4_beta1Julian Andres Klode2016-11-251-1/+1
|
* Release 1.3.11.3.1Julian Andres Klode2016-10-041-1/+1
|
* Release 1.31.3Julian Andres Klode2016-09-201-1/+1
|
* Release 1.3~rc41.3_rc4Julian Andres Klode2016-09-021-1/+1
|
* Release 1.3~rc31.3_rc3Julian Andres Klode2016-08-301-1/+1
|
* Release 1.3~rc21.3_rc2Julian Andres Klode2016-08-171-1/+1
|
* Release 1.3~rc11.3_rc1Julian Andres Klode2016-08-111-1/+1
| | | | | | | | This commit looks heavy. Most of that comes from the fact that the ordering of files in the translations changed with the switch to CMake. I could have gone the extra mile to figure out the original ordering and replicate it, but I have chosen to re-order everything by file and line number, as that's easier.
* disable explicit configuration of all packages at the endDavid Kalnischkies2016-08-101-77/+7
| | | | | | | | | | | | | | | | | | | With b4450f1dd6bca537e60406b2383ab154a3e1485f we dropped what we calculated here later on and now that we don't need it in the meantime either we can just skip the busy work by default and expect dpkg to do the right thing dropping also our little "last explicit configures" removal trick introduced in b4450f1dd6bca537e60406b2383ab154a3e1485f. This enables the last of a bunch of previously experimental options, some of them existing still, but are very special and hence not really worth documenting anymore (especially as it would need to be rewritten now entirely) which is why the documentation is nearly completely dropped. The order of configuration stanzas in the simulation code changes slightly as it isn't concerning itself with finding the 'right' order, but any order is valid anyhow as long as the entire set happens in the same call.
* releasing package apt version 1.3~pre3+cmake21.3_pre3+cmake2Julian Andres Klode2016-08-061-1/+1
|
* releasing package apt version 1.3~pre3+cmake11.3_pre3+cmake1Julian Andres Klode2016-08-061-1/+1
|
* doc: update path to periodic options scriptJason Travis2016-08-051-1/+1
|
* Release 1.3~pre31.3_pre3Julian Andres Klode2016-08-041-1/+1
|
* Release 1.3~pre21.3_pre2Julian Andres Klode2016-07-081-1/+1
| | | | | Yes, we might still add new features to 1.3 or break some more stuff. Stay tuned!
* Release 1.3~pre11.3_pre1Julian Andres Klode2016-07-071-1/+1
|
* Release 1.3~exp31.3_exp3Julian Andres Klode2016-06-221-1/+1
| | | | Quite a huge churn of new strings.
* add insecure (and weak) allow-options for sources.listDavid Kalnischkies2016-06-221-4/+12
| | | | | | | | Weak had no dedicated option before and Insecure and Downgrade were both global options, which given the effect they all have on security is rather bad. Setting them for individual repositories only isn't great but at least slightly better and also more consistent with other settings for repositories.
* forbid insecure repositories by default expect in apt-getDavid Kalnischkies2016-06-221-16/+13
| | | | | | | | | | | | | | | With this commit all APT-based clients default to refusing to work with unsigned or otherwise insufficently secured repositories. In terms of apt and apt-get this changes nothing, but it effects all tools using libapt like aptitude, synaptic or packagekit. The exception remains apt-get for stretch for now as this might break too many scripts/usecases too quickly. The documentation is updated and extended to reflect how to opt out or in on this behaviour change. Closes: 808367
* implement and document DIRECT for auto-detect-proxyDavid Kalnischkies2016-06-201-7/+12
| | | | | | | There is a subtile difference between an empty setting and "DIRECT" in the configuration as the later overrides the generic settings while the earlier does not. Also, non-zero exitcodes should really be reported as an error rather than silently discarded.
* Release 1.3~exp21.3_exp2Julian Andres Klode2016-06-111-1/+1
|
* fix and document on the fly compressor configDavid Kalnischkies2016-05-271-11/+34
| | | | | | | libapt allows to configure compressors to be used by its system via configuration implemented in 03bef78461c6f443187b60799402624326843396, but that was never really documented and also only partly working, which also explains why the tests weren't using it…
* fix two typos in apt.conf & apt-cache manpageDavid Kalnischkies2016-05-241-1/+1
| | | | | Reported-By: lintian: spelling-error-in-manpage Git-Dch: Ignore
* change debian related entities to a more explicit nameDavid Kalnischkies2016-01-141-1/+1
| | | | Git-Dch: Ignore
* fix 3 typos/omissions in apt.conf(5)Beatrice Torracca2015-12-271-6/+7
| | | | Closes: 809160
* 1.1.6 Christmas releaseJulian Andres Klode2015-12-241-1/+1
|
* Release 1.1.51.1.5Julian Andres Klode2015-12-141-1/+1
|
* Release 1.1.41.1.4Julian Andres Klode2015-12-071-1/+1
|
* use @CHANGEPATH@ as placeholder in changelog URI templatesDavid Kalnischkies2015-12-021-1/+1
| | | | | | | | | This should make it more obvious that CHANGEPATH is a placeholder which apt will replace with a package specific path rather than a string constant. Mail-Reference: <87d1upgvaf.fsf@deep-thought.43-1.org> Mail-Archive: https://lists.debian.org/debian-dak/2015/12/msg00005.html
* update manpage last-modified from git via pre-export hookDavid Kalnischkies2015-11-251-1/+1
| | | | | | | | 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
* add binary-specific options via Binary scopeDavid Kalnischkies2015-11-041-0/+20
| | | | | | Especially with apt now, it can be useful to set an option only for apt and not for apt-get. Using a binary-specific subtree which is merged into the root seems like a simple enough trick to achieve this.
* add by-hash sources.list option and document all of by-hashDavid Kalnischkies2015-09-141-0/+10
| | | | | | | | | | | | This changes the semantics of the option (which is renamed too) to be a yes/no value with the special additional value "force" as this allows by-hash to be disabled even if the repository indicates it would be supported and is more in line with our other yes/no options like pdiff which disable themselves if no support can be detected. The feature wasn't documented so far and hasn't reached a (un)stable release yet, so changing it without trying too hard to keep compatibility seems okay.
* sources.list and indextargets option for pdiffsDavid Kalnischkies2015-08-271-2/+4
| | | | | | | 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.
* Fix typoMichael Vogt2015-08-241-1/+1
| | | | | Thanks: Julian Andres Klode Git-Dch: ignore
* doc/apt.conf.5.xml: document Acquire::EnableSrvRecodsMichael Vogt2015-08-211-0/+9
| | | | Git-Dch: ignore
* document VERSION 2 (and 3) pre-install-pkgs hook interfaceJonathan Nieder2015-08-121-4/+28
| | | | | | | [Commiter: Patch adapted to apply to current version of the manpage and added/moved a few words about Version 3 to make it fit better] Closes: 627188
* remove Dir:: scope limit of RootDir in the documentationDavid Kalnischkies2015-08-121-1/+2
| | | | | | | RootDir doesn't only effect Dir-scope but all FindDir directories, so document it accordingly. Closes: 659387
* add sources.list Check-Valid-Until and Valid-Until-{Max,Min} optionsDavid Kalnischkies2015-08-101-2/+6
| | | | | | | | | | | | | | | | | | These options could be set via configuration before, but the connection to the actual sources is so strong that they should really be set in the sources.list instead – especially as this can be done a lot more specific rather than e.g. disabling Valid-Until for all sources at once. Valid-Until-* names are chosen instead of the Min/Max-ValidTime as this seems like a better name and their use in the wild is probably low enough that this isn't going to confuse anyone if we have to names for the same thing in different areas. In the longrun, the config options should be removed, but for now documentation hinting at the new options is good enough as these are the kind of options you set once across many systems with different apt versions, so the new way should work everywhere first before we deprecate the old way.
* provide a public interface for acquiring changelogsDavid Kalnischkies2015-06-151-0/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Provided is a specialized acquire item which given a version can figure out the correct URI to try by itself and if not provides an error message alongside with static methods to get just the URI it would try to download if it should just be displayed or similar such. The URI is constructed as follows: Release files can provide an URI template in the "Changelogs" field, otherwise we lookup a configuration item based on the "Label" or "Origin" of the Release file to get a (hopefully known) default value for now. This template should contain the string CHANGEPATH which is replaced with the information about the version we want the changelog for (e.g. main/a/apt/apt_1.1). This middleway was choosen as this path part was consistent over the three known implementations (+1 defunct), while the rest of the URI varies widely between them. The benefit of this construct is that it is now easy to get changelogs for Debian packages on Ubuntu and vice versa – even at the moment where the Changelogs field is present nowhere. Strictly better than what apt-get had before as it would even fail to get changelogs from security… Now it will notice that security identifies as Origin: Debian and pick this setting (assuming again that no Changelogs field exists). If on the other hand security would ship its changelogs in a different location we could set it via the Label option overruling Origin. Closes: 687147, 739854, 784027, 787190
* Document ↵Michael Vogt2014-10-131-0/+32
| | | | | | | Acquire{MaxReleaseFileSize,AllowInsecureRepositories,AllowDowngradeToInsecureRepositories} and --no-allow-insecure-repositories Document the new options to restrict loading unauthenticated data into our parsers.
* Merge branch 'debian/sid' into debian/experimentalMichael Vogt2014-09-051-9/+3
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: apt-pkg/acquire-item.cc configure.ac debian/changelog doc/apt-verbatim.ent doc/po/apt-doc.pot doc/po/de.po doc/po/es.po doc/po/fr.po doc/po/it.po doc/po/ja.po doc/po/pt.po po/ar.po po/ast.po po/bg.po po/bs.po po/ca.po po/cs.po po/cy.po po/da.po po/de.po po/dz.po po/el.po po/es.po po/eu.po po/fi.po po/fr.po po/gl.po po/hu.po po/it.po po/ja.po po/km.po po/ko.po po/ku.po po/lt.po po/mr.po po/nb.po po/ne.po po/nl.po po/nn.po po/pl.po po/pt.po po/pt_BR.po po/ro.po po/ru.po po/sk.po po/sl.po po/sv.po po/th.po po/tl.po po/tr.po po/uk.po po/vi.po po/zh_CN.po po/zh_TW.po test/integration/test-ubuntu-bug-346386-apt-get-update-paywall
| * ensure that all docs use all entities filesDavid Kalnischkies2014-08-261-9/+3
| | | | | | | | | | | | | | | | | | Not all are needed for all files at the moment, but the new docbook building hadn't available some of the entities it used as the files weren't correctly copied around in all cases and having the same across the bord makes working with all of them a little easier. Git-Dch: Ignore
* | Merge branch 'debian/sid' into debian/experimentalMichael Vogt2014-07-081-4/+5
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: apt-pkg/deb/deblistparser.cc doc/po/apt-doc.pot doc/po/de.po doc/po/es.po doc/po/fr.po doc/po/it.po doc/po/ja.po doc/po/pl.po doc/po/pt.po doc/po/pt_BR.po po/da.po po/mr.po po/vi.po
| * Improve description how to turn off the cachesCédric Barboiron2014-07-081-4/+5
| | | | | | | | Closes: #753531
* | reenable pipelining via hashsum reordering supportDavid Kalnischkies2014-05-091-3/+3
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | Now that methods have the expected hashes available they can check if the response from the server is what they expected. Pipelining is one of those areas in which servers can mess up by not supporting it properly, which forced us to disable it for the time being. Now, we check if we got a response out of order, which we can not only use to disable pipelining automatically for the next requests, but we can fix it up just like the server responded in proper order for the current requests. To ensure that this little trick works pipelining is only attempt if we have hashsums for all the files in the chain which in theory reduces the use of pipelining usage even on the many servers which work properly, but in practice only the InRelease file (or similar such) will be requested without a hashsum – and as it is the only file requested in that stage it can't be pipelined even if we wanted to. Some minor annoyances remain: The display of the progress we have doesn't reflect this change, so it looks like the same package gets downloaded multiple times while others aren't at all. Further more, partial files are not supported in this recovery as the received data was appended to the wrong file, so the hashsum doesn't match. Both seem to be minor enough to reenable pipelining by default until further notice through to test if it really solves the problem. This therefore reverts commit 8221431757c775ee875a061b184b5f6f2330f928.
* Add new Debug::RunScripts optionMichael Vogt2014-04-011-0/+12
| | | | | This debug option will display all scripts that are run by apts RunScripts and RunScriptsWithPkgs helpers.
* support DEB_BUILD_PROFILES and -P for build profilesDavid Kalnischkies2014-03-131-0/+9
| | | | | | | | | | Inspired by the rest of the patch in 661537, but abstract the parsing of various ways of setting the build profiles more so it can potentially be reused and all apt parts have the same behaviour. Especially config options, cmdline options and environment will not be combined as proposed as this isn't APTs usual behaviour and dpkg doesn't do it either, so one overrides the other as it normally does.
* add a vendor specific file to have configurable entitiesDavid Kalnischkies2013-11-301-0/+2
| | | | | | | manpages sometimes refer to distro-specific things like the name of the package providing the achive-keyring. Having a central place to configure this helps in having it consistent in the manpages and allows to load this info from other places in the buildsystem as well later.
* improve documentation for Acquire::http::Proxy-Auto-Detect (thanks to ↵Michael Vogt2013-10-251-4/+10
| | | | Francesco Poli)
* add Acquire::http::Proxy-Auto-Detect to the apt.conf.5 manpage (closes: 726597)Michael Vogt2013-10-221-0/+8
|
* allow Pre-Install-Pkgs hooks to get info over an FD != stdinDavid Kalnischkies2013-08-161-2/+11
| | | | | | | | | | | | | | | This adds ::InfoFD option alongside the ::Version one to request sending the information to the specified FD, by default it is STDIN as it was the case before. The environment variable APT_HOOK_INFO_FD contains the FD the data is on as a confirmation that the APT version used understood the request. Allowing the hook to choose the FD is needed/helpful e.g. for shellscripts which have a hard time accessing FDs above 9 (as >= 10 are usually used internally by them) Closes: #671728
* merge patch from Daniel Hartwig to Clarify units of Acquire::http::Dl-Limit ↵Michael Vogt2013-08-151-4/+6
| | | | | | | (closes: #705445) Conflicts: debian/changelog
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-02 12:16:00 +0000