summaryrefslogtreecommitdiff
path: root/doc/sources.list.5.xml
Commit message (Collapse)AuthorAgeFilesLines
* Initial support for snapshot servers, apt --snapshot optionJulian Andres Klode2023-05-021-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
|
* Add non-free-firmware component in documentationDavid Kalnischkies2023-01-301-10/+10
| | | | | | This changes a lot of lines technically, but its easy enough to unfuzzy the translations as most of the mentions are examples to be copied literally in translations (sadly po4a isn't clever enough for this).
* Release 2.4.02.4.0Julian Andres Klode2022-02-221-1/+1
|
* Improve the documentation for /etc/apt/keyringsJulian Andres Klode2022-02-221-1/+4
|
* Release 2.3.102.3.10Julian Andres Klode2021-10-181-1/+1
|
* Add support for embedding PGP keys into Signed-By in deb822 sourcesJulian Andres Klode2021-10-181-0/+17
| | | | | | Extend the Signed-By field to handle embedded public key blocks, this allows shipping self-contained .sources files, making it substantially easier to provide third party repositories.
* Release 1.9.0 to experimental1.9.0Julian Andres Klode2019-06-171-1/+1
|
* Perform minor copy-editing on the docsMartin Michlmayr2019-04-041-3/+3
|
* Fix typos encountered while updating de translationChris Leick2018-10-301-1/+1
|
* Support multiple keyrings in sources.list Signed-ByDavid Kalnischkies2018-09-111-12/+17
| | | | | | | A user can specify multiple fingerprints for a while now, so its seems counter-intuitive to support only one keyring, especially if this isn't really checked or enforced and while unlikely mixtures of both should work properly, too, instead of a kinda random behaviour.
* Fix various typos reported by spellcheckersDavid Kalnischkies2018-05-051-1/+1
| | | | | Reported-By: codespell & spellintian Gbp-Dch: Ignore
* mention mirror method in sources.listDavid Kalnischkies2018-04-151-0/+11
| | | | Closes: 679580
* Release 1.6~rc11.6_rc1Julian Andres Klode2018-04-151-1/+1
|
* Revert "mention mirror method in sources.list"Julian Andres Klode2018-04-151-11/+0
| | | | This reverts commit 57a00c50b14a49ed91816e3f4467e0f2e57ee772.
* mention mirror method in sources.listDavid Kalnischkies2018-04-071-0/+11
| | | | Closes: 679580
* 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/+17
| | | | | | | | | | | | | 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
|
* Introduce inrelease-path option for sources.listJulian Andres Klode2018-01-171-0/+9
| | | | | | | | | | | | | | Allow specifying an alternative path to the InRelease file, so you can have multiple versions of a repository, for example. Enabling this option disables fallback to Release and Release.gpg, so setting it to InRelease can be used to ensure that only that will be tried. We add two test cases: One for checking that it works, and another for checking that the fallback does not happen. Closes: #886745
* Release 1.6~alpha61.6_alpha6Julian Andres Klode2018-01-031-1/+1
|
* document https options in new apt-transport-https manpageDavid Kalnischkies2018-01-031-1/+1
| | | | | | 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-9/+7
| | | | | | 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.
* allow multivalue fields in deb822 sources to be foldedDavid Kalnischkies2017-11-191-3/+5
| | | | | | | | | | | | | | | The documentation said "spaces", but there is no real reason to be so strict and only allow spaces to separate values as that only leads to very long lines if e.g. multiple URIs are specified which are again hard to deal with from a user PoV which the deb822 format is supposed to avoid. It also deals with multiple consecutive spaces and strange things like tabs users will surely end up using in the real world. The old behviour on encountering folded lines is the generation of URIs which end up containing all these whitespace characters which tends to mess really bad with output and further processing. Closes: 881875
* Release 1.5~rc31.5_rc3Julian Andres Klode2017-09-101-1/+1
|
* Release 1.5~rc21.5_rc2Julian Andres Klode2017-09-091-1/+1
|
* Release 1.5~rc11.5_rc1Julian Andres Klode2017-08-241-1/+1
|
* Release 1.5~beta21.5_beta2Julian Andres Klode2017-08-171-1/+1
|
* update URI scheme descriptions in sources.list(5)David Kalnischkies2017-07-261-18/+43
|
* 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
|
* Switch documentation from httpredir.d.o to deb.d.oJulian Andres Klode2016-08-291-11/+11
| | | | | The CDN service deb.d.o is more reliable than the http redirector, so switch to it for our examples.
* 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
|
* 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-0/+8
| | | | | | | | 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.
* Release 1.3~exp21.3_exp2Julian Andres Klode2016-06-111-1/+1
|
* Release 1.3~exp11.3_exp1Julian Andres Klode2016-05-111-1/+1
|
* implement Identifier field for IndexTargetsDavid Kalnischkies2016-05-081-6/+7
| | | | | | | | | | | A frontend like apt-file is only interested in a specific set of files and selects those easily via "Created-By". If it supports two locations for those files through it would need to select both and a user would need to know that implementation detail for sources.list configuration. The "Identifier" field is hence introduced which by default has the same value as "Created-By", but can be freely configured – especially it can be used to give two indexes the same identifier.
* support Signed-By in Release files as a sort of HPKPDavid Kalnischkies2016-05-011-2/+4
| | | | | | | | | | | | Users have the option since apt >= 1.1 to enforce that a Release file is signed with specific key(s) either via keyring filename or fingerprints. This commit adds an entry with the same name and value (except that it doesn't accept filenames for obvious reasons) to the Release file so that the repository owner can set a default value for this setting effecting the *next* Release file, not the current one, which provides a functionality similar "HTTP Public Key Pinning". The pinning is in effect as long as the (then old) Release file is considered valid, but it is also ignored if the Release file has no Valid-Until at all.
* support multiple fingerprints in signed-byDavid Kalnischkies2016-05-011-5/+5
| | | | | A keyring file can include multiple keys, so its only fair for transitions and such to support multiple fingerprints as well.
* change debian related entities to a more explicit nameDavid Kalnischkies2016-01-141-8/+8
| | | | Git-Dch: Ignore
* release apt 1.11.1Michael Vogt2015-11-261-1/+1
|
* Fix missing </literal> in sources.list.5.xml pageMichael Vogt2015-11-261-1/+1
| | | | Git-Dch: ignore
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2026-05-12 16:46:55 +0000