thanks for the response, however my supercow powers are NOT so great,
reading repo options-> gpgkey ; doesn’t get me, personally, any closer, to what is expected behaviour and what I’m to do if I’m supposed to ‘squelch’ the message.
gpgkey list of strings
URLs of a GPG key files that can be used for signing metadata and packages of this repository, empty by default. If a file can not be verified using the already imported
keys, import of keys from this option is attempted and the keys are then used for verification.
this seems to have come about after qubes-secpack/QSBs/qsb-067-2021.txt at master · QubesOS/qubes-secpack · GitHub
After installing the updates in dom0, it is necessary to install updates
in Fedora-based TemplateVMs and StandaloneVMs. This can be
done via the Qubes Update tool [4] or using qubesctl (salt) as follows:
$ sudo qubesctl --skip-dom0 --templates state.sls update.qubes-vm
After installing the updates in dom0, it is necessary to install updates
in Fedora-based TemplateVMs and StandaloneVMs. This can be
done via the Qubes Update tool [4] or using qubesctl (salt) as follows:
$ sudo qubesctl --skip-dom0 --templates --standalones state.sls update.qubes-vm
actually fails FWIW.
maybe its more of a fedora error message, that I might look up elsewhere, but was asking here.
seems to be something simliar going on in Fed33 templates for this person