Hi Apollon, Thanks for your response, your explanation and reasoning makes sense. Having augueas-tools linked to puppet would, in retrospect, seem like a more logical place. would you like me to raise a new bug against puppet or is it possible to reassign this one especially as the maintainers seem to be the same
Thanks John On Wed, Jul 17, 2019 at 11:00 PM Apollon Oikonomopoulos <[email protected]> wrote: > Control: reassign -1 puppet > Control: priority -1 wishlist > > Hi John, > > On 13:17 Mon 18 Mar , John Bond wrote: > > Package: facter > > Version: 3.11.0-1.1+b1 > > Severity: normal > > > > Dear Maintainer, > > > > `augparse`, which is provided by `augeas-tools`, is required by `facter` > to > > resolve the `augeasversion` fact[1]. If augparse is not present facter > > returns an empty string and exits cleanly. please consider adding the > > following > > Thanks for the report! While I do understand your frustration, I don't > think it is appropriate to add augeas-tools to facter's Recommends; I > simply don't think it's the right place to solve this issue. Having > facter Recommend: augeas-tools just to get a fact resolved by default is > like Recommend'ing zfs-dkms to get the zfs facts resolved by default. > Facter is there just to tell you what your system looks like and we > shouldn't configure our systems around facter to get every possible fact > supported. > > That said, I admit that most of the times, facter co-exists with puppet > and puppet has already pulled in most of augeas, although not > augeas-tools. I think it's possible to include augeas-tools in puppet's > Recommends instead, which should do what you want, what do you think? > > Regards, > Apollon >
