Hi Klemens,
On Sat, Feb 21, 2026 at 11:33 PM Klemens Nanni <[email protected]> wrote: > 19.02.2026 23:49, Sebastian Reitenbach пишет: > > Hi, > > > > with a fresh head, I looked at it again. The culprit was the PuppetDB > port because it involves multiple packages. I had to add the ,-SUBPACKAGE > to the @pkgpath in the respective PLIST files. > > > > Now, a "make update" in openvoxdb, or puppetserver works for me, > resolving all interdependencies between those packages properly. > > I keep forgetting the details, but I don't think 'make update' is enough > to catch everything that 'pkg_add -u' would do. > > At least that's how I learned and remmber how to test > pkgpath/conflicts/quirks, > hence my suggestion to build all the packages and then do a regular update > via TRUSTED_PKG_PATH pointing at them. > > > > > Updated removal patch attached. > > Reads OK to me. > > openfact has no conflict with facter since their gem files are unique > and they ship bin/facter and bin/ruby34-facter, respectively. > > But isn't '@conflict ruby34-facter-*' now as you merge its pkgpath? > I can have both installed in parallel, and update works alike: /home/ports/sysutils/ruby-openfact> make update ===> Updating for openfact-5.4.0p0 Upgrading from ruby34-facter-4.10.0p2 openfact-5.4.0p0: ok /home/ports/sysutils/ruby-openfact> sudo pkg_add -i ruby34-facter /home/ports/sysutils/ruby-openfact> pkg_info | grep fact openfact-5.4.0p0 system inventory tool ruby34-facter-4.10.0p2 system inventory tool I should probably add the: '@conflict ruby34-facter-*'. If someone makes make install or pkg_add openvox, then it would not purge facter. > > > > > > Once it's in, would also add some blurb to current.html, also mentioning > the removal of Ruby Flavor from several Puppet-related Ruby-based ports. > > Why not. > thank you, I'll go ahead with it some time Tomorrow then. Sebastian
