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.

Sign up for GitHub

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

Jump to bottom

Debian >=9 has the same new GPG key than ubuntu >= 16 #193

Closed
sinfomicien opened this issue Apr 18, 2018 · 1 comment
Closed

Debian >=9 has the same new GPG key than ubuntu >= 16 #193

sinfomicien opened this issue Apr 18, 2018 · 1 comment
Assignees
@sinfomicien
Milestone
1.5.4

Comments

@sinfomicien
Copy link
Contributor

When installing package from mariadb reporistory... The new key used for Ubuntu >=16 is the same used for Debian >=9.

Will push a PR as soon as i fully tested my change locally.
@sinfomicien sinfomicien self-assigned this Apr 18, 2018
sinfomicien added a commit to sinfomicien/mariadb that referenced this issue Apr 19, 2018
@sinfomicien
Correct issue sous-chefs#193, which appeared in Debian >=9
8ce40db
sinfomicien added a commit to sinfomicien/mariadb that referenced this issue Apr 20, 2018
@sinfomicien
Merge pull request #2 from sinfomicien/correct-issue-#193
ef21a25 
Correct issue sous-chefs#193, which appeared in Debian >=9
damacus added a commit to sinfomicien/mariadb that referenced this issue May 15, 2018
@damacus
Merge branch 'master' into correct-issue-sous-chefs#193
176c03a
@sinfomicien sinfomicien added this to the 1.5.4 milestone May 21, 2018
sinfomicien added a commit to sinfomicien/mariadb that referenced this issue May 22, 2018
@sinfomicien
Merge branch 'master' into correct-issue-sous-chefs#193
244f009
sinfomicien added a commit that referenced this issue May 22, 2018
@sinfomicien
Correct issue #193, which appeared in Debian >=9
52eb083
@lock
Copy link

lock bot commented May 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sinfomicien sinfomicien

Labels
None yet
Projects
None yet
Milestone
1.5.4
Development

No branches or pull requests
1 participant
@sinfomicien