I think I never talked to him :(

mayeb 10 years ago in an issue

ewoud: release worked

have we validated that the metadata on the new packages properly replaces & removes the legacy puppet packages? If so, I'd like to clean up the install pages quite a bit.

I think on debian they keep around with the rc status? Which is "package is removed, but config files are still around"

but then because the openvox packages "own" the same config files, purging legacy won't remove them, right?

I'm not sure which files the old package refers to, but I could purge it and everything was still working

I didn't care enough to debug it

binford2k: if it's about RPMs, https://github.com/OpenVoxProject/openvox-agent/pull/21 is IMHO still a good idea

I think it is too

binford2k: press tha button!

lol, I'll go look more at it

but also, https://github.com/voxpupuli/voxpupuli.github.io/pull/463

computer says no

silly computer

bastelfreak++

\o/

ewoud: https://github.com/voxpupuli/voxpupuli-test/pull/153 \o/

no need for PSH in unit tests & static validation anymore \o/

bastelfreak: neat!

binford2k: about purging legacy puppet-agent, I just did that on my Debian machines. it's a noop. the only thing that gets run by

/var/lib/dpkg/info/puppet-agent.postrm

is

systemctl daemon-reload

just also did the same (with

aptitude purge ~c

, meaning purge packages that still have config files hanging around) on my primary server and that was a noop too. purged puppet-agent, puppet-release, puppetdb, and puppetserver

[thread]: i wrote a shell script called

catalog

that finds and `cat`s the cached catalog file ... i have

catalog | jq -r -M '.resources[]|select(

as muscle memory at this point 😁

Nice yubikey?

ewoud: you need to go to bed!

bastelfreak: but I don't want to :(

I know :(

kenyon++