apt/test/integration, branch 1.7.0

Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts

2018-10-05T10:45:47Z

Some post-invoke scripts install packages, which fails because the environment variable is not set. This sets the variable for all three kinds of scripts {pre,post-}invoke and pre-install-pkgs, but we will only allow post-invoke at a later time. Gbp-Dch: full

Deal with descriptions embedded in displayed record correctly

2018-09-20T16:36:03Z

The implementation of "apt-cache show" (not "apt show") incorrectly resets the currently used parser if the record itself and the description to show come from the same file (as it is the case if no Translation-* files are available e.g. after debootstrap). The code is more complex than you would hope to support some rather unusual setups involving Descriptions and their translations as tested for by ./test-bug-712435-missing-descriptions as otherwise this could be a one-line change. Regression-Of: bf53f39c9a0221b670ffff74053ed36fc502d5a0 Closes: #909155

Merge branch 'bugfix/statusfd' into 'master'

2018-09-18T12:05:20Z

Process all of --status-fd and don't expect duplicate status msg See merge request apt-team/apt!26

Show all architectures in 'apt list' output

2018-09-15T15:45:16Z

The uniqueness in std::set containers is ensured by the ordering operator we provide, but it was not considering that different versions can have the same description like the different architectures for a version of a package. Closes: #908218

Reorder progress report messages

2018-09-11T11:08:58Z

We are seeing 'processing' messages from dpkg first, so it makes sense to translate them to "Preparing" messages instead of using "Installing" and co to override these shortly after with the "Preparing" messages. The difference isn't all to visible as later messages tend to linger far longer in the display than the ealier ones, but at least in a listing it seems more logical.

Don't expect duplicated dpkg status-fd messages

2018-09-11T11:08:58Z

The progress reporting relies on parsing the status reports of dpkg which used to repeat being in the same state multiple times in the same run, but by fixing #365921 it will stop doing so. The problem is in theory just with 'config-files' in case we do purge as this (can) do remove + purge in one step, but we remove this also for the unpack + configure combination althrough we handle these currently in two independent dpkg calls.

Unset more environment variables in test framework

2018-09-11T10:59:01Z

It is an uphill battle to "reset" the environment to a clean state without making it needlessly hard to use 'good' environment variables, so we just try a little harder here without really trying for completeness. Gbp-Dch: Ignore

Don't use gpg directly in apt-key test

2018-09-10T19:57:51Z

Reported-By: Guillem Jover Gbp-Dch: Ignore

Fix typos reported by codespell & spellintian

2018-08-29T15:51:43Z

No user-visible change as it effects mostly code comments and not a single error message, manpage or similar. Reported-By: codespell & spellintian Gbp-Dch: Ignore

Don't use invalid iterator in Fallback-Of handling

2018-08-29T15:50:31Z

cppcheck reports: (error) Iterator 't' used after element has been erased. The loop is actually fashioned to deal with this (not in the most efficient way, but in simplest and speed isn't really a concern here) IF this codepath had a "break" at the end… so I added one. Note that the tests aren't failing before (and hopefully after) the change as the undefined behavior we encounter is too stable. Thanks: David Binderman for reporting