Re: ChiPass

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Mon, 9 Nov 2026 06:10:26 +0100
    From:        Matti Andreas =?utf-8?B?S8OkaMOkcmk=?= <andreas.kahari%abc.se@localhost>
    Message-ID:  <avFVwllKWa-2gWy4@eeyore.invalid>

  | On Sun, Nov 08, 2026 at 07:58:54PM -0800, Jeff wrote:

  | > I ran 'cd /usr/pkgsrc && cvs update -dP' and it did update a bunch of
  | > stuff, but did not add ChiPass. Any advice on how I should proceed?

  | If you have checked out a stable branch of pkgsrc, such as pkgsrc-2026Q3,
  | you will not find it there.  It's only currently available on the trunk.

Which means that "cvs update -AdP" should add it - along with updating
everything else in pkgsrc from its current state to that of pkgsrc HEAD.

That is not recommended if you've been using binary packages, as there
will be lots of incompatibilities, and lots of packages that need to be
rebuilt from source.

What you could do, if you want to experiment, is copy (all of)
	/usr/pkgsrc/security
to some-other-place/security, cd some-other-place/security && cvs update -dAP
(the order of the flags is irrelevant), and then try just copying the
ChiPass directory which should appear there back to /usr/pkgsrc/security

That, of itself, should cause no problems.   Whether or not ChiPass will
build in that environment, I have no idea, it might need some changes to
its Makefile (and perhaps more), whether or not it would work, even less
certain, but it is a far safer and less problematic option that attempting
to update all of /usr/pkgsrc to HEAD, and then trying to mix packages built
that way with binaries from one of the stable branches.   You could of course
delete all of /usr/pkg/* and start again, building everything from source.
Depending how much "everything" is, and the capacity of the build host,
that might take something between weeks and months to finish.

Alternatively, you could wait until the next stable branch appears, and
upgrade everything to that.  Then ChiPass should (probably) be included.

kre