already committed UDFs will be signed
This happens if you have two trusted machines, and you generate UDF on one, commit (ie: c7328ed8), then pull&&sign on the other.
The old code will not sign the UDFs, because they're not new to git. It would sign them if I manually rsync'ed, but that's not what I did.
The new code will work regardless of the git status, and will sign anything that needs to be signed:
- it involves
${VERSION}
- it doesn't have a valid signature
closes #19665 (closed)
Edited by boyska