From: haunma <haunma@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: fwupd refresh fails with "signatures were required, but none supplied"
Date: Fri, 29 Dec 2023 22:01:28 +0100 [thread overview]
Message-ID: <20231229210128.M-Ogmtm2R5aOHKIiDlTH4SVHz_YcaL3hUlwPHM1rXG4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47932@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
New comment by haunma on void-packages repository
https://github.com/void-linux/void-packages/issues/47932#issuecomment-1872335685
Comment:
Was this a fresh install, running fwupdmgr for ths first time?
I'm sure that it works once the proper keys are installed. The trouble is, it's not clear how to get to that point.
next prev parent reply other threads:[~2023-12-29 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 0:30 [ISSUE] " haunma
2023-12-29 9:17 ` sgn
2023-12-29 21:01 ` haunma [this message]
2023-12-31 16:15 ` [ISSUE] [CLOSED] " sgn
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=20231229210128.M-Ogmtm2R5aOHKIiDlTH4SVHz_YcaL3hUlwPHM1rXG4@z \
--to=haunma@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).