Bug 360461

Summary:	repoman should help out when PORTAGE_GPG_KEY is not valid
Product:	Portage Development	Reporter:	SpanKY <vapier>
Component:	Repoman	Assignee:	Portage team <dev-portage>
Status:	RESOLVED WONTFIX
Severity:	enhancement	CC:	pva, williamh
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description SpanKY gentoo-dev

2011-03-25 18:25:16 UTC

as follow up to Bug 360459, if PORTAGE_GPG_KEY is not set or has expired, it'd be great to automate the new key generation step.

so when this situation occurs, we can initially show the message:
 Please set up a PORTAGE_GPG_KEY signing key:
 http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=6

for now, i guess we'll want to just warn rather than have it be fatal.

as a follow up, we could even automate the gpg step for people.  ask them if they want repoman to generate a key for them.  this would require some new make.conf settings:
  PORTAGE_GPG_NAME
  PORTAGE_GPG_EMAIL
  PORTAGE_GPG_COMMENT
these would be used to populate the different fields requested by gpg for a DSA 2048bit signing key.  once gpg has been executed, we show to the user the PORTAGE_GPG_KEY setting that they need.

Comment 1 Sam James archtester

2022-07-12 03:18:38 UTC

repoman support has been removed per bug 835013.

Please file a new bug (or, I suppose, reopen this one) if you feel this check is still applicable to pkgcheck and doesn't already exist.