-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maybe skip "gpg: refreshing 13 keys" #45
Comments
On a second thought, https://keyserver.ubuntu.com/pks/lookup?search=0x974C8BE49078F532&fingerprint=on&op=index has an expiration date, so without the refresh things would stop working on 2021-06-19 and we'd need a new installer after the key is extended again and before 2021-06-19. Not very hard, but easy to forget I guess. But the time savings are compelling. hmm.... |
It's absolutely ok!
Maybe we should have some environment variable to customize this and other similar details. That would allow to skip all of them, but force the "default" behaviour when we need it. From the Action, we can decide when to set/unset that variable by checking some api/file/release. I guess any API call will take a second. Moreover, skipping these kind of checks can be the default behaviour when |
Continuing my journey to nitpick everything. I hope that's OK.
So, on the first start we have:
Which means 11 seconds lost for basically no change. (the thing executed here is this I think: https://github.com/msys2/MSYS2-packages/blob/3a99587ca16686fd0e2e74ffacabd2be15dd85ae/filesystem/07-pacman-key.post#L7)
I wonder if we should somehow skip that part. If we ever need to update the existing keys before an update we can always push out a new installer and update the action to use it. I haven't thought about how to skip it yet.
The text was updated successfully, but these errors were encountered: