facter VS osinfo-db

I'm just wondering whether I'm the only one who's wondering how to access Puppet's ticket system nowadays? On the one hand I was stumbling over a bug in Facter last week which luckily has been fixed in the meantime because obviously someone else spotted it as well.

or using community package: https://docs.ansible.com/ansible/latest/collections/community/general/facter_module.html which uses this: https://github.com/puppetlabs/facter

The latest major version of Facter—Puppet's tool for collecting system information—has been out for some time now. However, we've been hard at work fixing bugs ever since. The fact that Facter has to be able to run on a variety of operating systems and architectures makes maintenance quite a challenging ordeal.

Look into the facter package: https://github.com/puppetlabs/facter

Facter 3.x (part of Puppet 6.x): up to now, AlmaLinux is incorrectly detected as RedHat operating system (fact os.name). I also submitted a patch here which got merged. But so far there hasn't been a new release of Facter 3.x yet. So anybody not building Facter from source has to wait for Facter 3.15.17. Facter 4 (part of Puppet 7.x) seems to work correctly and it wasn't affected by this issue, as it is a complete rewrite with a different resolver logic.

Check the getting started section: https://github.com/puppetlabs/facter#getting-started

So, if you want to see where Gnome Boxes loads the systems from, you can check the database in this repository.

Like already mentioned, Gnome Boxes derives its list of known OS from a library called osinfo. You can check the osinfo data for all catalogued systems, which Gnome Boxes also uses as reference for their recommended downloads.

All I'm missing is great IDE support because most don't support flatpak well, but it's still usable. No idea what you need for data science as I don't do it, but everything else you mentioned works great (except for Windows 11 VMs because the libosinfo merge request that is required hasn't been merged yet (link), so GNOME Boxes doesn't create a VM with UEFI support. Win10 works though)

libosinfo (used by libvirt/KVM for example): a fix has been added by Andrew Lukoshko, see https://gitlab.com/libosinfo/osinfo-db/-/merge_requests/285 which basically boils down the the file /usr/share/osinfo/os/almalinux.org/almalinux-8.xml provided by the RPM osinfo-db (of AlmaLinux 8.3). If this meta information is missing in your KVM hypervisor (for example if you install an AlamLinux VM on a CentOS hypervisor just now) and you did not specify --os-variant rhel8.3 for example when using virt-install when installing an AlmaLinux VM, you might miss certain optimization because only very generic virtualization settings get applied in case of an undetected operating system.