apt/test, branch 1.9.0Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.9.02019-06-12T13:02:55ZAdjust code for missing includes/using std::string2019-06-12T13:02:55ZJulian Andres Klodejulian.klode@canonical.com2019-06-12T11:47:46Zurn:sha1:82b881caafa0c82b20db3900f8b76cebd8a393a4http: Fix Host header in proxied https connections2019-06-11T15:27:34ZSimon Körnergit@lubiland.de2019-05-17T22:32:15Zurn:sha1:86d4d98060f36c7e71c34af20a1193a75496ef72
Currently CONNECT requests use the name of the proxy as Host value, instead of
the origin server's name.
According to RFC 2616 "The Host field value MUST represent the naming authority
of the origin server or gateway given by the original URL."
The current implementation causes problems with some proxy vendors. This
commit fixes this.
[jak: Adding a test case]
See merge request apt-team/apt!66
Introduce apt satisfy and apt-get satisfy2019-06-11T14:49:03ZJulian Andres Klodejulian.klode@canonical.com2019-05-09T20:23:17Zurn:sha1:9244f712396c10b674740cc79fdab61c47173d04
Allow to satisfy dependency strings supplied on
the command line, optionally prefixed with
"Conflicts:" to satisfy them like Conflicts.
Build profiles and architecture restriction lists,
as used in build dependencies, are supported as
well.
Compared to build-dep, build-essential is not
installed automatically, and installing of recommended
packages follows the global default, which defaults
to yes.
Closes: #275379
See merge request apt-team/apt!63
Make APT::StringView public2019-06-11T12:45:55ZJulian Andres Klodejulian.klode@canonical.com2019-02-04T18:50:16Zurn:sha1:a6e86d51a0e32cdc91f2902b0d6b483af884dccaCMake: Enforce "override" use on overriden methods2019-05-06T14:29:40ZJulian Andres Klodejulian.klode@canonical.com2019-05-06T14:29:40Zurn:sha1:3bec42fdf01eb3f7403876979023ad952228ee73
This ensures that we do not accidentally stop overriding a
method because it's signature changed in an API break.
Use debDebFile to get control file instead of dpkg-deb2019-05-06T11:01:23ZJulian Andres Klodejulian.klode@canonical.com2019-05-06T10:22:42Zurn:sha1:6089a4b17c61ef30b2efc00e270b0907f51f352aMerge libapt-inst into libapt-pkg2019-05-06T10:14:04ZJulian Andres Klodejulian.klode@canonical.com2019-05-06T09:40:08Zurn:sha1:dfe2511e31f232a8a8880eba40af40d1deb0e49cAdd test case for local-only packages pinned to never2019-04-15T07:43:32ZJulian Andres Klodejulian.klode@canonical.com2019-04-02T15:03:04Zurn:sha1:5557a3c337075f9700a67d9ef74a79e914768197
Test from the fix for the regression in trusty for LP #1821308.
Add explicit message for unsupported binary signature2019-03-03T20:52:40ZDavid Kalnischkiesdavid@kalnischkies.de2019-03-03T18:41:42Zurn:sha1:3e3638dc9389591cfd30baa6c41d85c31127402a
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 documentation2019-02-10T12:16:27ZJakub Wilkjwilk@jwilk.net2019-02-10T11:51:30Zurn:sha1:9a702b150c8ddeafa8c10c9f120dafdeb08ef93b