Re: PKG_PATH never works as stated
On Sun, Oct 25, 2009 at 10:29 PM, Juan Miscaro jmisc...@gmail.com wrote: I've had this problem for a long time (over many OpenBSD releases). The pkg_add man page (for 4.5) states: If a given package name cannot be found, the directories named by PKG_PATH are searched. It should contain a series of entries separated by colons. Each entry consists of a directory name. URL schemes such as FTP, HTTP, HTTPS, or SCP are also appropriate. On a client machine: PKG_PATH=http://$HTTP_MASTER/:http://$HTTP_MASTER/by_port/i386/all/ My master server serves up normal packages and those packages compiled from ports. When I do this only the first component is searched. I have to do a second package update run with PKG_PATH pointing directly to the second component for the ports packages to be seen. Why is this? I've seen this too but I've never figured it out. Obviously it's supposed to work so we must be doing it wrong... or maybe we have odd characters in our URLs that are throwing off the parser (after all, http:// contains the delimiter field, it's not unlikely it might screw up). Can you echo your $HTTP_MASTER, and your $PKG_PATH? And show an attempt to use pkg_add that fails? -Nick
Re: PKG_PATH never works as stated
hmm, on Mon, Oct 26, 2009 at 02:56:49AM +, Jacob Meuser said that If a given package name cannot be found, the directories named by ^^^ PKG_PATH are searched. It should contain a series of entries separated by colons. Each entry consists of a directory name. URL schemes such as FTP, HTTP, HTTPS, or SCP are also appropriate. later man pages go like this: If the given package names are not found in the current working directo- ry, pkg_add will search for them in each directory named by the PKG_PATH environment variable. Specifying `-' as a package name causes pkg_add to read from the standard input. i think this is inaccurate... the current working directory is never searched unless the package name starts with './' or PKG_PATH contains '.': not working: $ echo $PKG_PATH $ ls autossh-1.3.tgz $ sudo pkg_add autossh-1.3.tgz Can't find autossh-1.3.tgz Can't call method grabPlist on an undefined value at /usr/libdata/perl5/OpenBSD/Handle.pm line 154. working: $ PKG_PATH=. $ sudo pkg_add autossh-1.3.tgz autossh-1.3: complete or $ PKG_PATH= $ sudo pkg_add ./autossh-1.3.tgz autossh-1.3: complete -f -- i'm not religious. god willing, i never will be.
Re: PKG_PATH never works as stated
On Mon, Oct 26, 2009 at 08:41:44PM +0100, frantisek holop wrote: hmm, on Mon, Oct 26, 2009 at 02:56:49AM +, Jacob Meuser said that If a given package name cannot be found, the directories named by ^^^ PKG_PATH are searched. It should contain a series of entries separated by colons. Each entry consists of a directory name. URL schemes such as FTP, HTTP, HTTPS, or SCP are also appropriate. later man pages go like this: If the given package names are not found in the current working directo- ry, pkg_add will search for them in each directory named by the PKG_PATH environment variable. Specifying `-' as a package name causes pkg_add to read from the standard input. i think this is inaccurate... the current working directory is never searched unless the package name starts with './' or PKG_PATH contains '.': not working: $ echo $PKG_PATH $ ls autossh-1.3.tgz $ sudo pkg_add autossh-1.3.tgz Can't find autossh-1.3.tgz Can't call method grabPlist on an undefined value at /usr/libdata/perl5/OpenBSD/Handle.pm line 154. works for me with Oct 22 snap on i386. that file (Handle.pm) is relatively new. what version do you have? -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: PKG_PATH never works as stated
hmm, on Tue, Oct 27, 2009 at 01:05:26AM +, Jacob Meuser said that On Mon, Oct 26, 2009 at 08:41:44PM +0100, frantisek holop wrote: hmm, on Mon, Oct 26, 2009 at 02:56:49AM +, Jacob Meuser said that If a given package name cannot be found, the directories named by ^^^ PKG_PATH are searched. It should contain a series of entries separated by colons. Each entry consists of a directory name. URL schemes such as FTP, HTTP, HTTPS, or SCP are also appropriate. later man pages go like this: If the given package names are not found in the current working directo- ry, pkg_add will search for them in each directory named by the PKG_PATH environment variable. Specifying `-' as a package name causes pkg_add to read from the standard input. i think this is inaccurate... the current working directory is never searched unless the package name starts with './' or PKG_PATH contains '.': not working: $ echo $PKG_PATH $ ls autossh-1.3.tgz $ sudo pkg_add autossh-1.3.tgz Can't find autossh-1.3.tgz Can't call method grabPlist on an undefined value at /usr/libdata/perl5/OpenBSD/Handle.pm line 154. works for me with Oct 22 snap on i386. that file (Handle.pm) is relatively new. what version do you have? # $OpenBSD: Handle.pm,v 1.6 2009/10/19 14:00:10 espie Exp $ afaik the latest. i am on Oct 20 snapshot. -f -- i'm neither for, nor against apathy.
Re: PKG_PATH never works as stated
2009/10/25 Jacob Meuser jake...@sdf.lonestar.org: On Sun, Oct 25, 2009 at 10:29:29PM -0400, Juan Miscaro wrote: I've had this problem for a long time (over many OpenBSD releases). The pkg_add man page (for 4.5) states: If a given package name cannot be found, the directories named by B ^^^ PKG_PATH are searched. B It should contain a series of entries separated by colons. B Each entry consists of a directory name. B URL schemes such as FTP, HTTP, HTTPS, or SCP are also appropriate. On a client machine: PKG_PATH=http://$HTTP_MASTER/:http://$HTTP_MASTER/by_port/i386/all/ My master server serves up normal packages and those packages compiled from ports. When I do this only the first component is searched. B I have to do a second package update run with PKG_PATH pointing directly to the B B B B ^^ second component for the ports packages to be seen. Why is this? did you give pkg_add a package name? No, as I stated I am updating my packages. Are you saying that PKG_PATH takes on a different meaning in this context? That certainly seems to be the case. Too bad. -- /jm
Re: PKG_PATH never works as stated
On Mon, Oct 26, 2009 at 10:00:20PM -0400, Juan Miscaro wrote: 2009/10/25 Jacob Meuser jake...@sdf.lonestar.org: On Sun, Oct 25, 2009 at 10:29:29PM -0400, Juan Miscaro wrote: I've had this problem for a long time (over many OpenBSD releases). The pkg_add man page (for 4.5) states: If a given package name cannot be found, the directories named by B ^^^ PKG_PATH are searched. B It should contain a series of entries separated by colons. B Each entry consists of a directory name. B URL schemes such as FTP, HTTP, HTTPS, or SCP are also appropriate. On a client machine: PKG_PATH=http://$HTTP_MASTER/:http://$HTTP_MASTER/by_port/i386/all/ My master server serves up normal packages and those packages compiled from ports. When I do this only the first component is searched. B I have to do a second package update run with PKG_PATH pointing directly to the B B B B ^^ second component for the ports packages to be seen. Why is this? did you give pkg_add a package name? No, as I stated I am updating my packages. Are you saying that PKG_PATH takes on a different meaning in this context? That certainly seems to be the case. Too bad. well, think about it. if pkg_add were scanning all paths for the latest of each package ... that could easily be a very large and complicated task. certainly much more complex than finding a first match. suggestions for you: a) use one path for all packages or b) instead of pkg_add -u, use pkg_add -r list of exact names of packages to be updated, perhaps from running the ports out-of-date script, or following ports-changes, or however -- /jm -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
PKG_PATH never works as stated
I've had this problem for a long time (over many OpenBSD releases). The pkg_add man page (for 4.5) states: If a given package name cannot be found, the directories named by PKG_PATH are searched. It should contain a series of entries separated by colons. Each entry consists of a directory name. URL schemes such as FTP, HTTP, HTTPS, or SCP are also appropriate. On a client machine: PKG_PATH=http://$HTTP_MASTER/:http://$HTTP_MASTER/by_port/i386/all/ My master server serves up normal packages and those packages compiled from ports. When I do this only the first component is searched. I have to do a second package update run with PKG_PATH pointing directly to the second component for the ports packages to be seen. Why is this? -- /jm
Re: PKG_PATH never works as stated
On Sun, Oct 25, 2009 at 10:29:29PM -0400, Juan Miscaro wrote: I've had this problem for a long time (over many OpenBSD releases). The pkg_add man page (for 4.5) states: If a given package name cannot be found, the directories named by ^^^ PKG_PATH are searched. It should contain a series of entries separated by colons. Each entry consists of a directory name. URL schemes such as FTP, HTTP, HTTPS, or SCP are also appropriate. On a client machine: PKG_PATH=http://$HTTP_MASTER/:http://$HTTP_MASTER/by_port/i386/all/ My master server serves up normal packages and those packages compiled from ports. When I do this only the first component is searched. I have to do a second package update run with PKG_PATH pointing directly to the ^^ second component for the ports packages to be seen. Why is this? did you give pkg_add a package name? -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
