From: Matthew Thode <prometheanfire@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH][v3] enable user settable gpg keyservers (attached)
Date: Tue, 26 Feb 2019 15:33:53 -0600 [thread overview]
Message-ID: <20190226213353.lneq5smuvehn5cgk@gentoo.org> (raw)
In-Reply-To: <d9c68d1a-4d77-cbaf-2d94-b7111f9cbad8@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2329 bytes --]
On 19-02-26 10:52:52, Zac Medico wrote:
> On 2/26/19 10:48 AM, Zac Medico wrote:
> > On 2/25/19 1:45 PM, Matthew Thode wrote:
> >> On 19-02-25 15:41:03, Matthew Thode wrote:
> >>> On 19-02-25 14:34:46, Matthew Thode wrote:
> >>>> Allowing users to define which keyservers they update from allows them
> >>>> to work around buggy keyservers. It is also useful for local mirrors
> >>>> and / or private keyservers.
> >>>>
> >>>> It's likely that I'm setting the default incorrectly and not
> >>>> alphabetizing right, but the code works at least...
> >>>>
> >>>
> >>> Ok, let's try that again, should be cleaner/better/etc
> >>>
> >>
> >> v3, attached
> >>
> >> ---
> >
> >> lib/portage/repository/config.py | 6 ++++++
> >> lib/portage/sync/syncbase.py | 6 +++---
> >> 2 files changed, 9 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/lib/portage/repository/config.py b/lib/portage/repository/config.py
> >> index 482711c4b..235371ce5 100644
> >> --- a/lib/portage/repository/config.py
> >> +++ b/lib/portage/repository/config.py
> >> @@ -109,6 +109,7 @@ class RepoConfig(object):
> >> 'sync_allow_hardlinks',
> >> 'sync_depth',
> >> 'sync_hooks_only_on_change',
> >> + 'sync_openpgp_keyserver',
> >> 'sync_openpgp_key_path',
> >> 'sync_openpgp_key_refresh_retry_count',
> >> 'sync_openpgp_key_refresh_retry_delay_exp_base',
> >> @@ -224,6 +225,9 @@ class RepoConfig(object):
> >> self.sync_allow_hardlinks = repo_opts.get(
> >> 'sync-allow-hardlinks', 'true').lower() in ('true', 'yes')
> >>
> >> + self.sync_openpgp_keyserver = repo_opts.get(
> >> + 'sync-openpgp-keyserver', 'hkps.pool.sks-keyservers.net').strip.lower()
> >
> > It needs to be like this:
> >
> > + 'sync-openpgp-keyserver', 'hkps.pool.sks-keyservers.net').strip().lower() or None
> >
> > because gemato handles None but not empty strings.
>
> Also let's not provide a default keyserver, let gemato handle that.
>
> Also please update man/portage.5.
>
Ok, that stanza no reads:
self.sync_openpgp_keyserver = repo_opts.get(
'sync-openpgp-keyserver').strip.lower() or None
I didn't see a section for the sync-openpgp options though, let me know
anything else or I'll send the updated patch tonight.
--
Matthew Thode (prometheanfire)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-26 21:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 20:34 [gentoo-portage-dev] [PATCH] enable user settable gpg keyservers Matthew Thode
2019-02-25 20:59 ` Michał Górny
2019-02-25 21:27 ` Matthew Thode
2019-02-25 21:41 ` Matthew Thode
2019-02-25 21:44 ` [gentoo-portage-dev] [PATCH][v3] " Matthew Thode
2019-02-25 21:45 ` [gentoo-portage-dev] [PATCH][v3] enable user settable gpg keyservers (attached) Matthew Thode
2019-02-26 18:48 ` Zac Medico
2019-02-26 18:52 ` Zac Medico
2019-02-26 21:33 ` Matthew Thode [this message]
2019-03-03 21:43 ` [gentoo-portage-dev] [PATCH][v4] enable user settable gpg keyservers Matthew Thode
2019-03-31 19:47 ` Zac Medico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190226213353.lneq5smuvehn5cgk@gentoo.org \
--to=prometheanfire@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox