In message <CAN6yY1uuc4NbTMc5B1uvux86mR7cwZ37rLFn54z6bK4sn-0MFQ@mail.gmail.c om> , Kevin Oberman writes: > --000000000000a8e5f306343fe6e8 > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > On Sat, May 3, 2025 at 9:36=E2=80=AFAM void <v...@f-m.fm> wrote: > > > On Fri, May 02, 2025 at 07:32:34AM +0100, Graham Perrin wrote: > > >root@mowa219-gjp4-zbook-freebsd:~ # pkg version -C -vRL=3D | grep -v > > orphaned > > >pkg: invalid option -- C > > >pkg: invalid option -- v > > >pkg: invalid option -- R > > >pkg: invalid option -- L > > >pkg: invalid option -- =3D > > > > how odd. > > > > I'd try re-making pkg from an updated ports tree. > > My context builds everything from source. It doesn't use pkg base. > > > > % pkg version -C -vRL=3D | grep -v orphaned > > % > > > > % pkg which /usr/local/sbin/pkg > > /usr/local/sbin/pkg was installed by package pkg-2.1.2 > > > > % pkg --version > > 2.1.2 > > > > 15.0-CURRENT FreeBSD 15.0-CURRENT #0 n276073-67c1c4dfd1cc: Wed Mar 26 > > 16:26:10 GMT 2025 > > r...@redacted.home.arpa:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG > > amd64 1500034 1500034 > > > I see the same thing, but only after updating the system (not ports) to > main-n276966-46adaf3642cf: Fri May 2 21:35:20 PDT. rebuilding the port > made no difference. It looks like the issue is in the base system, not > port, or the interaction between /usr/sbin/ports.
Likely be61deae0aa2. > > As a workaround, I will also mention that the error messages do not appear > if I directly run /usr/local/sbin/pkg. By aliasing pkg to > /usr/local/sbin/pkg, the issue disappears. > --=20 > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkober...@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 -- Cheers, Cy Schubert <cy.schub...@cschubert.com> FreeBSD UNIX: <c...@freebsd.org> Web: https://FreeBSD.org NTP: <c...@nwtime.org> Web: https://nwtime.org e^(i*pi)+1=0
