Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/rebuildpkgs.in
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2018-12-01 19:36:23 -0500
committerErich Eckner <git@eckner.net>2019-04-01 10:20:17 +0200
commit9efc5d0e37a6c781f83b853ec5bdc5b6a01a472a (patch)
treec913ab05845230e9849d48b81b65f184a3e5f32e /rebuildpkgs.in
parent9ace6a0f5cf0d205924cf742fc287ab9574b4ff2 (diff)
arch-nspawn: don't delete the guest gpg configurationv20190329
It's important to ensure the guest has up to date data because updating a chroot after quite some time can potentially rely on updated archlinux-keyring, something which the host machine either kept up to date on or manually fixed, but it kills automation to mess around with chroot configs like that. Alternatively, signed packages added with -I need to work, and we assume the host is configured to accept these. That is *not* a good reason to completely nuke whatever is in the guest, though. A guest might have been manually configured to accept keys which aren't accepted by the host; one example of this happening in practice, is archlinux32 when building 32-bit packages from an archlinux host. A simple solution is to use pacman-key's native facility to dump the known keys and trust status from one gpg configuration, and import it into another. Use this to append to, rather than overwrite, the chrooted guest's pacman keyring. While we are at it, fix a bug where we didn't respect the host's pacman.conf settings for the GpgDir. While it isn't wildly likely a user will choose to customize this, it is a valid and supported use case and we must think about this ourselves.
Diffstat (limited to 'rebuildpkgs.in')
0 files changed, 0 insertions, 0 deletions