apt/apt-pkg/deb/dpkgpm.cc, branch 2.9.1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.12024-02-20T12:49:04ZModernize standard library includes2024-02-20T12:49:04ZJulian Andres Klodejulian.klode@canonical.com2024-02-20T12:43:08Zurn:sha1:40a75722c43ae24cb9a99d6730a3b25b65819c49
This was automated with sed and git-clang-format, and then I had to
fix up the top of policy.cc by hand as git-clang-format accidentally
indented it by two spaces.
apt-pkg/deb/dpkgpm.cc: make DPkg::Chroot-Directory work under fakechroot2021-09-19T17:03:29ZJohannes Schauer Marin Rodriguesjosch@mister-muffin.de2021-09-19T17:03:29Zurn:sha1:e6f7bfb02ef254ec6922c1a3b3f9a2c741db6a79Restore dpkg::chroot-directory functionality2021-06-10T17:25:17ZDavid Kalnischkiesdavid@kalnischkies.de2021-06-10T16:06:14Zurn:sha1:8083d4019844f764058efa2a950ed16975178bff
If we call dpkg inside a chroot we have to ensure that the temporary
directory we construct to call dpkg --recursive is inside the chroot and
that we strip the path to the chroot from the directory name we pass to
dpkg.
Note that the added test succeeds before and (hopefully) after as we
can't really chroot here or fiddle with the needed settings as we are
already setting up apt to work with a quasi-chroot. The test perhaps
helps in ensuring we don't break it too much in the future though.
(Broken five years (and one day) ago this seems to have an immense user
base at the moment, but it might in the future via mmdebstrap)
References: f495992428a396e0f98886c9a761a804aa161c68
Reported-By: Johannes Schauer Marin Rodrigues on IRC
Tested-By: Johannes Schauer Marin Rodrigues
Do 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
Add basic support for the Protected field2020-06-29T15:32:17ZJulian Andres Klodejulian.klode@canonical.com2020-06-29T15:31:06Zurn:sha1:ddd8fc3d28cd8e668868158049ced7fa3c8c71b8
This will be mapped to Important for the time being.