apt/apt-pkg/deb, branch 2.3.2Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.3.22021-04-21T09:49:50ZDo not pass --force-remove-protected with --auto-deconfigure2021-04-21T09:49:50ZJulian Andres Klodejulian.klode@canonical.com2021-04-14T08:48:15Zurn:sha1:6cb80d1eb2e8abcd4246fe39af3d1cd0398e1188
dpkg 1.20.8 no longer requires this.
Merge the three RAII vectors managing args lifetime2021-03-09T12:44:30ZDavid Kalnischkiesdavid@kalnischkies.de2021-03-09T12:26:05Zurn:sha1:676f716717b7f138661ee5cb01edb0051f96ca49
Having three different vectors littered over the method to manage
various parts of the lifetime of the argument vector we are creating is
a bit dangerous as it means a simple code change could result in a
desync of these three, so by moving the functionality of them all into a
wrapper class should prevent us from making such mistakes.
Handle multi-arch pkgnames for dpkg call via RAII2021-03-09T12:38:13ZDavid Kalnischkiesdavid@kalnischkies.de2021-03-09T10:40:35Zurn:sha1:302b1edcb1afe8098ddc2ddd576e56b898c1d90bUse RAII to clean up tmp dir for dpkg recursive install2021-03-09T12:36:52ZDavid Kalnischkiesdavid@kalnischkies.de2021-03-09T10:40:59Zurn:sha1:3312607159410eda3c634a0c6fe3c2b1a4fd3cc3
One less thing to remember to do in all branches.
Replace multi-statement macro with lambda2021-03-09T10:45:08ZDavid Kalnischkiesdavid@kalnischkies.de2021-03-09T10:39:29Zurn:sha1:a5346a50c4f3ef15e71c16a9bf88723ae1153776
It is easy to make mistakes while dealing with such macros regardless of
how much you guard them, so just using a lambda removes a lot of
concerns here basically for free.
Do not require force-loopbreak on Protected packages2021-02-23T18:10:29ZJulian Andres Klodejulian.klode@canonical.com2021-02-23T17:23:30Zurn:sha1:f8ff3afcd42d8b2e6506bc6f44a894149bf87442
dpkg will be changed in 1.20.8 to not require --force-remove for
deconfiguration anymore, but we want to decouple our changes from the
dpkg ones, so let's always pass --force-remove-protected when installing
packages such that we can deconfigure protected packages.
Closes: #983014
Guess compressor only if no AR nember with exact name exists2021-02-02T18:56:46ZDavid Kalnischkiesdavid@kalnischkies.de2020-12-02T14:51:09Zurn:sha1:f2c087449286812823d06d1b560fa947e438fa0d
Explicitly opening a tar member is a bit harder than it needs to be as
you have to remove the compressor extension so that it can be guessed
here gain potentially choosing the wrong member.
Doesn't really matter for deb packages of course as the member count is
pretty low and strongly defined, but testing is easier this way.
It also finally fixes an incorrectly formatted error message.
Merge branch 'pu/include-all-translations' into 'master'2021-01-27T15:17:01ZJulian Andres Klodejak@debian.org2021-01-27T15:17:01Zurn:sha1:ce2fbbbcd5d81b4cfd60d2a277cbd9ee63d2c1e7
Include all translations when building the cache
See merge request apt-team/apt!156Include all translations when building the cache2021-01-27T11:48:58ZJulian Andres Klodejulian.klode@canonical.com2021-01-27T11:31:05Zurn:sha1:ccd952cc8793bc6b866f92912ef0bb51c42eb540
We do download all translations we ever downloaded, but we don't add all
of those to the cache, meaning that if we run update with LANG=C, it
might still download your de_DE translation, but it won't insert it into
the cache, causing your de_DE user to not get translated messages.
LP: #1907850
dpkg: fix passing readonly /dev/null fd as stdout/stderr2021-01-22T15:41:12ZYoufu Zhangzhangyoufu@gmail.com2021-01-22T09:41:22Zurn:sha1:acbe227d50178657d98a609221b1caa5b128d7bb
The read-only /dev/null was duplicated to stdout and stderr, causing writes to those descriptors to fail:
[pid 260] openat(AT_FDCWD, "/dev/null", O_RDONLY) = 7
[pid 260] dup2(7, 0) = 0
[pid 260] close(5) = 0
[pid 260] dup2(6, 1) = 1
[pid 260] dup2(7, 2) = 2
[pid 260] write(2, "Chrooting into ", 15) = -1 EBADF (Bad file descriptor)
[pid 260] chroot("/chroot/") = 0