From: Jelle Licht <jlicht@fsfe.org>
To: 60065@debbugs.gnu.org
Subject: bug#60065: fwupd can not find required polkit actions
Date: Wed, 14 Dec 2022 14:06:12 +0100 [thread overview]
Message-ID: <87tu1ym8xn.fsf@fsfe.org> (raw)
The package description for fwupd looks for polkit actions in the polkit
output. There are multiple ways to patch this.
--8<---------------cut here---------------start------------->8---
(add-before 'configure 'set-polkit-rules-dir
;; Locate actions in our {output,etc-dir}, not that of the polkit input.
(lambda _
(setenv "PKG_CONFIG_POLKIT_GOBJECT_1_ACTIONDIR"
;; This makes it 'Just Work':
;; (string-append #$output "/share/polkit-1/actions")
;; This only makes it work when we extend polkit-service-type:
(string-append "/etc/polkit-1/actions")
)))
--8<---------------cut here---------------end--------------->8---
Example service definition:
--8<---------------cut here---------------start------------->8---
(define (fwupd-shepherd-service package)
"Return a Shepherd service to start fwupd."
(list (shepherd-service
(requirement '(dbus-system))
(provision '(fwupd))
(start #~(make-forkexec-constructor
(list #$(file-append package "/libexec/fwupd/fwupd"))))
(stop #~(make-kill-destructor)))))
(define-public fwupd-service-type
(service-type
(name 'fwupd)
(description "Setup the firmware update deamon.")
(default-value fwupd)
(extensions
(list
(service-extension profile-service-type list)
(service-extension polkit-service-type list)
(service-extension dbus-root-service-type list)
(service-extension shepherd-root-service-type
fwupd-shepherd-service)))))
--8<---------------cut here---------------end--------------->8---
If we go for the first fix, the polkit-service-type extension is not
required. If we go for the /etc fix, the polkit-service-type extension
is required. I know too little about polkit to make an informed choice
here, so with some guidance I could work on a patch to close this issue.
- Jelle
reply other threads:[~2022-12-14 13:07 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tu1ym8xn.fsf@fsfe.org \
--to=jlicht@fsfe.org \
--cc=60065@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).