apt, branch 2.0.1

Release 2.0.1

2020-03-24T10:54:09Z

Merge branch 'pu/colored-error' into 'master'

2020-03-24T10:52:29Z

Add color highlighting to E:/W:/N: prefixes See merge request apt-team/apt!112

configure-index: Add APT::Color option

2020-03-24T09:24:39Z

This caused unbound error list growth, because each time we dumped an error, the calls to _config->FindB() inside operator << would add 3 new errors of the form: W: Using unknown config option »apt::color« of type BOOL Hence we are dumping an infinite list of errors, and eventually that list will exceed available memory.

Add color highlighting to E:/W:/N: prefixes

2020-03-24T09:24:39Z

This matches the definitions used by dpkg. Closes: #953527

Merge branch 'pu/analyze-pattern' into 'master'

2020-03-24T09:16:42Z

apt-helper: Add analyze-pattern helper See merge request apt-team/apt!113

Russian program translation update

2020-03-21T08:18:37Z

Closes: #953804

Parse last line in deb file correctly by adding a newline

2020-03-21T07:35:26Z

While merging apt-pkg and apt-inst libraries the codepath of handling deb files in apt-pkg was adapted to use the 'old' code from apt-inst instead of fork&exec of dpkg-deb -I. The information we get this way forms the main part of the package stanza, but we add a few semi-optional fields to the stanza to make it look and work more like a stanza we got from a repository. Just be careful with the area where these two parts touch as if, hypothetically, we would stip all newlines around the parts, but forget to add a newline between them later, the two lines around the merge would stick a bit too close together forming one which could result in fun parsing errors if this merged line was previously e.g. a well-formed Depends line and has now extra fluff attached. This codepath has a history with too many newlines (#802553) though, so how likely is it really that it will some day lack one you may ask. References: 6089a4b17c61ef30b2efc00e270b0907f51f352a

apt-helper: Add analyze-pattern helper

2020-03-12T20:04:50Z

The analyze-pattern helper parses a pattern and then renders the parsed pattern, allowing you to analyze how the parser interpreted the string. This can be useful to analyse (yes, analyse-pattern also works) why a pattern is different from aptitude or why it does not work as expected. It can also be used to check if apt has pattern support, although that will miss out on the version shipped in eoan, but who really cares about that longer term anyway?

error: Extract operator<< into error.cc (de-inline it)

2020-03-10T21:29:46Z

Extract the code, and reformat it with clang-format so we can modify it.

Don't crash pattern matching sections if pkg has no section

2020-03-10T09:57:21Z

Packages from third-party sources do not always follow the established patterns of more properly maintained archives. In that case it was a driver package for a scanner&printer device which has only a minimum of info attached, but also minimal non-installed packages do not include sections, so we really shouldn't assume their availability.