W: GPG error: http://apt.puppet.com jammy InRelease: The following
signatures were invalid: EXPKEYSIG 4528B6CD9E61EF26 Puppet, Inc. Release
Key (Puppet, Inc. Release Key)
E: The repository 'http://apt.puppet.com jammy InRelease' is not signed.
The Puppet Slack channel appears to no longer exist
Am Mittwoch, dem 09.04.2025 um 14:15 -0700 schrieb stide...@gmail.com:
> It's no longer fully Open Source.
Well, Puppet still is. The PuppetLabs packages are not. Just use the
ones from Debian/Ubuntu or those from the OpenVox project.
HTH...
Dirk
--
Dirk Heinrichs
Senior Systems Engineer, Del
I got the impression it won't be fixed. Puppet has been acquired by
Perforce and will only allow registered users a maximum of 25 nodes to be
managed. It's no longer fully Open Source.
https://www.puppet.com/blog/open-source-puppet-updates-2025
On Wednesday, April 9, 2025 at 12:25:40 AM UTC+10
Hi Tom,
Encountered a GPG error while updating the Puppet repository. The
error message indicates an expired key 4528B6CD9E61EF26. How can I resolve
this issue, and is there an estimated timeframe for a fix from Puppet?
On Tuesday, April 8, 2025 at 1:53:21 AM UTC+5:30 t...@nalca.bio wr
On Mon, Apr 7, 2025 at 4:12 PM Dietrich, Stefan
wrote:
> Hello Tom,
>
> the future key [1] still works. It has the same ID as
> DEB-GPG-KEY-puppet-20250406, but without an expiry date.
>
> Regards,
> Stefan
>
> [1] https://apt.puppet.com/DEB-GPG-KEY-future
Hi Stefan,
Thanks for taking the time
Hello Tom,
the future key [1] still works. It has the same ID as
DEB-GPG-KEY-puppet-20250406, but without an expiry date.
Regards,
Stefan
[1] https://apt.puppet.com/DEB-GPG-KEY-future
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubs
