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

Debian11 Bullseye config #1439

Closed
wants to merge 4 commits into from
Closed

Debian11 Bullseye config #1439

wants to merge 4 commits into from

Conversation

ap-16
Copy link

@ap-16 ap-16 commented Sep 9, 2021

I have changed my local instance accordingly

@ap-16 ap-16 requested a review from a team as a code owner September 9, 2021 12:16
@CLAassistant
Copy link

CLAassistant commented Sep 9, 2021

CLA assistant check
All committers have signed the CLA.

@puppet-community-rangefinder
Copy link

mysql::bindings::python is a class

Breaking changes to this file WILL impact these 1 modules (exact match):
Breaking changes to this file MAY impact these 14 modules (near match):

mysql::params is a class

Breaking changes to this file WILL impact these 2 modules (exact match):
Breaking changes to this file MAY impact these 1 modules (near match):

This module is declared in 142 of 578 indexed public Puppetfiles.


These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

align version name `bullseye´ in comment with version number `11´
@bastelfreak
Copy link
Collaborator

thanks for the PR. could you add debian 11 to the metadata.json? https://github.com/puppetlabs/puppetlabs-mysql/blob/main/metadata.json

Tim Meusel <notifications@github.com> wants me to add this entry
@daianamezdrea
Copy link
Contributor

Hi @ap-16, sorry for the late answer but our team went through some transformations, can you rebase your PR in order to have everything green and ready to merge? Thank you and sorry again

@github-actions
Copy link

This PR has been marked as stale because it has been open for a while and has had no recent activity. If this PR is still important to you please drop a comment below and we will add this to our backlog to complete. Otherwise, it will be closed in 7 days.

@github-actions github-actions bot added the stale label May 15, 2022
@github-actions github-actions bot closed this May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants