On Fri, Feb 16, 2024 at 06:55:49PM +0100, Sebastian Reitenbach wrote:
> Hi,
>
> On Friday, February 16, 2024 16:52 CET, Klemens Nanni <k...@openbsd.org>
> wrote:
>
> > On Fri, Feb 16, 2024 at 10:23:05AM +0100, Sebastian Reitenbach wrote:
> > > Puppet 6 made room for Puppet8. Initial port for Puppet8 was sent to me
> > > by Alex Talaran.
> > > It took me a while to test and prepare. With Puppet6 gone, and for
> > > Puppet7 all dependencies updated,
> > > I think Puppet8 is good to go. Puppet8 agent works well for me on amd64
> > > against puppetdb/puppetserver v8.
> > >
> > > Attached tarball to be extracted in sysutils/ruby-puppet
> > >
> > > Any feedback, or even OK to import welcome!
> >
> > I only have serverless setups and won't roll out db/server.
> > The agent port looks good and works in light testing, but I'd be easier
> > for me to just pkg_add it on a bunch of machines to test more.
> >
> > Why this when 7 has no @pkgpath markers?
> > @pkgpath sysutils/ruby-puppet/6
> > @pkgpath sysutils/ruby-puppet/7
> >
> > I would expect it to conflict with installed puppet, this leads to
>
> I always get these kind of wrong. Remove these lines, and put
> @conflict puppet-* into PLIST, and same for Puppet7?
@conflict is already there, so does 7 have it.
7/pkg/PLIST had its @pkgpath lines removed recently:
revision 1.5
date: 2023/11/21 21:44:12; author: sebastia; state: Exp; lines: +0
-2;
packaging issues due to pkgpath in PLIST as noted by jca@
> attached version without MESSAGE as you pointed out privately.
MESSAGE got removed but PLIST still @pktpath lines...
OK kn with just those two removed, then both 7 and 8 just use
@option is-branch
@conflict puppet-*
as I'd expect.
