457106 – repoman uses $HOME/.gnupg/gpg.conf instead of $PORTAGE_GPG_DIR/.gpg.conf

Bug 457106 - repoman uses $HOME/.gnupg/gpg.conf instead of $PORTAGE_GPG_DIR/.gpg.conf

Summary: repoman uses $HOME/.gnupg/gpg.conf instead of $PORTAGE_GPG_DIR/.gpg.conf

Status:	RESOLVED WONTFIX

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Repoman (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2013-02-13 15:55 UTC by Agostino Sarubbo
Modified:	2022-07-12 03:18 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Agostino Sarubbo gentoo-dev

2013-02-13 15:55:17 UTC

Suppose I have 2 gpg keys. The first is located into /home/ago/.gnupg and the second in /media/gnupg/                                                                                                                                                                       
                                                                                                                                                                                    
If my PORTAGE_GPG_DIR is set to /media/gnupg is expected I would use that key, but portage take the conf from /home/ago/.gnupg/gpg.conf

Comment 1 Zac Medico gentoo-dev

2013-02-13 15:58:14 UTC

Portage should be using the command defined by PORTAGE_GPG_SIGNING_COMMAND. The default value from /usr/share/portage/config/make.globals is:

PORTAGE_GPG_SIGNING_COMMAND="gpg --sign --digest-algo SHA256 --clearsign --yes --default-key \"\${PORTAGE_GPG_KEY}\" --homedir \"\${PORTAGE_GPG_DIR}\" \"\${FILE}\""

Maybe we need to use some different options.

Comment 2 Sam James archtester

2022-07-12 03:18:32 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.