notary: Use separate input and output directories #1090
Conversation
|
The notary image appears to be the only one where we don't pinpoint a specific numeric version of the image to build and use, does anyone know if that was an oversight or was it deliberate? |
FWIW, there's no discussion on #252 about why we did it this way at the time. At the very least, we are setting Off the top of my head, I can't think of any reason why pinning the notary runner to a specific tag would be a bad idea. |
Ok, I'll start that by specifying |
After content-addressable tarballs is merged, clearsigning will be performed on spec manifest files, without changing the name of the file. To prevent issues with gpg overwriting files, this change puts re-signed files into a different directory from the original files.
scottwittenburg
force-pushed
the
fix-signing-for-content-addressed
branch
from
3c670ed to
7152074
Compare
|
Noting for posterity that the lack of image bump in |
After content-addressable tarballs is merged, clearsigning will be performed on spec manifest files, without changing the name of the file. This change keeps the original file name when re-signing, and to prevent issues with gpg overwriting files, it puts re-signed files into a different directory from the original files.
This can be merged before the content-addressable tarballs spack PR.