apt/doc/apt-get.8.xml, branch 2.7.2

Release 2.7.0

2023-05-02T14:46:14Z

Initial support for snapshot servers, apt --snapshot option

2023-05-02T13:23:14Z

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 options

2023-05-02T13:16:54Z

This runs update before opening the cache and sources.list for installing/upgrading.

Release 2.5.6

2023-02-08T16:09:26Z

Document --allow-insecure-repositories

2023-01-25T11:57:16Z

since --no-allow-insecure-repositories is the default. Signed-off-by: MichaIng

Release 2.5.4

2022-10-31T11:12:04Z

Documentation for autopurge command

2022-10-28T18:36:16Z

Release 2.5.3

2022-09-28T15:34:34Z

doc: Explain that apt-get download ensures package authenticity

2022-08-06T12:43:46Z

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" release

2021-01-08T21:18:01Z