[pacman-dev] [GIT] The official pacman repository branch, master, updated. v5.2.1-3-g091b244d
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "The official pacman repository".
The branch, master has been updated via 091b244d0ffa281ba9968606184d709e59c2a2d5 (commit) via e1f5f2198370400565c1eb4ca342299767383f65 (commit) via 7be75523297875dacfad9083b0663a04bf823a3e (commit) from f6564377a2b0a0dd6294fb366a3f91a31142e124 (commit)
Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below.
- Log ----------------------------------------------------------------- commit 091b244d0ffa281ba9968606184d709e59c2a2d5 Author: Matthew Sexton wsdmatty@gmail.com Date: Mon Nov 4 22:30:06 2019 -0500
pacman-key: ignore already lsigned/deleted keys
Added two new functions, key_is_lsigned() and key_is_revoked() that check whether a key has been locally signed or revoked respectively during --populate. If the key is already signed or revoked, it is quietly ignored.
Suggested-by: Eli Schwartz eschwartz@archlinux.org Signed-off-by: Matthew Sexton wsdmatty@gmail.com Signed-off-by: Allan McRae allan@archlinux.org
commit e1f5f2198370400565c1eb4ca342299767383f65 Author: Matthew Sexton wsdmatty@gmail.com Date: Sun Nov 3 23:43:00 2019 -0500
pacman-key: hide lsign and revoke output behind --verbose
To cut down on spam during --populate, both locally signing and revoking keys now hide the specific keys being signed or revoked, but can be shown with --verbose. A count was added, to show the number of keys signed/revoked during the process.
Partially Implements: FS#64142 - pacman-key: make populate less noisy
Signed-off-by: Matthew Sexton wsdmatty@gmail.com Signed-off-by: Allan McRae allan@archlinux.org
commit 7be75523297875dacfad9083b0663a04bf823a3e Author: Ethan Sommer e5ten.arch@gmail.com Date: Sun Nov 3 19:45:04 2019 -0500
libmakepkg: add optional argument support to parseopts
Adds a "?" suffix that can be used to indicate that an option's argument is optional.
This allows options to have a default behaviour when the user doesn't specify one, e.g.: --color=[when] being able to behave like --color=auto when only --color is passed
Options with optional arguments given on the command line will be returned in the form "--opt=optarg" and "-o=optarg". Despite that not being the syntax for passing an argument with a shortopt (trying to pass -o=foo would make -o's argument "=foo"), this is done to allow the caller to split the option and its optarg easily
Signed-off-by: Ethan Sommer e5ten.arch@gmail.com Reviewed-by: Dave Reisner dreisner@archlinux.org Signed-off-by: Allan McRae allan@archlinux.org
-----------------------------------------------------------------------
Summary of changes: scripts/libmakepkg/util/parseopts.sh.in | 116 ++++++++++++++++++++------------ scripts/pacman-key.sh.in | 56 +++++++++++++-- test/scripts/parseopts_test.sh | 12 +++- 3 files changed, 135 insertions(+), 49 deletions(-)
hooks/post-receive
participants (1)
-
Allan McRae