e repositories makes it do that
> "masking" feature you explain.
New users are advised to run -stable (at faq5.html#Flavors).
Besides, adding -a to your pkg_info -Q'uery shouldn't make a difference
on -current, right? (On default PKG_PATH, yada yada.)
> ideally, the
es it do that "masking"
feature you explain.
Thoughts?
ideally, the -Q switch for pkg_info should search all repositories on -stable,
not just the first, with a fallback to ./, but thats just how I feel it should
be for intuitive's sake.
I appreciate this discussion-
-
Marc,
What was the rational to put "./" as the first search path in the default
PKG_PATH, in particular? And include "./" in there at all, in general?
* * *
Yesterday on Libera Chat we debugged a related problem followed by a
conversation about pkg_add, pkg_info, and de
On Dec 09 16:58:16, glok...@kuzdra.org wrote:
> The FAQ page [FAQ15] suggests to use "pkg_info -Q" to search the
> collection of pre-compiled packages. When I search for "tcl",
> I get a few "nextcloud" packages only, but no Tcl:
>
> $ pkg_i
On 12/9/24 7:58 AM, Maxim wrote:
The FAQ page [FAQ15] suggests to use "pkg_info -Q" to search the
collection of pre-compiled packages. When I search for "tcl",
I get a few "nextcloud" packages only, but no Tcl:
$ pkg_info -v -Q tcl
I've been usi
The FAQ page [FAQ15] suggests to use "pkg_info -Q" to search the
collection of pre-compiled packages. When I search for "tcl",
I get a few "nextcloud" packages only, but no Tcl:
$ pkg_info -v -Q tcl
PKG_PATH=
nextcloud-27.1.11p0
nextcloud
think what packages(7) says is also easier to understand than
> what the quirks package description says.
>
> > not sure what such a manpage would be named.
>
> Given that manual pages are named after programs, functions, devices,
> or file formats,
>
>$ pkg_info
d:
> packages(7) - overview of the binary package system
I think what packages(7) says is also easier to understand than
what the quirks package description says.
> not sure what such a manpage would be named.
Given that manual pages are named after programs, functions, devices,
or fi
On 2023-08-18, l...@ena.re wrote:
> Hey,
>
> according to pkg_info(1) the -m options "shows the names and one-line
> comments for all packages tagged as manually installed". However,
> executing `pkg_info -m` shows the quirks package, which is clearly not
> "manua
Hey,
according to pkg_info(1) the -m options "shows the names and one-line
comments for all packages tagged as manually installed". However,
executing `pkg_info -m` shows the quirks package, which is clearly not
"manually installed". According to it's package descri
> Am 15.04.2023 um 23:44 schrieb Antun Matanović :
>
>> I'm generally interested in what is available for the exact machine I am
>> running on.
>
> You could use `pkg_info -a -Q` which searches all the repositories.
>> From the pkg_info man page:
>
> I'm generally interested in what is available for the exact machine I am
> running on.
You could use `pkg_info -a -Q` which searches all the repositories.
>From the pkg_info man page:
-Q substring
Show the names of all packages in the first rep
> Am 14.04.2023 um 18:24 schrieb Allan Streib :
>
> On Fri, Apr 14, 2023, at 05:50, Stuart Henderson wrote:
>> I never found pkg_info -Q to be a useful tool.
>>
>> Try pkglocate instead ("pkg_add pkglocatedb" first) which allows
>> searching on an ind
On Fri, Apr 14, 2023, at 05:50, Stuart Henderson wrote:
> I never found pkg_info -Q to be a useful tool.
>
> Try pkglocate instead ("pkg_add pkglocatedb" first) which allows
> searching on an index that is built from : - as a
> result it lets you do a substring match o
Inline…
> Am 14.04.2023 um 12:50 schrieb Stuart Henderson :
>
> On 2023-04-14, Mike Fischer wrote:
>> Usually when looking for a port to install I use `pkg_info -Q name` to
>> search for the the port.
>>
>> Strangely this does not completely work for PHP on
On 2023-04-14, Mike Fischer wrote:
> Usually when looking for a port to install I use `pkg_info -Q name` to
> search for the the port.
>
> Strangely this does not completely work for PHP on OpenBSD 7.3:
>
> `pkg_info -Q php` does not list PHP 7.4.33 and related ports wh
Usually when looking for a port to install I use `pkg_info -Q name` to search
for the the port.
Strangely this does not completely work for PHP on OpenBSD 7.3:
`pkg_info -Q php` does not list PHP 7.4.33 and related ports which are clearly
available.
It seems that -Q only finds ports in
On Mon, 2023-01-30 at 11:26 +, Stuart Henderson wrote:
> On 2023-01-30, David Demelier wrote:
> > While searching for sqlite3 I've realized that pkg_info -Q sqlite3
> > finds some php packages but not everything available in the remote
> > repository:
>
> Thi
On 2023-01-30, David Demelier wrote:
> While searching for sqlite3 I've realized that pkg_info -Q sqlite3
> finds some php packages but not everything available in the remote
> repository:
This is a consequence of the "first repository of the package search
path" limitati
Hi,
* David Demelier wrote:
> Hello,
>
> While searching for sqlite3 I've realized that pkg_info -Q sqlite3
> finds some php packages but not everything available in the remote
> repository:
>
> # cat /etc/installurl
&g
Hello,
While searching for sqlite3 I've realized that pkg_info -Q sqlite3
finds some php packages but not everything available in the remote
repository:
# cat /etc/installurl
https://ftp.fr.openbsd.org/pub/OpenBSD/
# pkg_info -Q sqlite3
debu
>> 6.2 era. The machine has been upgraded over the years all the way to 6.9.
>> I'm not sure that it's relevant, but I've regularly run sysclean in an
>> effort to keep my install clean and fresh.
>>
>> When running "pkg_info -m", within the output l
6.9. I'm not
> sure that it's relevant, but I've regularly run sysclean in an effort to keep
> my install clean and fresh.
>
> When running "pkg_info -m", within the output list I am shown a number of
> random dependencies which I did not manually install. I
gularly run sysclean in an effort to keep my
install clean and fresh.
When running "pkg_info -m", within the output list I am shown a number of
random dependencies which I did not manually install. Is there a way to remove
the "manually installed" tag from these libra
On Sun, Jan 24, 2021 at 09:35:46PM +0100, Andrew Easton wrote:
> Hello everyone,
>
> it appears that there may be a way to misinterpret
> the man page for pkg_info(1) in the state of
> commit 0b249e2164be2385bc6a5e82814435649b2b06e0
> Date: Sun Jan 24 10:21:43 2021 +00
Hello everyone,
it appears that there may be a way to misinterpret
the man page for pkg_info(1) in the state of
commit 0b249e2164be2385bc6a5e82814435649b2b06e0
Date: Sun Jan 24 10:21:43 2021 +
on the github openbsd src mirror.
The problem description is under the headline
"Issue&quo
qlports
> $ sqlite3 /usr/local/share/sqlports
> https://cvsweb.openbsd.org/ports/
> > and read the man page pkg_info(1).
For what it may be worth, another way to get a list of ports is
(as root, or maybe should be rewritten with "doas", as Ingo
did, but):
# cd /usr/port
/local/share/ports-INDEX
$ doas pkg_add sqlports
$ sqlite3 /usr/local/share/sqlports
https://cvsweb.openbsd.org/ports/
> and read the man page pkg_info(1).
>
> That man page it states,
> "When browsing through uninstalled packages, running pkg_info -I *.tgz
> wil
Hello,
I am running OpenBSD in a virtualbox because I am taking a deeper look
into it.
I was looking for a list of ports packages and read the man page
pkg_info(1).
That man page it states,
"When browsing through uninstalled packages, running pkg_info -I *.tgz
will report a summary lin
Thanks Stuart,
I tried that package and it indeed does what i needed :)
But I decided to scratch my itch anyway and dug a bit into the
pkg_info code to figure out
what was going on and I found the culprit: is the match_locations function
in the PackageRepositoryList class that all the matches
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-c
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 t
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
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.
Cheers
odule "mysqlclient", I get the
following puzzling results:
$ pkg_info -Q mysql
php-mysqli-7.2.24
php-mysqli-7.3.11
php-pdo_mysql-7.2.24
php-pdo_mysql-7.3.11
$ pkg_info -Q py-mysql
py-mysql-1.2.5p6
py-mysqlclient-1.4.2p0
Am I doing something wrong? Why is "py-mysqlclient" not ma
ient", I get the
> following puzzling results:
>
> $ pkg_info -Q mysql
> php-mysqli-7.2.24
> php-mysqli-7.3.11
> php-pdo_mysql-7.2.24
> php-pdo_mysql-7.3.11
>
> $ pkg_info -Q py-mysql
> py-mysql-1.2.5p6
> py-mysqlclient-1.4.2p0
>
> Am I doing something wrong?
Hi misc,
I see pkg_info's man page says:
-Q query
Show all packages in $PKG_PATH which match the given query.
Trying in 6.6 to find the Python module "mysqlclient", I get the
following puzzling results:
$ pkg_info -Q mysql
php-mysqli-7.2.24
php-mysqli-7.3.11
php-p
Hello,
Is there a way to do multiple queries at once using pkg_info?
Something like:
pkg_info -Q query1 query2 ...
The best I've found so far is to do something like:
for q in query1 query2 ...; do pkg_info -Q $q; done
which is slow when the list of queries is long (my network bandwid
Hi Evan,
Evan Silberman wrote on Wed, May 01, 2019 at 04:24:51PM -0700:
> pkg_info -R PACKAGE lists the packages that depend on PACKAGE. Is there a
> particular reason there's not an analogous option that lists a package's own
> dependencies? (i.e., listing the contents of
pkg_info -R PACKAGE lists the packages that depend on PACKAGE. Is there a
particular reason there's not an analogous option that lists a package's own
dependencies? (i.e., listing the contents of +REQUIRING from the package
db, rather than +REQUIRED_BY)
(Granted, in asking this questi
id, and a
few months ago I did have a problem where a trailing slash caused
problems with syspatch, which, without any pressure from me, I was
informed would be fixed. The issue may simply be one of
consistency, but looks more likely to be an error in the pkg_info
script.
>
roblems with
> syspatch, which, without any pressure from me, I was informed would be
> fixed. The issue may simply be one of consistency, but looks more likely to
> be an error in the pkg_info script.
> >
> > So, to sum up:
> >
> > Pkg_add works;
> > Syspatc
;months ago I did have a problem where a trailing slash caused problems
>with syspatch, which, without any pressure from me, I was informed
>would be fixed. The issue may simply be one of consistency, but looks
>more likely to be an error in the pkg_info script.
>>
>> So, to su
would be fixed.
> The issue may simply be one of consistency, but looks more likely to be an
> error in the pkg_info script.
>
> So, to sum up:
>
> Pkg_add works;
> Syspatch works;
> Cloudflare was up last time I tried it;
> Despite the above, pkg_info -Q does *not* w
an error in the
pkg_info script.
So, to sum up:
Pkg_add works;
Syspatch works;
Cloudflare was up last time I tried it;
Despite the above, pkg_info -Q does *not* work.
Jeff
Sent from Blue
On 15 Apr 2018, 03:26, at 03:26, Edgar Pettijohn
wrote:
>
>
>On 04/14/18 19:34, Jeffrey Josh
nBSD 6.3-release for amd64 on
virtualbox, and updated it with syspatch as of 20:40 UTC.
pkg_info -Q seems to be failing. Specifically, I tried $
pkg_info -Q mate ...and also as root, to remind myself what
the metapackage is [I have a feeling it's just &qu
Hi,
I've installed OpenBSD 6.3-release for amd64 on virtualbox, and updated it
with syspatch as of 20:40 UTC. pkg_info -Q seems to be failing.
Specifically, I tried
$ pkg_info -Q mate
...and also as root, to remind myself what the metapackage is [I have a
feeling it's just "mate
Hi Lari/Marc/all,
On Thu, 2 Nov 2017 00:21:08 +0200 Lari Rasku wrote:
> Oh, it's a ports tree mechanism? I only use packages, so I've been
> using it for a fast reinstall/lookup cache in case I come to second
> thoughts about some package:
Likewise, I have:
$ printenv | fgrep PKG_
PKG_CACHE=/v
Marc Espie kirjoitti 11/01/17 klo 20:11:
On Wed, Nov 01, 2017 at 11:51:52AM +0100, Marc Espie wrote:
>> Somewhat low priority.
>
> Fairly easy to fix actually, so it's going to be in current, thx
Sweet.
Well, people usually don't define PKG_CACHE manually, but rely
on the ports tree to do it
gt; >
> > To a directory the current user lacks write access to:
> >
> > $ touch /var/cache/pkg/somefile
> > touch: /var/cache/pkg/somefile: Permission denied
> >
> > Trying to call pkg_info on an uninstalled package fails:
> >
> >
touch /var/cache/pkg/somefile
> touch: /var/cache/pkg/somefile: Permission denied
>
> Trying to call pkg_info on an uninstalled package fails:
>
> $ pkg_info -e lumina-1.3.0pl1p2; echo $?
> 1
> $ pkg_info lumina-1.3.0pl1p2
> Fatal error: bad PKG_CACHE d
Oct 27 snapshot, amd64.
When PKG_CACHE is set:
$ cat /etc/profile
export PKG_CACHE=/var/cache/pkg
To a directory the current user lacks write access to:
$ touch /var/cache/pkg/somefile
touch: /var/cache/pkg/somefile: Permission denied
Trying to call pkg_info
On Tue, Jun 28, 2016 at 08:29:23PM -0500, Edgar Pettijohn wrote:
> On 16-06-29 03:16:02, Theo Buehler wrote:
> > On Tue, Jun 28, 2016 at 08:09:02PM -0500, Edgar Pettijohn wrote:
> > > This doesn't seem possible, but maybe I'm missing something.
> > >
> &g
On 16-06-29 03:16:02, Theo Buehler wrote:
> On Tue, Jun 28, 2016 at 08:09:02PM -0500, Edgar Pettijohn wrote:
> > This doesn't seem possible, but maybe I'm missing something.
> >
> > I would like pkg_info to tell me where to find a package in
> > the ports tr
On Tue, Jun 28, 2016 at 08:09:02PM -0500, Edgar Pettijohn wrote:
> This doesn't seem possible, but maybe I'm missing something.
>
> I would like pkg_info to tell me where to find a package in
> the ports tree. For example:
>
> If I go to /usr/ports and do make searc
Edgar Pettijohn wrote:
> I would like pkg_info to tell me where to find a package in
> the ports tree. For example:
>
> If I go to /usr/ports and do make search key=wget I can find
> the following.
>
> Port: wget-1.16.3p0
> Path: net/wget
> Info: retrieve
This doesn't seem possible, but maybe I'm missing something.
I would like pkg_info to tell me where to find a package in
the ports tree. For example:
If I go to /usr/ports and do make search key=wget I can find
the following.
Port: wget-1.16.3p0
Path: net/wget
Info: retrieve
On Mon, Feb 14, 2011 at 01:13:34PM +0100, Jan Stary wrote:
> Is this the intended behaviour?
Yeah. it's meant to find where a file you know lives.
You want pkglocatedb.
This is
OpenBSD 4.8-current (GENERIC.MP) #0: Wed Nov 24 15:23:13 CET 2010
r...@stary.fjfi.cvut.cz:/usr/src/sys/arch/i386/compile/GENERIC.MP
When looking for a package that contains a given file,
I am using the -E feature of pkg_info:
$ pkg_info -E /usr/local/lib/libschroedinger-1.0.so.2.0
On Fri, Jan 22, 2010 at 06:42:45AM +0100, Song Li wrote:
> Thank you Bret. I can see that now after Aaron's comments and yours.
>
> cheers,
This is actually documented. You can tell by telling me where you looked,
and where I should put the info to be sure newbies see it.
>From packages(7), thir
stupid to you.
>>
>> I am using the current release 4.6 installed from the file
>> install46.iso on ftp://openbsd.ftp.fu-berlin.de/pub/OpenBSD/4.6/i386/
>>
>> Have anyone encountered any problem using pkg_info, pkg_add, etc.?
>> They do not seem working to me.
&
/
>
> Have anyone encountered any problem using pkg_info, pkg_add, etc.?
> They do not seem working to me.
>
> Take a simplest example, when I checked pkg_info, the man page says:
> ...
> -A Show information for all currently installed packages,
> including internal p
Hi:
I am really a newbie on OpenBSD. So my question might look stupid to you.
I am using the current release 4.6 installed from the file
install46.iso on ftp://openbsd.ftp.fu-berlin.de/pub/OpenBSD/4.6/i386/
Have anyone encountered any problem using pkg_info, pkg_add, etc.?
They do not seem
On 2008/10/5, Philip Guenther <[EMAIL PROTECTED]> wrote:
> [In the context of pkg_info only downloading the first part of a
> package to get the info]
>
> On Sat, Oct 4, 2008 at 5:09 AM, Slim Joe <[EMAIL PROTECTED]> wrote:
>>
>> Also I think it would be nice if
[In the context of pkg_info only downloading the first part of a
package to get the info]
On Sat, Oct 4, 2008 at 5:09 AM, Slim Joe <[EMAIL PROTECTED]> wrote:
...
> Also I think it would be nice if the packages are dumped not into
> the present directory but in the $PKG_CACHE tha
On 2008/10/4, Marc Espie <[EMAIL PROTECTED]> wrote:
> pkg_info will only download the beginning of the package, since it only
> needs the packing information, and we're very careful to store it at
> the beginning.
>
> Now, a lot of FTP servers tend to not like abort
fo for a file not already downloaded or installed without
> >> such heavy bandwidth (just the package info).
> >
> > Look at the -Q option on the pkg_info(1) manpage.
> >
>
> I think he's asking for how to read package descriptions without
> downloading everyth
On Thu, Oct 2, 2008 at 3:20 AM, Slim Joe <[EMAIL PROTECTED]> wrote:
> On 2008/10/1, Stuart Henderson <[EMAIL PROTECTED]> wrote:
>> On 2008-10-01, Nick Guenther <[EMAIL PROTECTED]> wrote:
>>> If you are looking for package descriptions, install the ports tree
>>> and read the Makefiles.
>
> A lynx d
On 2008/10/1, Stuart Henderson <[EMAIL PROTECTED]> wrote:
> On 2008-10-01, Nick Guenther <[EMAIL PROTECTED]> wrote:
>> If you are looking for package descriptions, install the ports tree
>> and read the Makefiles.
A lynx dump of http://www.openbsd.org/4.3_packages/i386.html
seems more handy.
> Fo
On 2008-10-01, Nick Guenther <[EMAIL PROTECTED]> wrote:
> If you are looking for package descriptions, install the ports tree
> and read the Makefiles.
For 4.4/-current, landry@ has written a curses-based package browser,
pkg_mgr. It's in the ports tree and of course a package is available,
"pkg_a
On Tue, Sep 30, 2008 at 10:47:56PM -0400, Nick Guenther wrote:
> If you are looking for package descriptions, install the ports tree
> and read the Makefiles. Also, if you are lazy/not on an OpenBSD box,
> most of the descriptions are available at
> http://www.openbsd.org/4.3_packages/.
or even
h
bandwidth (just the package info).
>
> Look at the -Q option on the pkg_info(1) manpage.
>
I think he's asking for how to read package descriptions without
downloading everything. But pkg_info has to download the entirety of
each package first because a package is a compressed archive fil
On Tue, Sep 30, 2008 at 11:16 AM, Slim Joe <[EMAIL PROTECTED]> wrote:
> Is there a way to get package
> info for a file not already downloaded or installed without
> such heavy bandwidth (just the package info).
Look at the -Q option on the pkg_info(1) manpage.
On Tue, Sep 30, 2008 at 11:16 AM, Slim Joe <[EMAIL PROTECTED]> wrote:
> When I invoke something like "pkg_info vim*",
> pkg_info insists on downloading all the packages named
> "vim*". That is, I see a bunch of "vim*" packages on
> "." (pr
When I invoke something like "pkg_info vim*",
pkg_info insists on downloading all the packages named
"vim*". That is, I see a bunch of "vim*" packages on
"." (present directory). Is there a way to get package
info for a file not already downloaded or inst
75 matches
Mail list logo
