Date: Fri, 03 Dec 2021 13:36:55 UTC
On 2021-12-03 5:25, Baptiste Daroussin wrote: > On Fri, Dec 03, 2021 at 05:11:06AM -0800, Mel Pilgrim wrote: >> On 2021-12-03 2:56, Baptiste Daroussin wrote: >>> On Fri, Dec 03, 2021 at 02:28:58AM -0800, Mel Pilgrim wrote: >>>> With pkg-1.17.5: >>>> >>>> # pkg alias >>>> ALIAS ARGUMENTS >>>> # pkg leaf >>>> pkg: unknown command: leaf >>>> >>>> For more information on available commands and options see 'pkg help'. >>>> >>> >>> I don't know what happened in your case, but I cannot reproduce. >> >> Do you have any diagnostic steps I can do to figure out what happened? >> >> I fetched a fresh copy of pkg-1.17.5~d6f9535722.pkg from the public repo and >> installed it using pkg-static, but that didn't fix the problem. >> >> I can at least confirm this only happens on one particular system. I have >> 15 systems all using the same private pkg repo, and only one has this >> problem. > > it means on the system with this issue, someone touched /usr/local/etc/pkg.conf > > The aliases are set there, the original file is stored at the following place: > /usr/local/etc/pkg.conf.sample Ya I found that about 10 seconds after sending my last email. But it raises another question: The non-default pkg.conf had been on the system since August 2021, but alias commands like pkg leaf worked on 1.17.4. Why does 1.17.5 require pkg.conf define the aliases?