Hello,
I have uploaded packages to deken, but have just found out, that these packages were not signed correctly with my gpg key for reasons totally unrelated to deken.
Should I reupload the packages or should I sign these packages with gpg, get the signature extension .gpg (or .asc or .sig), and should I upload those signatures via the webinterface to https://puredata.info/Members/residuum/software/purest_json/2.0.0/
Thanks, Thomas
Am 30. November 2022 00:35:47 MEZ schrieb Thomas Mayer thomas@residuum.org:
Hello,
I have uploaded packages to deken, but have just found out, that these packages were not signed correctly with my gpg key for reasons totally unrelated to deken.
Should I reupload the packages or should I sign these packages with gpg, get the signature extension .gpg (or .asc or .sig), and should I upload those signatures via the webinterface to https://puredata.info/Members/residuum/software/purest_json/2.0.0/
deken uses detached signatures (.asc files), so you only need to (re)upload the signatures themselves (eg using the webinterface).
mfg.sfg.jfd IOhannes