Michael Schroeder
Michael Schroeder
Our sign tool already supports a '-4' option, so implementing this just means using this option in the call.
Maybe it's a good idea to also return the pubkey version with the fingerprint if you're adding a new API function.
> How do you imagine rpm or an application that uses the library using this information? Lets say you want to put the key in a database so that you...
Are you really arguing that the keyid would have been enough in the signature and switching to the fingerprint was a mistake? Note that the fingerprint subpackage does include the...
That would be easy to implement with an expression: ``` %pytest %[isarch("s390x") ? "|| :" : ""] ``` Would that be ok or is it not short enough?
That's `%isarch` the macro, i used `isarch()` the expression function. But we can certainly do it with a macro. But it needs to be able a accept multiple architectures like...
Using a bit of lua: ``` %contains() %{lua: arg1 = arg[1] for i = 2, #arg do if arg1 == arg[i] then return 1 end end return 0 } %isarch()...
The next time the key gets autoextended you should automatically get a sha256 binding signature. You can force this with `osc signkey --extend`.
Argh, I looked at the old parseSpecParts.c instead of parseSpecParts.cc by mistake. Sorry for the noise. (I wonder why git did not delete the old files...)
AFAIR if the packages contain no files, they wont get any color.