Kenyon Ralph

@parryb @voxpupuli is a collective of volunteers, so when someone volunteers to maintain a module is when it will be maintained.

Duplicates #155

This can be done with webserver configuration.

https://github.com/google/fonts#self-host-fonts-available-from-google-fonts -> https://fontsource.org/docs/getting-started/install Not sure how this would be integrated into puppetboard in a maintainable way since it doesn't use npm at all yet, as far as I know.

What is the full error message? It should give you filenames and line numbers. Seems like this is coming from your code, because the package resource is only declared once...

The commit message check wants only a PA jira issue ID, but the issue for this is in the MODULES jira project. Caused by #642.

@mhashizume already did that. That's what the last force push was. Commit e48620a6c61c5c4c753d817eb8004a753c4bb887 is on top of current `main`.

FWIW I'm using this plus puppetlabs-apt at https://github.com/puppetlabs/puppetlabs-apt/commit/cb21d0b93f3b44130adef034b58ef3f2193640e3 on my infrastructure, and it does the right thing on Ubuntu 18.04, 20.04, and 22.04.

Modern APT keyring format also needs to be used in `puppet_enterprise::repo::config`, which doesn't use puppetlabs-apt. Bug report: https://github.com/puppetlabs/puppet-enterprise_issues/issues/2

I'm not seeing why the Debian tests would be running on Windows agents, and why my changes would cause these test failures.