apt, branch 1.8.0

Release 1.8.0

2019-03-08T08:42:06Z

CMake: Install auth.conf.d directory

2019-03-07T12:10:08Z

The missing auth.conf.d directory was an oversight, it should be there. LP: #1818996

Dutch manpages translation update

2019-03-06T14:16:05Z

Closes: #923834

Dutch program translation update

2019-03-06T14:15:38Z

Closes: #923728

Fix name of APT::Update::Post-Invoke-Stats (was ...Update-Post...)

2019-03-06T14:12:06Z

Bad accident. Accidents happen.

Merge branch 'l10n-1.8.y' into '1.8.y'

2019-03-04T13:19:41Z

[l10n] Update Italian translation See merge request apt-team/apt!53

Merge branch 'bugfix/reportbinarysig' into '1.8.y'

2019-03-04T13:17:00Z

Add explicit message for unsupported binary signature See merge request apt-team/apt!52

[l10n] Update Italian translation

2019-03-04T10:29:29Z

Signed-off-by: Milo Casagrande

Add explicit message for unsupported binary signature

2019-03-03T20:52:40Z

Verifying the content of Release.gpg made us fail on binary signatures which were never officially supported (apt-secure manpage only documents only the generation of ASCII armored), but silently accepted by gpgv as we passed it on unchecked before. The binary format is complex and is itself split into old and new formats so adding support for this would not only add lots of code but also a good opportunity for bugs and dubious benefit. Reporting this issue explicitly should help repository creators figure out the problem faster than the default NODATA message hinting at captive portals. Given that the binary format has no file magic or any other clear and simple indication that this is a detached signature we guess based on the first two bits only – and by that only supporting the "old" binary format which seems to be the only one generated by gnupg in this case. References: e2965b0b6bdd68ffcad0e06d11755412a7e16e50 Closes: #921685

Release 1.8.0~rc4

2019-02-26T07:33:51Z