[pacman-dev] [Git][pacman/pacman][master] 3 commits: pacman-key: Add --quiet to a few more gpg invocations

Allan McRae (@allan) allan at archlinux.org
Sat Sep 4 06:44:03 UTC 2021



Allan McRae pushed to branch master at Pacman / Pacman


Commits:
160f5bec by Daan De Meyer at 2021-09-04T13:34:58+10:00
pacman-key: Add --quiet to a few more gpg invocations

Currently, when running pacman-key --populate, gpg prints the
trustdb check output once for each locally signed and revoked key.
When bootstrapping a new container image, about 50 keys get signed
and revoked which leads to a huge amount of output when running
pacman-key which is repeated 50x.

To avoid overloading the user with gpg output, we add --quiet to the gpg
calls generating the trustdb checking output to silence those calls which
gets rid of the trustdb check output on the terminal.

Signed-off-by: Daan De Meyer <daan.j.demeyer at gmail.com>
Signed-off-by: Allan McRae <allan at archlinux.org>

- - - - -
c7e4f459 by Daan De Meyer at 2021-09-04T13:43:26+10:00
pacman-key: Reduce gpg trustdb checks

Every time we modify gpg's state by signing or revoking a key, gpg
marks the trustdb as stale and rechecks it the next time key_is_lsigned()
or key_is_revoked() is called.

Currently, we alternate calls signing of keys and calling key_is_lsigned()
(idem for revoking) which means that for each key we sign (or revoke), gpg
will check the trustdb once.

To avoid checking the trustb so many times, we can simply do all the
key_is_lsigned() and key_is_revoked() checks upfront. Inbetween read
operations the trustdb is not marked stale and inbetween write operations
the trustdb is also not marked stale. This reduces the amount of trustdb
checks from 50 to 1.

Signed-off-by: Allan McRae <allan at archlinux.org>

- - - - -
4c3c0e06 by Allan McRae at 2021-09-04T16:16:20+10:00
Update translations from Transifex

Signed-off-by: Allan McRae <allan at archlinux.org>

- - - - -


25 changed files:

- lib/libalpm/po/LINGUAS
- lib/libalpm/po/ar.po
- lib/libalpm/po/ast.po
- lib/libalpm/po/bg.po
- lib/libalpm/po/br.po
- lib/libalpm/po/ca.po
- lib/libalpm/po/cs.po
- lib/libalpm/po/da.po
- lib/libalpm/po/de.po
- lib/libalpm/po/el.po
- lib/libalpm/po/en_GB.po
- lib/libalpm/po/eo.po
- lib/libalpm/po/es.po
- lib/libalpm/po/es_419.po
- lib/libalpm/po/eu.po
- lib/libalpm/po/eu_ES.po
- lib/libalpm/po/fi.po
- lib/libalpm/po/fr.po
- lib/libalpm/po/gl.po
- lib/libalpm/po/hi.po
- lib/libalpm/po/hr.po
- lib/libalpm/po/hu.po
- lib/libalpm/po/id.po
- lib/libalpm/po/it.po
- lib/libalpm/po/ja.po


View it on GitLab: https://gitlab.archlinux.org/pacman/pacman/-/compare/5da4af2b5dcb6f214a93fd5cabf228df08d006f5...4c3c0e06e5ec1637f06dcebcb2bd64373da55106

-- 
View it on GitLab: https://gitlab.archlinux.org/pacman/pacman/-/compare/5da4af2b5dcb6f214a93fd5cabf228df08d006f5...4c3c0e06e5ec1637f06dcebcb2bd64373da55106
You're receiving this email because of your account on gitlab.archlinux.org.




More information about the pacman-dev mailing list