<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/test-policy-pinning, branch 2.4.2</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.4.2</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.4.2'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2022-02-02T12:18:09Z</updated>
<entry>
<title>Enable tests commented out with no longer true fixme</title>
<updated>2022-02-02T12:18:09Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2022-01-03T10:37:46Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ea2b51f29f9510da87d193fe12ac37d19ed4f51b'/>
<id>urn:sha1:ea2b51f29f9510da87d193fe12ac37d19ed4f51b</id>
<content type='text'>
Pinning and its display was reworked years ago, but the test and
especially the comment never got the memo.

References: a91aae406112df1d8fe16d00212333a20210f674
Gbp-Dch: Ignore
</content>
</entry>
<entry>
<title>Remove useless use of awk</title>
<updated>2022-02-02T12:18:09Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2022-01-03T10:31:15Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=71ea488ca53c7bde176655623a829c82e32e5a85'/>
<id>urn:sha1:71ea488ca53c7bde176655623a829c82e32e5a85</id>
<content type='text'>
I have no idea what I was thinking 12 years ago.

Gbp-Dch: Ignore
</content>
</entry>
<entry>
<title>test/integration/test-policy-pinning: test listing multiple package in Package: field</title>
<updated>2022-01-03T10:51:56Z</updated>
<author>
<name>Johannes Schauer Marin Rodrigues</name>
<email>josch@mister-muffin.de</email>
</author>
<published>2022-01-03T10:51:56Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=13b3dede65707282819f901c4b37da7e9028420e'/>
<id>urn:sha1:13b3dede65707282819f901c4b37da7e9028420e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add test case for local-only packages pinned to never</title>
<updated>2019-04-15T07:43:32Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-04-02T15:03:04Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=5557a3c337075f9700a67d9ef74a79e914768197'/>
<id>urn:sha1:5557a3c337075f9700a67d9ef74a79e914768197</id>
<content type='text'>
Test from the fix for the regression in trusty for LP #1821308.
</content>
</entry>
<entry>
<title>Introduce experimental 'never' pinning for sources</title>
<updated>2019-02-01T16:51:35Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2018-12-18T13:50:25Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8bb2a91a070170d7d8e71206d1c66a26809bdbc3'/>
<id>urn:sha1:8bb2a91a070170d7d8e71206d1c66a26809bdbc3</id>
<content type='text'>
This allows disabling a repository by pinning it to 'never',
which is internally translated to a value of -32768 (or whatever
the minimum of short is).

This overrides any other pin for that repository. It can be used
to make sure certain sources are never used; for example, in
unattended-upgrades.

To prevent semantic changes to existing files, we substitute
min + 1 for every pin-priority: &lt;min&gt;. This is a temporary
solution, as we are waiting for an ABI break.

To add pins with that value, the special Pin-Priority
"never" may be used for now. It's unclear if that will
persist, or if the interface will change eventually.
</content>
</entry>
<entry>
<title>error in update on Release information changes</title>
<updated>2017-06-28T17:18:47Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-04-12T15:39:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=081fbea14d12f79c8d91ce4fe1f1004c7bc08656'/>
<id>urn:sha1:081fbea14d12f79c8d91ce4fe1f1004c7bc08656</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>restore pinning to min/max value of short</title>
<updated>2016-04-25T14:30:43Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-04-25T14:30:43Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=fd2e438b24f4ce153ee35a691ae5bcb7eb28cc98'/>
<id>urn:sha1:fd2e438b24f4ce153ee35a691ae5bcb7eb28cc98</id>
<content type='text'>
Broken in the previous commit (69cea1ef2cfda3c4da79fd756a8edaf2be26998e).
Adding a test and a comment to avoid future embarrassment.

Git-Dch: Ignore
Reported-By: Julian Andres Klode on IRC
</content>
</entry>
<entry>
<title>properly parse comments in apt_preferences and deb822-style sources</title>
<updated>2016-01-02T15:20:01Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-01-02T12:27:02Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f6459e646f6fa45c34d1f13f37173ea4b92ffd5f'/>
<id>urn:sha1:f6459e646f6fa45c34d1f13f37173ea4b92ffd5f</id>
<content type='text'>
apt_preferences and deb822-style sources used the specialized class
pkgUserTagSection to deal with comments before/after a given stanza, but
it couldn't deal with comments in the stanza at all.

codesearch suggests that nobody else does and a vastely superior way of
working with potentially commented files is implemented now, so we can
officially discourage the use of the old incomplete hack class.
</content>
</entry>
<entry>
<title>tests: support spaces in path and TMPDIR</title>
<updated>2015-12-19T22:04:34Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-12-15T16:20:26Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2'/>
<id>urn:sha1:3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2</id>
<content type='text'>
This doesn't allow all tests to run cleanly, but it at least allows to
write tests which could run successfully in such environments.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>tagfile: Hardcode error message for out of range integer values</title>
<updated>2015-12-14T12:58:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2015-12-14T12:58:46Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=137e8ad4b6ce28b1a1355d5a125d09670388c2b7'/>
<id>urn:sha1:137e8ad4b6ce28b1a1355d5a125d09670388c2b7</id>
<content type='text'>
This makes the test suite work on 32 bit-long platforms.

Gbp-Dch: ignore
</content>
</entry>
</feed>
