apt/apt-pkg/aptconfiguration.cc, branch 1.1.7Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.1.72015-11-04T17:04:00Zimplement a public pkgSystem::ArchitecturesSupported2015-11-04T17:04:00ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-15T12:12:19Zurn:sha1:825db89094a8413dcc9c8ef3abe0a45b0bb7a2e2aptconfiguration: Convert strtok() to strtok_r()2015-10-30T13:20:11ZJulian Andres Klodejak@debian.org2015-10-23T18:39:56Zurn:sha1:1843d82ff5f8712778062cc08ed991e1dee42b6e
strtok() is not thread-safe, whereas strtok_r() is.
Gbp-Dch: ignore
try xz instead of bz2 first for compressed files2015-08-29T17:55:19ZDavid Kalnischkiesdavid@kalnischkies.de2015-08-29T17:55:19Zurn:sha1:e93b4028825648bb29074a1422287e2cb435b0de
xz has pretty much won "the compressor war" and e.g. the Debian archive
doesn't even distribute bz2 anymore in favor of 'xz' and 'gz', so by
changing the default order we have a more realistic --print-uris
behavior as it will always show the first compressor.
In practice this effects repositories without a Release file (very bad,
we don't want to support them anymore anyhow) as xz will be tried before
bz2 now [which is probably not available, but so might be bz2…] AND
repositories which provide both, bz2 and xz (which isn't too common) in
sofar as apt will now download xz instead of bz2.
Users with special needs can stick with bz2 as first compressor tried
with Acquire::CompressionTypes::Order:: "bz2"; (see man apt.conf) – but
users with special needs usually prefer "gz" anyhow, so the realworld
change is expected to be very low.
use c++11 algorithms to avoid strange compiler warnings2015-08-29T10:33:30ZDavid Kalnischkiesdavid@kalnischkies.de2015-08-29T10:28:24Zurn:sha1:8dd562a894c2472e3705fe13c212f665b55744a9
Nobody knows what makes the 'unable to optimize loop' warning to appear
in the sourceslist minus-options parsing, especially if we use a foreach
loop, but we can replace it with some nice c++11 algorithm+lambda usage,
which also helps in making even clearer what happens here.
And as this would be a lonely change, lets do it for a few more loops as
well where I might or might not have seen the warning at some point in
time, too.
Git-Dch: Ignore
Cleanup includes after running iwyu2015-08-17T10:01:45ZMichael Vogtmvo@debian.org2015-08-17T10:01:45Zurn:sha1:88a8975f156e452d9f3ebe76822b236e8962ebbaMake apt compile with clang++ again2015-08-14T17:44:25ZMichael Vogtmvo@debian.org2015-08-14T17:44:25Zurn:sha1:f8043f219f077b1cfc6c5ad2263c4caa4709a00d
This allows us to run the clang static analyzer and to run the
testsuite with the clang MemorySanitizer.
mark private methods as hidden2014-09-29T22:15:15ZDavid Kalnischkiesdavid@kalnischkies.de2014-09-29T13:41:12Zurn:sha1:3809194b662f48733916e6248cd0c141f281313d
We are the only possible users of private methods, so we are also the
only users who can potentially export them via using them in inline
methods. The point is: We don't need these symbols exported if we don't
do this, so marking them as hidden removes some methods from the API
without breaking anything as nobody could have used them.
Git-Dch: Ignore
invalid cache if architecture set doesn't match2014-05-10T10:50:00ZDavid Kalnischkiesdavid@kalnischkies.de2014-05-10T10:50:00Zurn:sha1:7a223b933cab0447438ca2e964576da39078eaf4
The cache heavily depends on the architecture(s) it is build for,
especially if you move from single- to multiarch. Adding a new
architecture to dpkg therefore has to be detected and must invalidate
the cache so that we don't operate on incorrect data.
The incorrect data will prevent us from doing otherwise sensible
actions (it doesn't allow bad things to happen) and the recovery is
simple and automatic in most cases, so this hides pretty well and is
also not as serious as it might sound at first.
Closes: 745036
do not create an (additional) empty compressor2014-04-11T09:16:04ZDavid Kalnischkiesdavid@kalnischkies.de2014-04-11T09:16:04Zurn:sha1:8056a00cd76c0f9dd6c444f23aa9998f96f805ed
FileFd code knows how to deal with such a compressor, so it isn't a
problem, but it is absolutely not needed as we already have an
(matching) identity compressor with '.' earlier in the list.
Git-Dch: Ignore
use liblzma-dev to provide xz/lzma support2014-03-13T13:00:38ZDavid Kalnischkiesdavid@kalnischkies.de2014-03-12T13:39:18Zurn:sha1:7f350a377e0c65a656b9b5437e27d037fd742901
We have xz/lzma support for a while, but only via an external binary
provided by xz-utils. Now that the Debian archive provides xz by default
and dpkg pre-depends on the library provided by liblzma-dev we can switch
now to use this library as well to avoid requiring an external binary.
For now the binary is in a prio:required package, but this might change
in the future.
API wise it is quiet similar to bz2 code expect that it doesn't provide
file I/O methods, so we piece this together on our own.