apt/test/integration/test-policy-pinning, branch main

Implement 'Pin: source-version '

2024-08-22T14:11:38Z

As wondered about by Paride some minutes ago.

Allow apt to run if no dpkg/status file exists

2022-09-02T14:55:45Z

Not having a dpkg/status file used to be a hard error which from a boostrap perspective is suspect as in the beginning, there is no status so you would need to touch it into existence. We make a difference between factual non-existence and inaccessibility to catch mistakes in which the file is not readable for some reason, the testcase test-bug-254770-segfault-if-cache-not-buildable is an example of this. Note that apt has already figured out at this point that this is a Debian-like system which should have a dpkg/status file. This change does not effect the auto-detection and is not supposed to.

Enable tests commented out with no longer true fixme

2022-02-02T12:18:09Z

Pinning and its display was reworked years ago, but the test and especially the comment never got the memo. References: a91aae406112df1d8fe16d00212333a20210f674 Gbp-Dch: Ignore

Remove useless use of awk

2022-02-02T12:18:09Z

I have no idea what I was thinking 12 years ago. Gbp-Dch: Ignore

test/integration/test-policy-pinning: test listing multiple package in Package: field

2022-01-03T10:51:56Z

Add test case for local-only packages pinned to never

2019-04-15T07:43:32Z

Test from the fix for the regression in trusty for LP #1821308.

Introduce experimental 'never' pinning for sources

2019-02-01T16:51:35Z

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: . 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.

error in update on Release information changes

2017-06-28T17:18:47Z

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.

restore pinning to min/max value of short

2016-04-25T14:30:43Z

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

properly parse comments in apt_preferences and deb822-style sources

2016-01-02T15:20:01Z

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.