summaryrefslogtreecommitdiff
path: root/doc/apt-get.8.xml
Commit message (Collapse)AuthorAgeFilesLines
* Release 2.7.82.7.8Julian Andres Klode2024-01-081-1/+1
|
* Revert "Merge branch 'distclean-doc-an-test' into 'main'"Julian Andres Klode2024-01-081-7/+1
| | | | | This reverts commit 86e6eace1d50527b5a2396290acd1db819b13e26, reversing changes made to 6e43eef9ca8250eb561f2c9af2f4890d674f3911.
* Test and document 'dist-clean'Gábor Németh2023-12-151-1/+7
|
* Release 2.7.32.7.3Julian Andres Klode2023-08-021-1/+1
|
* Add apt-patterns(7) to apt{,-cache,-get} SEE ALSO sectionsDavid Kalnischkies2023-07-261-1/+1
| | | | | | | While we are at it fix the mislabeling as (5) in some places and unfuzzy the translations. Reported-By: Enrico Zini on IRC
* Release 2.7.02.7.0Julian Andres Klode2023-05-021-1/+1
|
* Initial support for snapshot servers, apt --snapshot optionJulian Andres Klode2023-05-021-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Add apt install,upgrade,... -U,--update optionsJulian Andres Klode2023-05-021-0/+14
| | | | | This runs update before opening the cache and sources.list for installing/upgrading.
* Release 2.5.62.5.6Julian Andres Klode2023-02-081-1/+1
|
* Document --allow-insecure-repositoriesMichaIng2023-01-251-5/+5
| | | | | since --no-allow-insecure-repositories is the default. Signed-off-by: MichaIng <micha@dietpi.com>
* Release 2.5.42.5.4Julian Andres Klode2022-10-311-1/+1
|
* Documentation for autopurge commandquazgar2022-10-281-0/+6
|
* Release 2.5.32.5.3Julian Andres Klode2022-09-281-1/+1
|
* doc: Explain that apt-get download ensures package authenticityPovilas Kanapickas2022-08-061-1/+2
| | | | | | | | | | | The documentation currently does not specify whether `apt-get download` verifies the authenticity of downloaded packages or not. The underlying code does verify the authenticity of packages as usual and would fail if the package signature is invalid. Therefore it makes sense to make this guarantee explicit in the documentation, because without it security-conscious users will likely want to recheck the signatures or checksums manually which is not necessary in this case and just wastes time.
* Release 2.1.16 - "Happy build-essential freeeze" release2.1.16Julian Andres Klode2021-01-081-1/+1
|
* Implement update --error-on=anyJulian Andres Klode2021-01-081-0/+4
| | | | | | | | | | | People have been asking for a feature to error out on transient network errors for a while, this gives them one while keeping the door open for other modes we need, such as --error-on=no-success which we need to determine when to retry the daily update job. Closes: #594813 (and a whole bunch of duplicates...)
* Release 2.1.82.1.8Julian Andres Klode2020-08-041-1/+1
|
* Support marking all newly installed packages as automatically installedNicolas Schier2020-06-081-0/+10
| | | | | | | Add option '--mark-auto' to 'apt install' that marks all newly installed packages as automatically installed. Signed-off-by: Nicolas Schier <nicolas@fjasle.eu>
* Release 1.9.61.9.6Julian Andres Klode2020-01-151-1/+1
|
* apt(8): Disable regular expressions and fnmatchJulian Andres Klode2020-01-151-1/+4
| | | | | This is the first step. Next step will be to add warnings to apt-get and then remove support there as well.
* Release 1.9.0 to experimental1.9.0Julian Andres Klode2019-06-171-1/+1
|
* doc/apt-get.8.xml: Fix typo in satisfy command descriptionJulian Andres Klode2019-06-121-1/+1
| | | | Gbp-Dch: ignore
* Introduce apt satisfy and apt-get satisfyJulian Andres Klode2019-06-111-0/+13
| | | | | | | | | | | | | | | | | | Allow to satisfy dependency strings supplied on the command line, optionally prefixed with "Conflicts:" to satisfy them like Conflicts. Build profiles and architecture restriction lists, as used in build dependencies, are supported as well. Compared to build-dep, build-essential is not installed automatically, and installing of recommended packages follows the global default, which defaults to yes. Closes: #275379 See merge request apt-team/apt!63
* Fix various typos in the documentationJakub Wilk2019-02-101-2/+2
|
* Release 1.8.0~rc11.8.0_rc1Julian Andres Klode2019-02-041-1/+1
|
* Add a "reinstall" command as an alias for "install --reinstall".Josh Triplett2019-01-271-0/+4
| | | | aptitude has a similar "reinstall" command for precedent.
* Release 1.8.0~alpha11.8.0_alpha1Julian Andres Klode2018-11-121-1/+1
|
* Merge branch 'master' into 'master'Julian Andres Klode2018-10-141-1/+6
|\ | | | | | | | | apt-get.8: mention --only-source in 'source' and 'build-dep' description See merge request apt-team/apt!24
| * clarificationDamyan Ivanov2018-09-121-3/+4
| | | | | | | | | | do not suggest that 'source' and 'build-dep' arguments are binary package names only
| * apt-get.8: mention --only-source in 'source' and 'build-dep' descriptionDamyan Ivanov2018-08-091-1/+5
| |
* | Release 1.7.01.7.0Julian Andres Klode2018-10-071-1/+1
| |
* | 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
|
* 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
|
* document Acquire::AllowReleaseInfoChange without extra sDavid Kalnischkies2018-04-071-1/+1
| | | | Reported-By: Mattia Rizzolo on IRC
* Release 1.5~rc31.5_rc3Julian Andres Klode2017-09-101-1/+1
|
* Release 1.5~rc21.5_rc2Julian Andres Klode2017-09-091-1/+1
|
* doc: correct '--allow-releaseinfo-change-*' typosChristos Trochalakis2017-09-011-2/+2
| | | | Closes: #873914
* Release 1.5~rc11.5_rc1Julian Andres Klode2017-08-241-1/+1
|
* Release 1.5~beta21.5_beta2Julian Andres Klode2017-08-171-1/+1
|
* doc: Add '--allow-unauthenticated' to '--force-yes'Dominik2017-07-271-1/+5
|
* Upload 1.5~alpha4 to experimental1.5_alpha4Julian Andres Klode2017-06-301-1/+1
|
* Upload 1.5~alpha3 to experimental1.5_alpha3Julian Andres Klode2017-06-301-1/+1
|
* Upload 1.5~alpha2 to experimental1.5_alpha2Julian Andres Klode2017-06-291-1/+1
|
* Upload 1.5~alpha1 to experimental1.5_alpha1Julian Andres Klode2017-06-281-1/+1
|
* error in update on Release information changesDavid Kalnischkies2017-06-281-0/+17
| | | | | | | | | | | The value of Origin, Label, Codename and co can be used in user configuration from apts own pinning to unattended upgrades. A repository changing this values can therefore have serious effects on the behaviour of apt and other tools using these values. In a first step we will generate error messages for these changes now explaining the need for explicit confirmation and provide config options and commandline flags to accept them.