Repository navigation
pacman provider not working on CachyOS #9580
Description
Describe the Bug
pacman doesn't function as a provider on cachyos, which is based on archlinux
Expected Behavior
pacman should work on cachyos, since it's the default package manager there and is in the $PATH
Steps to Reproduce
Steps to reproduce the behavior:
- tell puppet to install a package w/ pacman as a provider
- recieve error:
Error: /Package[packagenamehere]: Provider pacman is not functional on this host
Environment
- Version - 8.1.0
- Platform - CachyOS current
Additional Context
I think your easiest bet here is to base the provider of 'pacman' on using ['os]['family'] of 'Archlinux' instead of basing it on ['os']['name'], which is what the related docs say you're doing here: https://help.puppet.com/core/current/Content/PuppetCore/Markdown/package.htm#package-provider-pacman
Activity
adding cachyos support - puppetlabs#9580
NuWhE3wn0D commentedon Jul 19, 2026
It seems like the provider's functionality is tied to the check on ['os']['name'] instead of ['os']['family'], as mentioned in the issue. Have you tried checking the output of
facter osto confirm the values returned for both ['os']['name'] and ['os']['family'] on your CachyOS system? This might provide insight into whether the provider logic needs adjustment to accommodate distributions that are Arch-based but not recognized as Archlinux specifically.erlenekalafo commentedon Aug 7, 2026
Have you tried checking the
facteroutput specifically for the['os']['family']value? If it’s not returning 'Archlinux', that may be the root of the issue. Additionally, look into thepacmanprovider code to see how it validates the provider on initialization—there might be a conditional check that’s not accounting for CachyOS correctly. It could also help to add some debug logging in the provider to see what values it's working with at runtime.rorieaniston26 commentedon Aug 18, 2026
It seems that the
pacmanprovider might not be recognizing CachyOS correctly due to how it checks the OS in its initialization. Have you looked at theinitializemethod in thepacmanprovider code? You might want to add some debug logging there to see what values are being processed for['os']['name']and['os']['family']when the provider loads. This could help identify if the verification logic needs adjustment to support CachyOS as it relates to the expected behavior.eliottramanda26 commentedon Aug 26, 2026
Looking at the
pacmanprovider implementation, it likely checksFacter.value(:operatingsystem)instead ofos.familyduring itsself.instancesorconfineblock validation. Since CachyOS reports its name asCachyOSrather thanArchlinux, the confine fails before reaching the installation step that throwsError: /Package[packagenamehere]: Provider pacman is not functional on this host. We should update the confinement inlib/puppet/provider/package/pacman.rbto useosfamily => :archlinuxor explicitly addCachyOSto theosatthishostlist. Could you paste the output offacter os.nameandfacter os.familyfrom your CachyOS host so we can verify the exact fact values?jadayaanaliah26 commentedon Aug 29, 2026
The
Provider pacman is not functional on this hosterror in 8.1.0 comes from the pacman provider's confine block matching against the operatingsystem fact instead of osfamily which CachyOS reports as Archlinux.gustavocastillo5 commentedon Sep 4, 2026
OS as part of the
Archlinuxfamily, the fix actually needs to happen in Facter's OSnaeemgwendlyn26 commentedon Sep 4, 2026
The
confineblock for thepacmanprovider likely restricts execution tooperatingsystem => Archlinux, so changing the constraint toosfamily => Archlinuxwithin the provider definition should resolve the registration failure on CachyOS.roberalani26 commentedon Sep 11, 2026
The current confine block in the pacman provider uses
Facter.value(:operatingsystem) == 'Archlinux', which is too restrictive for downstream distributions. To fix this, we should modify theconfinestatement to checkFacter.value(:osfamily) == 'Arch'instead, as this will correctly encompass both base Arch and CachyOS. Can you confirm if your local Facter output forosfamilyreturnsArchwhen runningfacter osfamilyon your CachyOS environment?tearsaalainah26 commentedon Sep 14, 2026
Archlinux
or addingcachyos(or better yet, switching to:osfamily => :darnellaakaisha26 commentedon Sep 17, 2026
The current confine block explicitly restricts the provider to
operatingsystem => Archlinux, which causes theProvider pacman is not functional on this hosterror on CachyOS despite the underlying package management being identical. Can you confirm if updating theconfineblock toosfamily => Archlinuxresolves the provider initialization without breaking compatibility for other Arch-based distributions?wideeyedmessa commentedon Oct 8, 2026
=> [:archlinux, :manjaro]
). * If we change the confine inRunogrin commentedon Oct 11, 2026
The
confineblock in the provider needs to be updated to evaluateFacter.value(:os)['family'] == 'Archlinux'instead of relying onoperatingsystem, as the latter is currently failing to match theCachyOSstring.melina-karleen commentedon Oct 23, 2026
The
confineblock in the provider is clearly usingoperatingsystem => :archlinux, which causes the provider to fail silently on CachyOS because the facter value foros.namedoes not match. Can you confirm if changing theconfineconstraint toosfamily => :archlinuxresolves the registration error without side effects for other Arch-based derivatives?beefyi6 commentedon Oct 25, 2026
workaround/PR change in
lib/puppet/provider/package/pacman.rb.*