869467 – sys-apps/portage: gpkg-sign doesn't work as unprivileged user

Bug 869467 - sys-apps/portage: gpkg-sign doesn't work as unprivileged user

Summary: sys-apps/portage: gpkg-sign doesn't work as unprivileged user

Status:	CONFIRMED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Binary packages support (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2022-09-10 11:06 UTC by Michał Górny
Modified:	2023-05-01 10:01 UTC (History)
CC List:	2 users (show)

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 Michał Górny archtester

2022-09-10 11:06:27 UTC

$ gpkg-sign inkscape-1.2.1-r2-1.gpkg.tar 
!!!
flock: cannot open lock file /run/lock/portage-binpkg-gpg.lock: Permission denied
 * Signature exception: inkscape-1.2.1-r2-1.gpkg.tar


I think it wouldn't be unreasonable to make it work as non-root ;-).

Comment 1 Sheng Yu 2022-09-10 20:28:31 UTC

You can set the lock to somewhere that allow read/write in make.conf

BINPKG_GPG_SIGNING_BASE_COMMAND="/usr/bin/flock /tmp/portage-binpkg-gpg.lock /usr/bin/gpg --sign --armor [PORTAGE_CONFIG]"