summaryrefslogtreecommitdiff
path: root/doc/apt.conf.5.xml
Commit message (Collapse)AuthorAgeFilesLines
* Release 3.2.03.2.0Julian Andres Klode2026-04-071-1/+1
|
* Document inhibitors (see Bug#112933)Julian Andres Klode2026-03-051-0/+16
|
* Release 3.1.163.1.16Julian Andres Klode2026-02-171-1/+1
|
* Release 3.1.133.1.13Julian Andres Klode2026-01-051-1/+1
|
* Grammar fixesVille Skyttä2025-12-031-3/+3
|
* Release 3.1.13.1.1Julian Andres Klode2025-06-101-1/+1
|
* Revert "doc: Increase visibility of special signs' usage"Julian Andres Klode2025-06-101-1/+1
| | | | | | This reverts commit 66ec0dfad8ac1d4d8646a4734eb9353f3ebc0a91. This creates too much churn in the translation.
* doc: Increase visibility of special signs' usageDaniel Lublin2025-05-291-1/+1
| | | | | | Closes: #310975 Signed-off-by: Daniel Lublin <daniel@lublin.se>
* Release 2.9.222.9.22Julian Andres Klode2025-01-141-1/+1
|
* Remove leftovers from ftp and rsh/ssh methods removalDavid Kalnischkies2025-01-051-52/+0
| | | | References: fd3684cdbc165ceaa635ed19fcbd231f509b0179
* Release 2.9.52.9.5Julian Andres Klode2024-06-131-1/+1
|
* Fix spelling of @SNAPSHOTID@ in apt.conf.5.xmlNoah Meyerhans2024-05-291-1/+1
| | | | Closes: #1072189
* Release 2.9.22.9.2Julian Andres Klode2024-04-221-1/+1
|
* apt.conf(5): Document the APT::Color scopeJulian Andres Klode2024-04-191-0/+39
|
* Release 2.7.142.7.14Julian Andres Klode2024-03-221-1/+1
|
* Remove non-existent Debug::BuildDeps from apt.conf(5)David Kalnischkies2024-03-071-10/+0
| | | | | | | | | The option was removed in 2016 along with the code surrounding it, as the special build-deps specific solver was replaced with reusing our generic solver(s). As such, the normal debug options for these apply here nowadays instead of requiring another one to be set as well. References: a249b3e6fd798935a02b769149c9791a6fa6ef16
* Release 2.7.122.7.12Julian Andres Klode2024-02-201-1/+1
| | | | | I also unfuzzied the translation strings for the 23.10->24.04 apt-key deprecation change.
* Merge branch 'keep-kernel-size' into 'main'Julian Andres Klode2024-02-201-0/+55
|\ | | | | | | | | Configure the amount of kernels to keep See merge request apt-team/apt!324
| * Add documentation of autoremove to apt.conf (5)Wesley Schwengle2024-01-261-0/+55
| | | | | | | | | | | | | | | | | | | | This commit adds documentation for: APT::Protect-Kernels, APT::NeverAutoRemove::*, APT::VersionedKernelPackages. This is to inform users about the newly introduced NeverAutoRemove::KernelCount feature. Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
* | Release 2.7.112.7.11Julian Andres Klode2024-02-131-1/+1
|/
* Release 2.7.62.7.6Julian Andres Klode2023-09-201-1/+1
| | | | Translation template reordering carnage :D
* Release 2.7.42.7.4Julian Andres Klode2023-09-161-1/+1
|
* Initial support for snapshot servers, apt --snapshot optionJulian Andres Klode2023-05-021-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Provide snapshot support for offical Debian and Ubuntu archives. There are two ways to enable snapshots for sources: 1. Add Snapshot: yes to your sources file ([snapshot=yes]). This will allow you to specify a snapshot to use when updating or installing using the --snapshot,-S option. 2. Add Snapshot: ID to your sources files to request a specific snapshot for this source. Snapshots are discovered using Label and Origin fields in the Release file of the main source, hence you need to have updated the source at least once before you can use snapshots. The Release file may also declare a snapshots server to use, similar to Changelogs, it can contain a Snapshots field with the values: 1. `Snapshots: https://example.com/@SNAPSHOTID@` where `@SNAPSHOTID@` is a placeholder that is replaced with the requested snapshot id 2. `Snapshots: no` to disable snapshot support for this source. Requesting snapshots for this source will result in a failure to load the source. The implementation adds a SHADOWED option to deb source entries, and marks the main entry as SHADOWED when a snapshot has been requested, which will cause it to be updated, but not included in the generated cache. The concern here was that we need to keep generating the shadowed entries because the cleanup in `apt update` deletes any files not queued for download, so we gotta keep downloading the main source. This design is not entirely optimal, but avoids the pitfalls of having to reimplement list cleanup. Gaps: - Ubuntu Pro repositories and PPAs are not yet supported.
* Release 2.6.0, the "unhappy bookworm" release2.6.0Julian Andres Klode2023-03-061-1/+1
|
* Release 2.5.32.5.3Julian Andres Klode2022-09-281-1/+1
|
* Release 2.5.22.5.2Julian Andres Klode2022-07-241-1/+1
|
* Release 2.3.72.3.7Julian Andres Klode2021-07-291-1/+1
|
* apt.conf(5): indicate # is also used for commentsDillon Brock2021-06-251-0/+1
| | | | LP: #1309658
* Release 1.9.0 to experimental1.9.0Julian Andres Klode2019-06-171-1/+1
|
* Perform minor copy-editing on the docsMartin Michlmayr2019-04-041-2/+2
|
* Release 1.8.0~alpha31.8.0_alpha3Julian Andres Klode2018-12-181-1/+1
|
* Set PATH=/usr/sbin:/usr/bin:/sbin:/bin when running dpkgJulian Andres Klode2018-12-101-0/+7
| | | | | | | | | This avoids a lot of problems from local installations of scripting languages and other stuff in /usr/local for which maintainer scripts are not prepared. [v3: Inherit PATH during tests, check overrides work] [v2: Add testing]
* Fix typos encountered while updating de translationChris Leick2018-10-301-1/+1
|
* Release 1.7.01.7.0Julian Andres Klode2018-10-071-1/+1
|
* Show APT::Compressor example in apt.conf(5)David Kalnischkies2018-09-271-2/+2
| | | | | | | | | Including a block-element like informalexample in a para is legal, but the documentation of the para tag hints that some processing systems may have difficulties handling this – so lets just move it out of the block and be happy as it is (again?) displayed. Closes: #909712
* Release 1.7.0~rc21.7.0_rc2Julian Andres Klode2018-09-201-1/+1
|
* Release 1.7.0~rc1 to unstable1.7.0_rc1Julian Andres Klode2018-09-181-1/+1
|
* Release 1.7.0~alpha31.7.0_alpha3Julian Andres Klode2018-08-201-1/+1
|
* Release 1.7.0~alpha21.7.0_alpha2Julian Andres Klode2018-07-091-1/+1
|
* Release 1.7.0~alpha11.7.0_alpha1Julian Andres Klode2018-06-251-1/+1
|
* Fix various typos reported by spellcheckersDavid Kalnischkies2018-05-051-1/+1
| | | | | Reported-By: codespell & spellintian Gbp-Dch: Ignore
* Release 1.7.0~alpha0 to experimental1.7.0_alpha0Julian Andres Klode2018-04-181-1/+1
|
* Release 1.6~rc11.6_rc1Julian Andres Klode2018-04-151-1/+1
|
* Release 1.6~beta11.6_beta1Julian Andres Klode2018-02-261-1/+1
|
* Check that Date of Release file is not in the futureJulian Andres Klode2018-02-191-0/+21
| | | | | | | | | | | | | By restricting the Date field to be in the past, an attacker cannot just create a repository from the future that would be accepted as a valid update for a repository. This check can be disabled by Acquire::Check-Date set to false. This will also disable Check-Valid-Until and any future date related checking, if any - the option means: "my computers date cannot be trusted." Modify the tests to allow repositories to be up to 10 hours in the future, so we can keep using hours there to simulate time changes.
* Release 1.6~alpha71.6_alpha7Julian Andres Klode2018-01-181-1/+1
|
* Release 1.6~alpha61.6_alpha6Julian Andres Klode2018-01-031-1/+1
|
* document https options in new apt-transport-https manpageDavid Kalnischkies2018-01-031-28/+5
| | | | | | Same reasoning as with the previous commit for http with the added benefit of moving the hard to discover and untranslated example config into a manpage which could be translated.
* document http options in new apt-transport-http manpageDavid Kalnischkies2018-01-031-64/+0
| | | | | | We had documentation for the http transport in our "catch-all" apt.conf manpage, but it seems benefitial to document transports in their own manpage instead of pushing them all into one.
* Upload 1.5~alpha1 to experimental1.5_alpha1Julian Andres Klode2017-06-281-1/+1
|
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2026-07-18 17:37:49 +0000