<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/doc/sources.list.5.xml, branch 2.9.25</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.9.25</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.9.25'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2025-01-14T17:33:49Z</updated>
<entry>
<title>Release 2.9.22</title>
<updated>2025-01-14T17:33:49Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-01-14T17:33:49Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=5429e2324f24a08b8460496e3fe2247545ed45be'/>
<id>urn:sha1:5429e2324f24a08b8460496e3fe2247545ed45be</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Change multi sources.list entry example from FTP to HTTPS</title>
<updated>2025-01-05T22:16:09Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2025-01-05T18:12:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=aa4c681f09f06359c0892329b9e39da77e4f9fda'/>
<id>urn:sha1:aa4c681f09f06359c0892329b9e39da77e4f9fda</id>
<content type='text'>
As the FTP method is dropped it is probably better to use an example
that actually works. We use https here as that requires no other text
changes as there is a HTTPS session to reuse similar to FTP usage ~ that
is the case for our HTTP, too, but the concept of a session isn't
usually known there and servers who close the connection after every
request are more common.
</content>
</entry>
<entry>
<title>Remove leftovers from ftp and rsh/ssh methods removal</title>
<updated>2025-01-05T22:16:09Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2025-01-05T17:16:54Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=213486fc1b9fc0675a35b5c530447b401f9410ff'/>
<id>urn:sha1:213486fc1b9fc0675a35b5c530447b401f9410ff</id>
<content type='text'>
References: fd3684cdbc165ceaa635ed19fcbd231f509b0179
</content>
</entry>
<entry>
<title>Release 2.9.21</title>
<updated>2025-01-01T21:52:23Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2025-01-01T21:00:35Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7b2703aa7dfc21713edd57a3802ee438cc7cd1b6'/>
<id>urn:sha1:7b2703aa7dfc21713edd57a3802ee438cc7cd1b6</id>
<content type='text'>
We updated po/ with libunistring 1.3 as before, but had no
doc changes since the manual update with libunstring 1.2,
so no churn there. Hooray.
</content>
</entry>
<entry>
<title>Remove obsolete references to ftp://ftp.debian.org</title>
<updated>2024-12-28T12:20:50Z</updated>
<author>
<name>Guillem Jover</name>
<email>guillem@debian.org</email>
</author>
<published>2022-03-20T10:34:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=54cb371c19c71cb4ac319fe7566924303379ce63'/>
<id>urn:sha1:54cb371c19c71cb4ac319fe7566924303379ce63</id>
<content type='text'>
Although Debian does not support FTP, this might still be used by other
organizations, or local users, so replaced these instances with an
example.org URL.

Ref: https://lists.debian.org/debian-announce/2017/msg00001.html
</content>
</entry>
<entry>
<title>sources.list(5): Suggest VENDOR.sources for new systems</title>
<updated>2024-12-24T14:01:40Z</updated>
<author>
<name>Simon McVittie</name>
<email>smcv@debian.org</email>
</author>
<published>2024-12-24T13:45:21Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a389a93cc7f3b793b64392b5e52df35204627682'/>
<id>urn:sha1:a389a93cc7f3b793b64392b5e52df35204627682</id>
<content type='text'>
This matches the filename used by default in Ubuntu since Ubuntu 24.04,
and in Debian cloud images and the Debian images provided by docker.io
since Debian 12 (although not currently used in new installations via
debian-installer).

Signed-off-by: Simon McVittie &lt;smcv@debian.org&gt;
</content>
</entry>
<entry>
<title>Release 2.9.17</title>
<updated>2024-12-07T16:14:35Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2024-12-07T16:14:35Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=93325e6c0eedfa16246f7ec0498ed6b3e4c6f553'/>
<id>urn:sha1:93325e6c0eedfa16246f7ec0498ed6b3e4c6f553</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove the apt-key manual page and add documentation to apt-secure</title>
<updated>2024-12-07T14:14:34Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2024-11-23T20:02:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f7f4a4cb5c99f2bfe7a2398c406048c92c9c93b2'/>
<id>urn:sha1:f7f4a4cb5c99f2bfe7a2398c406048c92c9c93b2</id>
<content type='text'>
We move the user configuration section to the top of the manual
page as that is going to be what most are interested in and rewrite
it to cover all the modern ways to configure keys in a succinct
way.
</content>
</entry>
<entry>
<title>Initial support for snapshot servers, apt --snapshot option</title>
<updated>2023-05-02T13:23:14Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2023-02-22T13:14:52Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a19f606aad717fe5c9c69237c3af53feb547115e'/>
<id>urn:sha1:a19f606aad717fe5c9c69237c3af53feb547115e</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Release 2.6.0, the "unhappy bookworm" release</title>
<updated>2023-03-06T12:30:01Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2023-03-06T12:30:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=aa8c9aad81b57da96e8ac7345d0024ee526c7714'/>
<id>urn:sha1:aa8c9aad81b57da96e8ac7345d0024ee526c7714</id>
<content type='text'>
</content>
</entry>
</feed>
