sincerelysaucy

I think what we have right now is working well enough, and the ticket can close. The "centos-stream+epel-8-x86_64.cfg" and similar, epel enabled configs seem to work quite well.

Since RHEL is now the downstream of CentOS, which is the beta test release for RHEL, I don't expect frequent issues. The potential for that sort of issue is real,...

*Really*? I personally build a while suite of stuff that uses python 3.11, not building that RPM itself, and hadn't seen any issue. Do you have a pointer to that...

I just did, it works great. I suspect you have another issue. * mock install python3.11 -r /etc/mock/centos-stream+epel-8-x86_64.cfg Maybe ensure your "mock" and "mock-core-configs" are up to date, and scrub...

I think you have a PEBKAC moment there. Your command three should not have that "-rpm" suffix. Try this: 3. mock -r centos-stream+epel-8-x86_64 --install python3.11

Forgive my confusion, the PEBKAC was on my end, I was seeing the "python3.11 rpm" rather than the "python3.11-rpm" package. As far as why enabling epel doesn't automatically enable epel-next,...

If it's going to stick around, the could should be labeled for RHEL 6, not "RHL 6". No on, and I mean *no one* referred to Red Hat 6 as...

/etc/supervisor.d is mostly where systemd stores content. Don't try to outsmart systemd: Rather than using "bitwarden.sh" directly, create a systemd for bitwarden and enable the designated service user to start...

Check your diskspace? The upgrade command can leave a lot of debris, especially if an update failed. And "/var/lib/docker/" can wind up overwhelmed by other content in the "/var/" partition,...

The #232 actually is related. If you manually install "docker-compose", the "bitwarden.sh" script is written to use it by preference. And it's obsolete and unsupported, and should no longer even...