apt/apt-pkg, branch 1.8.2

Unlock dpkg locks in reverse locking order

2019-05-21T12:53:13Z

We need to unlock in the reverse order of locking in order to get useful behavior. LP: #1829860

Prevent shutdown while running dpkg

2019-05-03T14:48:56Z

As long as we are running dpkg, keep an inhibitor that blocks us from shutting down. LP: #1820886

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

Fix various typos in the documentation

2019-02-10T12:16:27Z

Use std::to_string() for HashStringList::FileSize() getter

2019-02-04T14:29:09Z

This slightly improves performance, as std::to_string() (as in gcc's libstdc++) avoids a heap allocation. This is surprisingly performance critical code, so we might want to improve things further in 1.9 by manually calculating the string - that would also get rid of issues with locales changing string formatting, if any.

Detect function multiversioning and sse4.2/crc32, enables i386

2019-02-04T14:21:32Z

This fixes the build on kfreebsd-amd64, and due to the detection of sse4.2, should also enable the sse4.2 on i386.

gpgv: Use buffered writes for splitting clearsigned files

2019-02-04T13:43:16Z

This is safe here, as the code ensures that the file is flushed before it is being used. The next series should probably make GetTempFile() buffer writes by default.

Merge branch 'pu/dead-pin' into 'master'

2019-02-04T12:44:08Z

A pin of -32768 overrides any other, disables repo See merge request apt-team/apt!40

Add a Packages-Require-Authorization Release file field

2019-02-01T16:52:03Z

This new field allows a repository to declare that access to packages requires authorization. The current implementation will set the pin to -32768 if no authorization has been provided in the auth.conf(.d) files. This implementation is suboptimal in two aspects: (1) A repository should behave more like NotSource repositories (2) We only have the host name for the repository, we cannot use paths yet. - We can fix those after an ABI break. The code also adds a check to acquire-item.cc to not use the specified repository as a download source, mimicking NotSource.

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.