apt, branch 2.1.1

Release 2.1.1

2020-05-08T16:03:47Z

Use "po4a --porefs file" instead of undocumented compat noline

2020-05-08T14:38:20Z

References: https://github.com/mquinson/po4a/commit/329f472a378d42c7a33e8110e5091be61480a0fc

Drop nowrap from po4a --porefs as it is no longer supported

2020-05-08T14:34:36Z

Upstream says it had no effect before, so it seems safe to adapt. References: https://github.com/mquinson/po4a/commit/ac1e97305b6073ed87fa8cf0a2e32f9b1255d0f1

Fix typo in Polish translation of --help messages

2020-05-08T14:19:55Z

Also translating two related strings along the way. References: https://github.com/Debian/apt/pull/107

Allow aptitude to MarkInstall broken packages via FromUser

2020-05-08T13:52:14Z

apt marks packages coming from the commandline among others as protected to ensure the various resolver parts do not fiddle with the state of these packages. aptitude (and potentially others) do not so the state is modified (to a Keep which for uninstalled means it is not going to be installed) due to being uninstallable before the call fails – basically reverting at least some state changes the call made before it realized it has to fail, which is usually a good idea, except if users expect you to not do it. They do set the FromUser option though which has beside controlling autobit also gained the notion of "the user is always right" over time and can be used for this one here as well preventing the state revert. References: 0de399391372450d0162b5a09bfca554b2d27c3d Reported-By: Jessica Clarke on IRC

Release 2.1.0

2020-05-04T14:02:21Z

doc/po: Merge nl with template, update template

2020-05-04T14:01:43Z

We did not merge nl with the template when we updated it, hence we have quite a bit of churn in that commit and this one.

Merge branch 'pu/wildcards' into 'master'

2020-05-04T12:10:50Z

Reinstate * wildcards See merge request apt-team/apt!118

apt list: Fix behavior of regex vs fnmatch vs wildcards

2020-05-04T11:08:33Z

Previously (and still in cacheset), patterns where only allowed to start with ? or ~, which ignores the fact that a pattern might just as well start with a negation, such a !~nfoo. Also, we ignored the --regex flag if it looked like this, which was somewhat bad. Let's change this all: * If --regex is given, arguments are always interpreted as regex * If it is a valid package wildcard (name or * characters), then it will be interpreted as a wildcard - this set of characters is free from meaningful overlap with patterns. * Otherwise, the argument is interpreted as a pattern. For a future version, we need to adapt parsing for cacheset and list to use a common parser, to avoid differences in their interpretation. Likely, this code will go into the pattern parser, such that it generates a pattern given a valid fnmatch argument for example.

Reinstate * wildcards

2020-05-04T10:48:56Z

Reinstate * wildcards as they are safe to use, but do not allow any other special characters such as ? or []. Notably, ? would overlap with patterns, and [] might overlap with future pattern extensions (alternative bracketing style), it's also hard to explain. Closes: #953531 LP: #1872200