<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/doc, branch 3.1.2</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=3.1.2</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=3.1.2'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2025-06-10T19:16:43Z</updated>
<entry>
<title>Release 3.1.2</title>
<updated>2025-06-10T19:16:43Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2025-06-10T19:16:43Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=63919b628a9bf386136f708f06c1a8a7d4f09fca'/>
<id>urn:sha1:63919b628a9bf386136f708f06c1a8a7d4f09fca</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Release 3.1.1</title>
<updated>2025-06-10T16:06:26Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2025-06-10T16:05:29Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f9b5f49fe6030fc028bc93debf856d1ae75ca7ab'/>
<id>urn:sha1:f9b5f49fe6030fc028bc93debf856d1ae75ca7ab</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Revert "doc: Increase visibility of special signs' usage"</title>
<updated>2025-06-10T16:03:00Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2025-06-10T16:02:56Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=13e0d83d3186050485442bf2e8d50a12dc9e359f'/>
<id>urn:sha1:13e0d83d3186050485442bf2e8d50a12dc9e359f</id>
<content type='text'>
This reverts commit 66ec0dfad8ac1d4d8646a4734eb9353f3ebc0a91.

This creates too much churn in the translation.
</content>
</entry>
<entry>
<title>doc: Increase visibility of special signs' usage</title>
<updated>2025-05-29T20:30:50Z</updated>
<author>
<name>Daniel Lublin</name>
<email>daniel@lublin.se</email>
</author>
<published>2025-05-29T20:29:21Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=66ec0dfad8ac1d4d8646a4734eb9353f3ebc0a91'/>
<id>urn:sha1:66ec0dfad8ac1d4d8646a4734eb9353f3ebc0a91</id>
<content type='text'>
Closes: #310975

Signed-off-by: Daniel Lublin &lt;daniel@lublin.se&gt;
</content>
</entry>
<entry>
<title>Release 3.1.0</title>
<updated>2025-05-19T17:14:52Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2025-05-19T17:14:11Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=5bfea97d7b3c6f4fcaa56c24d6f3591b1862b86b'/>
<id>urn:sha1:5bfea97d7b3c6f4fcaa56c24d6f3591b1862b86b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Update translation templates and merge translations</title>
<updated>2025-05-19T16:29:05Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2025-05-19T16:29:05Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=529d34728126ad19f4729ddf9bf95420b343378b'/>
<id>urn:sha1:529d34728126ad19f4729ddf9bf95420b343378b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>sources.list(5): Explicitly say what the precedence order is</title>
<updated>2025-05-19T16:07:34Z</updated>
<author>
<name>Simon McVittie</name>
<email>smcv@debian.org</email>
</author>
<published>2024-12-24T13:45:57Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8576438367416c87f38effe960d143d94ebac851'/>
<id>urn:sha1:8576438367416c87f38effe960d143d94ebac851</id>
<content type='text'>
The order of apt sources can matter, but this man page did not
previously define whether /etc/apt/sources.list was parsed before or
after the fragment files in sources.list.d. Giving a concrete example
also provides a hint that numeric prefixes are a useful way to force a
particular sort order, and clarifies that the .list or .sources extension
is less important than lexicographic order.

Signed-off-by: Simon McVittie &lt;smcv@debian.org&gt;
</content>
</entry>
<entry>
<title>apt_preferences(5): Specify the order in which files are parsed</title>
<updated>2025-05-19T16:05:40Z</updated>
<author>
<name>Simon McVittie</name>
<email>smcv@debian.org</email>
</author>
<published>2024-12-24T13:53:48Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=49681c12b124e236731524b6fbbab7f91147295b'/>
<id>urn:sha1:49681c12b124e236731524b6fbbab7f91147295b</id>
<content type='text'>
The order of preference stanzas matters, but this man page did not
previously define whether /etc/apt/preferences was parsed before or
after the fragment files in preferences.d. Giving a concrete example
also provides a hint that numeric prefixes are a useful way to force a
particular sort order, and clarifies that the presence or absence of
the .pref extension is less important than lexicographic order.

Signed-off-by: Simon McVittie &lt;smcv@debian.org&gt;
</content>
</entry>
<entry>
<title>dselect: Add https support</title>
<updated>2025-05-19T16:02:55Z</updated>
<author>
<name>Guillem Jover</name>
<email>guillem@debian.org</email>
</author>
<published>2022-03-20T10:45:31Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=b00a59c0b953bf7688fc60a976bac74194886a0c'/>
<id>urn:sha1:b00a59c0b953bf7688fc60a976bac74194886a0c</id>
<content type='text'>
Recognize the method and update the documentation and prompts.
</content>
</entry>
<entry>
<title>Introduce apt why, apt why-not</title>
<updated>2025-05-19T15:20:09Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2025-05-19T12:17:23Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7724d170751b3dc1717ba7a08881437cf7151996'/>
<id>urn:sha1:7724d170751b3dc1717ba7a08881437cf7151996</id>
<content type='text'>
These are implemented somewhat differently from aptitudes
why and why-not commands: They produce the actual solver
trace for why a particular decision has been taken.

For the why-not case, we need to explicitly discover our
specified package, as if nothing else depends on it in
our graph, it would otherwise always be undiscovered and
conflicts not detected (see e.g. level-3 in the test).
</content>
</entry>
</feed>
