Open verygreen opened 1 year ago
The somewhat trivial fix is here: https://github.com/QubesOS/qubes-manager/pull/349
though I guess it does not like my lack of signature?
though I guess it does not like my lack of signature?
Would you mind generating a key and using it to sign your code? Instructions are provided here:
I signed the commit, but it's still unhappy.
I signed the commit, but it's still unhappy.
Hmm, did you upload your key to one of the approved keyservers?
there are references to "A key server", in that code signing document, but no instructions how to do it or what those servers are.
It's in this section:
sorry, somehow missed it. Should be all good now.
ha, "Great,", now it failed CI seemingly due to unrelated failure to fetch some fedora updates or some such. is there a way to retrigger the test?
Don’t worry @verygreen, it isn’t your fault :smile:. I just issued a command that will cause all the failed runs to be retried.
https://github.com/QubesOS/qubes-manager/pull/349 was merged a long time ago, but it says that it fixes https://github.com/QubesOS/qubes-issues/issues/8056, not this issue.
Should this issue still be open?
Qubes OS release
4.1.2
Brief summary
When renaming a qube (e.g. template) failes because there's disp vm running, a message is printed that outlines the failure. This message lists the qube name three times where clearly one of those occurrences is supposed to list the new desired name.
Steps to reproduce
Tename a template that has a dispvm running