On 2019-11-19, Marc Espie <es...@nerim.net> wrote: > On Tue, Nov 19, 2019 at 12:13:37PM +0200, Dumitru Moldovan wrote: >> On Mon, Nov 18, 2019 at 11:15:05AM +0100, Antonio Bibiano wrote: >> > Hello, >> > I just wanted to add to this thread that I incurred in the same >> > issue on a fresh 6.6 installation. >> > I also tried with a different mirror in /etc/installurl and receive >> > the same partial response from pkg_info -Q. >> > What makes it even more odd is that pkg_add finds the correct package. >> >> Thanks Antonio for double-checking this! I have also tested it on a >> fresh installation at the time and got the same results. >> >> Maybe the behaviour is undefined if PKG_PATH is not set, which is fine >> by me. But still, it's quite puzzling and against the principle of >> least surprise. > > It's one of those little things that is well known, but that won't change > until I have time to look at it, and it's definitely not a high priority > problem right now. > >
As a workaround (but also something that would be more likely to give the results wanted than a properly-working pkg_info -Q which doesn't match filenames inside the packages), you might like to "pkg_add pkglocatedb" and use the "pkglocate" tool that this provides.