Skip to content
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

Update the gpg key of the repo.aptly.info repository in the README #1052

Merged
merged 1 commit into from
Mar 30, 2022

Conversation

maciej-gol
Copy link
Contributor

Fixes

Using the gpg key in the README:

Err:1 http://repo.aptly.info squeeze InRelease                                                         
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EE727D4449467F0E

Requirements

All new code should be covered with tests, documentation should be updated. CI should pass.

Description of the Change

The actual repo uses different gpg key. Either the repo has been taken over, or the README is out of date.

Checklist

  • unit-test added (if change is algorithm)
  • functional test added/updated (if change is functional)
  • man page updated (if applicable)
  • bash completion updated (if applicable)
  • documentation updated
  • author name in AUTHORS

@randombenj randombenj self-requested a review March 30, 2022 12:24
@randombenj randombenj merged commit c46f12f into aptly-dev:master Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants