From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: lib/portage/sync/modules/webrsync/, /
Date: Tue, 6 Jun 2023 10:32:24 +0000 (UTC) [thread overview]
Message-ID: <1686047416.3dc119d927916e75d380a692bd9bca32fd9d42fe.sam@gentoo> (raw)
commit: 3dc119d927916e75d380a692bd9bca32fd9d42fe
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 6 10:12:29 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jun 6 10:30:16 2023 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=3dc119d9
sync: webrsync: fix keyserver variable typo
Much like with the news item issues, I think we need some full
end-to-end tests for sync.
Bug: https://bugs.gentoo.org/907816
Signed-off-by: Sam James <sam <AT> gentoo.org>
NEWS | 6 ++++++
lib/portage/sync/modules/webrsync/webrsync.py | 2 +-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index e059505bd..8727e5623 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,9 @@
+portage-3.0.48.1 (2023-06-06)
+----------------
+
+Bug fixes:
+* sync: webrsync: Fix syncing with keyserver explicitly specified (bug #907816).
+
portage-3.0.48 (2023-06-01)
--------------
Breaking changes:
diff --git a/lib/portage/sync/modules/webrsync/webrsync.py b/lib/portage/sync/modules/webrsync/webrsync.py
index 2c65486d0..0e1d1a463 100644
--- a/lib/portage/sync/modules/webrsync/webrsync.py
+++ b/lib/portage/sync/modules/webrsync/webrsync.py
@@ -103,7 +103,7 @@ class WebRsync(SyncBase):
] = self.repo.sync_openpgp_key_path
self.spawn_kwargs["env"][
"PORTAGE_GPG_KEY_SERVER"
- ] = self.repo.sync_openpgp_key_server
+ ] = self.repo.sync_openpgp_keyserver
webrsync_cmd = [self.bin_command]
if verbose:
reply other threads:[~2023-06-06 10:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1686047416.3dc119d927916e75d380a692bd9bca32fd9d42fe.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-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