Erik Berg

> One other comment I will make about bringing back 5.0 is it grows the testing matrix substantially to add another version. It already takes something like 2 hours to...

Ok, so I took a 32nd look at this code, and there is a flaw here. It was always there, but the ansible python database dependencies are installed on the...

During the refactoring of zabbix_proxy I noticed more variables (`zabbix_server_install_database_client`) that we could take advantage of. So I've brought those features over here by updating the commits that affect those....

Apologies for the hold up, been busy trying to get my own actions-runner working so I can get these results myself, as currently I'm currently just testing against [a few...

Apologies for the hold-up. To borrow a sentence from @fasterthanlime > GitHub actions-runners do not spark joy. So there are the important changes since last; - using pymysql for all...

Just adding a note here as I took a look at cleaning up the selinux.yml tasks. I think the inclusion of selinux.yml needs to move into main.yml after the zabbix...

> I think the inclusion of selinux.yml needs to move into main.yml after the zabbix packages are installed for some of the sebooleans to exist. I was completely wrong about...

> Unrelated to this: I delivered a PR to address an architecture issue I encountered with the Raspbian support: > #1060 > It is closed, but maybe it can be...

> But you're probably right that `Suites:` should be based on the lsb.id. Actually, it should probably just say `zabbix` here? Looking at https://repo.zabbix.com/zabbix/6.4/raspbian/dists/bullseye/Release `Suite: zabbix`, or maybe it doesn't...

> @eb4x Are you using HCO to deploy the kubevirt components are are you doing a more custom setup? Yep, I'm using the HCO to deploy. > Make sure that...