Re: Secure PKG_PATH for doas
On May 19, 2016 12:49:25 AM GMT+02:00, Igor Mironov <mcs6502-...@yahoo.com.au> wrote: >The packages and ports' FAQ mentions that those using doas need to pass >keepenv { PKG_PATH } in the config file. Is there a way to instruct >doas to take PKG_PATH (or another variable) from the target account's >environment (~/.profile)? As pointed out, $PKG_PATH might not be the solution, but $ doas env PKG_PATH="$PKG_PATH" pkg_add ... Would work for you, unless you want to restrict doas to a certain command. Not that it matters much if you'd allow any custom PKG_PATH anyway. /Alexander /Alexander
Re: Secure PKG_PATH for doas
Sat, 21 May 2016 12:34:58 +0100 Raf Czlonka <rczlo...@gmail.com> > On Sat, May 21, 2016 at 08:55:37AM BST, Marc Espie wrote: > > On Fri, May 20, 2016 at 03:37:48PM +0100, Raf Czlonka wrote: > > > On Fri, May 20, 2016 at 12:39:46PM BST, Igor Mironov wrote: > > > > > > > Thank you Mart, Ted and Stuart--I understood that installpath in > > > > pkg.conf provides a secure default, and PKG_PATH should probably > > > > be used for overrides only (if at all). > > > > > > PKG_PATH is essential - installpath= in pkg.conf(5) won't suffice > > > - if you don't want to build ports' dependencies and prefer to > > > simply have them install as packages, by using: > > > > > > FETCH_PACKAGES=Yes > > > > > > in mk.conf(5). > > > > But that one completely does not require doas since it's run in -n mode. > > Sure, me reply was to the "if at all" part and I was merely pointing > out that 'installpath' doesn't work everywhere and sometimes one must > set PKG_PATH. A suggestion would be to add /etc/mymirror plus related dangling block accessories. It would not work yet without tool propagation to honour this file. Who knows, it may never work, if this idea is quite silly.
Re: Secure PKG_PATH for doas
On Sat, May 21, 2016 at 08:55:37AM BST, Marc Espie wrote: > On Fri, May 20, 2016 at 03:37:48PM +0100, Raf Czlonka wrote: > > On Fri, May 20, 2016 at 12:39:46PM BST, Igor Mironov wrote: > > > > > Thank you Mart, Ted and Stuart--I understood that installpath in > > > pkg.conf provides a secure default, and PKG_PATH should probably > > > be used for overrides only (if at all). > > > > Hi Igor, > > > > PKG_PATH is essential - installpath= in pkg.conf(5) won't suffice > > - if you don't want to build ports' dependencies and prefer to > > simply have them install as packages, by using: > > > > FETCH_PACKAGES=Yes > > > > in mk.conf(5). > > > > Regards, > > > > Raf > > But that one completely does not require doas since it's run in -n mode. Sure, me reply was to the "if at all" part and I was merely pointing out that 'installpath' doesn't work everywhere and sometimes one must set PKG_PATH. Raf
Re: Secure PKG_PATH for doas
On Fri, May 20, 2016 at 03:37:48PM +0100, Raf Czlonka wrote: > On Fri, May 20, 2016 at 12:39:46PM BST, Igor Mironov wrote: > > > Thank you Mart, Ted and Stuart--I understood that installpath in > > pkg.conf provides a secure default, and PKG_PATH should probably > > be used for overrides only (if at all). > > Hi Igor, > > PKG_PATH is essential - installpath= in pkg.conf(5) won't suffice > - if you don't want to build ports' dependencies and prefer to > simply have them install as packages, by using: > > FETCH_PACKAGES=Yes > > in mk.conf(5). > > Regards, > > Raf But that one completely does not require doas since it's run in -n mode.
Re: Secure PKG_PATH for doas
On Fri, May 20, 2016 at 12:39:46PM BST, Igor Mironov wrote: > Thank you Mart, Ted and Stuart--I understood that installpath in > pkg.conf provides a secure default, and PKG_PATH should probably > be used for overrides only (if at all). Hi Igor, PKG_PATH is essential - installpath= in pkg.conf(5) won't suffice - if you don't want to build ports' dependencies and prefer to simply have them install as packages, by using: FETCH_PACKAGES=Yes in mk.conf(5). Regards, Raf
Re: Secure PKG_PATH for doas
Fri, 20 May 2016 00:18:47 + (UTC) Stuart Henderson <s...@spacehopper.org> > On 2016-05-19, Mart Tõnso <xti...@gmail.com> wrote: > > Do feel free to select from the list of actual mirrors: > > http://www.openbsd.org/ftp.html > > Or in /etc/examples/pkg.conf. Which reminds the installer already picks the nearest mirror, an idea to set it in /etc/pkg.conf at install time, and leave PKG_PATH for the user.
Re: Secure PKG_PATH for doas
Fri, 20 May 2016 08:46:47 +0300 li...@wrant.com > Fri, 20 May 2016 00:18:47 + (UTC) Stuart Henderson > <s...@spacehopper.org> > > On 2016-05-19, Mart Tõnso <xti...@gmail.com> wrote: > > > Do feel free to select from the list of actual mirrors: > > > http://www.openbsd.org/ftp.html > > > > Or in /etc/examples/pkg.conf. > > Which reminds the installer already picks the nearest mirror, an idea to > set it in /etc/pkg.conf at install time, and leave PKG_PATH for the user. [http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/distrib/miniroot/ins tall.sub] 2259 # Create or update pkg.conf with the new package path, if any. Appears this idea has already been realised, should have checked upfront ;)
Re: Secure PKG_PATH for doas
Thank you Mart, Ted and Stuart--I understood that installpath in pkg.conf provides a secure default, and PKG_PATH should probably be used for overrides only (if at all). On Friday, 20 May 2016, 3:41, Mart Tõnso <xti...@gmail.com> wrote: There is an alternative to PKG_PATH env var: http://man.openbsd.org/OpenBSD-current/man5/pkg.conf.5 echo "installpath = http://your.favorite.mirror/; > /etc/pkg.conf .. and enjoy! Mart On Thu, May 19, 2016 at 4:32 AM, Ted Unangst <t...@tedunangst.com> wrote: > Igor Mironov wrote: >> The packages and ports' FAQ mentions that those using doas need to pass keepenv { PKG_PATH } in the config file. Is there a way to instruct doas to take PKG_PATH (or another variable) from the target account's environment (~/.profile)? > > No, but you can easily write a shell wrapper that sets things up and calls > pkg_add.
Re: Secure PKG_PATH for doas
On 2016-05-19, Mart Tõnsowrote: > Do feel free to select from the list of actual mirrors: > http://www.openbsd.org/ftp.html Or in /etc/examples/pkg.conf.
Re: Secure PKG_PATH for doas
Do feel free to select from the list of actual mirrors: http://www.openbsd.org/ftp.html Mart On Thu, May 19, 2016 at 10:02 PM, Mihai Popescuwrote: >> echo "installpath = http://your.favorite.mirror/; > /etc/pkg.conf > >> .. and enjoy! > > Error from http://your.favorite.mirror/ > ftp: your.favorite.mirror: no address associated with name > http://your.favorite.mirror/ is empty > > :-)
Re: Secure PKG_PATH for doas
> echo "installpath = http://your.favorite.mirror/; > /etc/pkg.conf > .. and enjoy! Error from http://your.favorite.mirror/ ftp: your.favorite.mirror: no address associated with name http://your.favorite.mirror/ is empty :-)
Re: Secure PKG_PATH for doas
There is an alternative to PKG_PATH env var: http://man.openbsd.org/OpenBSD-current/man5/pkg.conf.5 echo "installpath = http://your.favorite.mirror/; > /etc/pkg.conf .. and enjoy! Mart On Thu, May 19, 2016 at 4:32 AM, Ted Unangst <t...@tedunangst.com> wrote: > Igor Mironov wrote: >> The packages and ports' FAQ mentions that those using doas need to pass >> keepenv { PKG_PATH } in the config file. Is there a way to instruct doas to >> take PKG_PATH (or another variable) from the target account's environment >> (~/.profile)? > > No, but you can easily write a shell wrapper that sets things up and calls > pkg_add.
Re: Secure PKG_PATH for doas
Igor Mironov wrote: > The packages and ports' FAQ mentions that those using doas need to pass > keepenv { PKG_PATH } in the config file. Is there a way to instruct doas to > take PKG_PATH (or another variable) from the target account's environment > (~/.profile)? No, but you can easily write a shell wrapper that sets things up and calls pkg_add.
Re: Secure PKG_PATH for doas
On 2016-05-18, Igor Mironov <mcs6502-...@yahoo.com.au> wrote: > The packages and ports' FAQ mentions that those using doas need to pass > keepenv { PKG_PATH } in the config file. Is there a way to instruct doas to > take PKG_PATH (or another variable) from the target account's environment > (~/.profile)? Not unless you let the target account run a shell. The simplest way is probably to avoid using PKG_PATH (don't set it in keepenv) and put the path in /etc/pkg.conf instead.
Secure PKG_PATH for doas
The packages and ports' FAQ mentions that those using doas need to pass keepenv { PKG_PATH } in the config file. Is there a way to instruct doas to take PKG_PATH (or another variable) from the target account's environment (~/.profile)?
Re: PKG_PATH - SOLVED
Thank you for that tip. On Fri, Apr 8, 2016 at 2:57 PM, Antoine Jacoutot <ajacou...@bsdfrog.org> wrote: > On Fri, Apr 08, 2016 at 09:16:13AM +0200, Peter Hessler wrote: >> On 2016 Apr 07 (Thu) at 22:56:42 +0200 (+0200), Teno Deuter wrote: >> :Hi, >> : >> :just installed a 5.9 AMD64 version and get issues with adding packages as a >> :regular system user. 'env' shows me the correct setting for PKG_PATH but >> :seems that the user environment isn't able to contact the source. >> : >> :As long as I change to 'root', everything works fine! >> : >> :Thank you for your support >> : >> >> You should put it into /etc/pkg.conf instead: >> >> """ >> installpath = http://ftp.hostserver.de/pub/OpenBSD/%c/packages/%a/ >> """ >> >> %c expands out into the version, and %a into the arch. > > I think nowadays you can do something like: > installpath = ftp.hostserver.de > > > -- > Antoine
Re: PKG_PATH
On Fri, Apr 08, 2016 at 09:16:13AM +0200, Peter Hessler wrote: > On 2016 Apr 07 (Thu) at 22:56:42 +0200 (+0200), Teno Deuter wrote: > :Hi, > : > :just installed a 5.9 AMD64 version and get issues with adding packages as a > :regular system user. 'env' shows me the correct setting for PKG_PATH but > :seems that the user environment isn't able to contact the source. > : > :As long as I change to 'root', everything works fine! > : > :Thank you for your support > : > > You should put it into /etc/pkg.conf instead: > > """ > installpath = http://ftp.hostserver.de/pub/OpenBSD/%c/packages/%a/ > """ > > %c expands out into the version, and %a into the arch. I think nowadays you can do something like: installpath = ftp.hostserver.de -- Antoine
Re: PKG_PATH
On 2016 Apr 07 (Thu) at 22:56:42 +0200 (+0200), Teno Deuter wrote: :Hi, : :just installed a 5.9 AMD64 version and get issues with adding packages as a :regular system user. 'env' shows me the correct setting for PKG_PATH but :seems that the user environment isn't able to contact the source. : :As long as I change to 'root', everything works fine! : :Thank you for your support : You should put it into /etc/pkg.conf instead: """ installpath = http://ftp.hostserver.de/pub/OpenBSD/%c/packages/%a/ """ %c expands out into the version, and %a into the arch. -- Any sufficiently advanced technology is indistinguishable from a rigged demo.
Re: PKG_PATH - SOLVED
yes indeed. Thank you On Fri, Apr 8, 2016 at 12:03 AM, Antoine Jacoutot <ajacou...@bsdfrog.org> wrote: > On Thu, Apr 07, 2016 at 11:49:11PM +0200, Teno Deuter wrote: >> I run 'pkg_add' with 'doas' and I get only: >> >> Can't find [the package] I try to install. Doesn't say anything about >> 'root'. >> >> Also, why 'pkg_add' has to be run as root only? In previous OpenBSD version >> this wasn't the case. Is that due to 'doas'? > > doas resets the environment. > If you want to keep PKG_PATH then use something like this in doas.conf: > permit keepenv { PKG_PATH } nopass :wheel > > > -- > Antoine
Re: PKG_PATH
On Thu, Apr 07, 2016 at 11:49:11PM +0200, Teno Deuter wrote: > I run 'pkg_add' with 'doas' and I get only: > > Can't find [the package] I try to install. Doesn't say anything about > 'root'. > > Also, why 'pkg_add' has to be run as root only? In previous OpenBSD version > this wasn't the case. Is that due to 'doas'? doas resets the environment. If you want to keep PKG_PATH then use something like this in doas.conf: permit keepenv { PKG_PATH } nopass :wheel -- Antoine
Re: PKG_PATH
I run 'pkg_add' with 'doas' and I get only: Can't find [the package] I try to install. Doesn't say anything about 'root'. Also, why 'pkg_add' has to be run as root only? In previous OpenBSD version this wasn't the case. Is that due to 'doas'? Thank you On Thu, Apr 7, 2016 at 11:17 PM, Mihai Popescu <mih...@gmail.com> wrote: > > just installed a 5.9 AMD64 version and get issues with adding packages > as a > > regular system user. 'env' shows me the correct setting for PKG_PATH but > > seems that the user environment isn't able to contact the source. > > "Get issues" is not a valid problem report. I am getting issues with > my stomach right now, but this will never tell you what is my problem. > Post the exact message(s) you get. > > You should get something like this: > > $ pkg_add -vn test > pkg_add should be run as root > Can't find test > > This is telling you what to do in order to fix that "issue". > > > As long as I change to 'root', everything works fine! > > Isn't it obvious? > > It may sound crazy, but OpenBSD does not allow any user to install > packages directly, much like Linux or Windows.
Re: PKG_PATH
And how are you installing packages as a non root user? On Apr 7, 2016 22:08, "Teno Deuter" <gvg...@googlemail.com> wrote: > Hi, > > just installed a 5.9 AMD64 version and get issues with adding packages as a > regular system user. 'env' shows me the correct setting for PKG_PATH but > seems that the user environment isn't able to contact the source. > > As long as I change to 'root', everything works fine! > > Thank you for your support
Re: PKG_PATH
> just installed a 5.9 AMD64 version and get issues with adding packages as a > regular system user. 'env' shows me the correct setting for PKG_PATH but > seems that the user environment isn't able to contact the source. "Get issues" is not a valid problem report. I am getting issues with my stomach right now, but this will never tell you what is my problem. Post the exact message(s) you get. You should get something like this: $ pkg_add -vn test pkg_add should be run as root Can't find test This is telling you what to do in order to fix that "issue". > As long as I change to 'root', everything works fine! Isn't it obvious? It may sound crazy, but OpenBSD does not allow any user to install packages directly, much like Linux or Windows.
PKG_PATH
Hi, just installed a 5.9 AMD64 version and get issues with adding packages as a regular system user. 'env' shows me the correct setting for PKG_PATH but seems that the user environment isn't able to contact the source. As long as I change to 'root', everything works fine! Thank you for your support
Re: Set PKG_PATH using Time Zone?
On 2015-03-26, L.R. D.S. arrowscr...@mail.com wrote: Is really boring write the package repository everytime we install. Why not set the repository using the Time Zone as a reference? If you do a network install, the installer already writes an /etc/pkg.conf pointing at the download mirror (and the mirror selection offers nearby mirrors first, and proposes a timezone). For example, if you set Japan as your zone, then run export PKG_PATH=http://www.ftp.ne.jp/OpenBSD/'uname -r'/packages/'uname -m'/ That should be arch -s (it matters for powerpc, arm, loongson etc), and doesn't take snapshots into account.
Re: Set PKG_PATH using Time Zone?
Routing from certain countries can also be funny sometimes (for example, I'm pretty sure users in Peru would get better speeds downloading from US servers rather than from Brazil, despite the geographical proximity). On Thu, Mar 26, 2015 at 4:18 PM, Joshua Smith jsm...@mail.wvnet.edu wrote: On Thu, Mar 26, 2015 at 06:55:50PM +, L.R. D.S. wrote: Is really boring write the package repository everytime we install. Why not set the repository using the Time Zone as a reference? For example, if you set Japan as your zone, then run export PKG_PATH=http://www.ftp.ne.jp/OpenBSD/'uname -r'/packages/'uname -m'/ What about regions which contain multiple mirrors? -- Joshua Smith Montani Semper Liberi
Re: Set PKG_PATH using Time Zone?
On Thu, 26 Mar 2015, L.R. D.S. wrote: Is really boring write the package repository everytime we install. Why not set the repository using the Time Zone as a reference? For example, if you set Japan as your zone, then run export PKG_PATH=http://www.ftp.ne.jp/OpenBSD/'uname -r'/packages/'uname -m'/ #!/usr/bin/perl -w use strict; chomp( my( $uname_r, $uname_m ) = ( `uname -r`, `uname -m` ) ); chomp( my $zone = join( '/', ( split('/', `ls -l /etc/localtime`) )[-2,-1] ) ); my %mirror = ( Canada/Mountain = ftp://ftp.openbsd.org/pub/OpenBSD;, # okay, I'm bored now... hopefully L.R. D.S. will help ); print $mirror{$zone}/$uname_r/packages/$uname_m/;
Set PKG_PATH using Time Zone?
Is really boring write the package repository everytime we install. Why not set the repository using the Time Zone as a reference? For example, if you set Japan as your zone, then run export PKG_PATH=http://www.ftp.ne.jp/OpenBSD/'uname -r'/packages/'uname -m'/
Re: Set PKG_PATH using Time Zone?
On Thu, Mar 26, 2015 at 06:55:50PM +, L.R. D.S. wrote: Is really boring write the package repository everytime we install. Why not set the repository using the Time Zone as a reference? For example, if you set Japan as your zone, then run export PKG_PATH=http://www.ftp.ne.jp/OpenBSD/'uname -r'/packages/'uname -m'/ What about regions which contain multiple mirrors? -- Joshua Smith Montani Semper Liberi
Re: Set PKG_PATH using Time Zone?
On Mar 26, 2015, at 1:39 PM, Dale Lindskog dale.linds...@gmail.com wrote: On Thu, 26 Mar 2015, L.R. D.S. wrote: Is really boring write the package repository everytime we install. Why not set the repository using the Time Zone as a reference? For example, if you set Japan as your zone, then run export PKG_PATH=http://www.ftp.ne.jp/OpenBSD/'uname -r'/packages/'uname -m'/ #!/usr/bin/perl -w use strict; chomp( my( $uname_r, $uname_m ) = ( `uname -r`, `uname -m` ) ); chomp( my $zone = join( '/', ( split('/', `ls -l /etc/localtime`) )[-2,-1] ) ); my %mirror = ( Canada/Mountain = ftp://ftp.openbsd.org/pub/OpenBSD;, # okay, I'm bored now... hopefully L.R. D.S. will help ); print $mirror{$zone}/$uname_r/packages/$uname_m/; Why not go whole hog and traceroute -I everything and see which is faster? :-P BTW: ftp5.usa.openbsd.org seems to not be responding on HTTP, so I dropped them a note. But then I found sonic has a mirror, that, though geographically further, is about 1/2 a ms faster (and two fewer hops). So, it's not just going to other countries where this happens. Sean
No address associated with PKG_PATH mirror
Hello, I get the following error when using any of the pkg_* commands:$ echo $PKG_PATH http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ $ pkg_info -Q mosh Error from http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ ftp: ftp.nluug.nl: no address associated with namehttp://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ is empty This seems to occur with any mirror I choose. I am able to access the directory via a web browser. Examining the logs in real-time with tcpdump doesn't reveal any blocks. Also, there are no errors written to /var/log/messages. Any ideas? Thanks
Re: No address associated with PKG_PATH mirror
Sent: Thursday, November 20, 2014 at 8:06 PM From: John Smith hufflep...@bsdmail.com To: misc@openbsd.org Subject: No address associated with PKG_PATH mirror Hello, I get the following error when using any of the pkg_* commands:$ echo $PKG_PATH http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ $ pkg_info -Q mosh Error from http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/[http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/] ftp: ftp.nluug.nl: no address associated with namehttp://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ is empty This seems to occur with any mirror I choose. I am able to access the directory via a web browser. Examining the logs in real-time with tcpdump doesn't reveal any blocks. Also, there are no errors written to /var/log/messages. Any ideas? Thanks (I apologize for the formatting. Here is the same message in plain text:) I get the following error when using any of the pkg_* commands: $ echo $PKG_PATH http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ $ pkg_info -Q mosh Error from http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ [http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/] ftp: ftp.nluug.nl: no address associated with name http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ is empty This seems to occur with any mirror I choose. I am able to access the directory via a web browser. Examining the logs in real-time with tcpdump doesn't reveal any blocks. Also, there are no errors written to /var/log/messages. Any ideas? Thanks
Re: No address associated with PKG_PATH mirror
I am able to access the mirror via a web browser, however there may be something wrong with my dns: # drill @127.0.0.1 http://ftp.nluug.nl ;; -HEADER- opcode: QUERY, rcode: NXDOMAIN, id: 55283 ;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;; http://ftp.nluug.nl[http://ftp.nluug.nl]. IN A ;; ANSWER SECTION: ;; AUTHORITY SECTION: nluug.nl. 3488 IN SOA ns1.nluug.nl. hostmaster.nluug.nl. 2013111701 28800 7200 604800 3600 ;; ADDITIONAL SECTION: ;; Query time: 0 msec ;; SERVER: 127.0.0.1 ;; WHEN: Thu Nov 20 20:49:40 2014 ;; MSG SIZE rcvd: 88 Sent: Thursday, November 20, 2014 at 8:00 PM From: Cosmo Wu co...@tetrachina.com To: John Smith hufflep...@bsdmail.com Subject: Re: No address associated with PKG_PATH mirror Hi , Is there anything wrong with the DNS or network connection on your OpenBSD box? I could access that using the mirror. On 21.11.2014 10:06, John Smith wrote: Hello, I get the following error when using any of the pkg_* commands:$ echo $PKG_PATH http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/[http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/] $ pkg_info -Q mosh Error from http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/[http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/][http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/[http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/]] ftp: ftp.nluug.nl: no address associated with namehttp://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ is empty This seems to occur with any mirror I choose. I am able to access the directory via a web browser. Examining the logs in real-time with tcpdump doesn't reveal any blocks. Also, there are no errors written to /var/log/messages. Any ideas? Thanks -- Best Regards, Cosmo Wu
Re: No address associated with PKG_PATH mirror
Works for me :) root@rel56[~] echo $PKG_PATH http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ root@rel56[~] pkg_info -Q mosh mosh-1.2.4p1 root@rel56[~] dig ftp.nluug.nl ; DiG 9.4.2-P2 ftp.nluug.nl ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 26971 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;ftp.nluug.nl. IN A ;; ANSWER SECTION: ftp.nluug.nl. 63662 IN A 192.87.102.43 ftp.nluug.nl. 63662 IN A 192.87.102.42 ;; Query time: 2 msec ;; SERVER: 192.168.222.10#53(192.168.222.10) ;; WHEN: Fri Nov 21 04:01:08 2014 ;; MSG SIZE rcvd: 62 On Fri, Nov 21, 2014 at 3:13 AM, John Smith hufflep...@bsdmail.com wrote: Sent: Thursday, November 20, 2014 at 8:06 PM From: John Smith hufflep...@bsdmail.com To: misc@openbsd.org Subject: No address associated with PKG_PATH mirror Hello, I get the following error when using any of the pkg_* commands:$ echo $PKG_PATH http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ $ pkg_info -Q mosh Error from http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/[http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/] ftp: ftp.nluug.nl: no address associated with namehttp:// ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ is empty This seems to occur with any mirror I choose. I am able to access the directory via a web browser. Examining the logs in real-time with tcpdump doesn't reveal any blocks. Also, there are no errors written to /var/log/messages. Any ideas? Thanks (I apologize for the formatting. Here is the same message in plain text:) I get the following error when using any of the pkg_* commands: $ echo $PKG_PATH http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ $ pkg_info -Q mosh Error from http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ [http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/] ftp: ftp.nluug.nl: no address associated with name http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ is empty This seems to occur with any mirror I choose. I am able to access the directory via a web browser. Examining the logs in real-time with tcpdump doesn't reveal any blocks. Also, there are no errors written to /var/log/messages. Any ideas? Thanks
[SOLVED] Re: No address associated with PKG_PATH mirror
Well, I'm not sure what happened but all is well now... # drill @127.0.0.1 ftp.nluug.nl ;; -HEADER- opcode: QUERY, rcode: NOERROR, id: 9907 ;; flags: qr rd ra ; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 3 ;; QUESTION SECTION: ;; ftp.nluug.nl.IN A ;; ANSWER SECTION: ftp.nluug.nl. 76422 IN A 192.87.102.42 ftp.nluug.nl. 76422 IN A 192.87.102.43 ;; AUTHORITY SECTION: nluug.nl. 5610IN NS ns2.nluug.nl. nluug.nl. 5610IN NS ns1.nluug.nl. ;; ADDITIONAL SECTION: ns1.nluug.nl. 5610IN A 46.19.34.198 ns1.nluug.nl. 76422 IN 2a02:2770::21a:4aff:fe01:dd51 ns2.nluug.nl. 5610IN A 193.200.132.194 ;; Query time: 135 msec ;; SERVER: 127.0.0.1 ;; WHEN: Thu Nov 20 21:14:18 2014 ;; MSG SIZE rcvd: 158 # pkg_info -Q mosh mosh-1.2.4p1 (installed) Thanks for the help Sent: Thursday, November 20, 2014 at 9:04 PM From: Adriaan misc.adri...@gmail.com To: OpenBSD general usage list misc@openbsd.org Subject: Re: No address associated with PKG_PATH mirror Works for me :) root@rel56[~] echo $PKG_PATH http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ root@rel56[~] pkg_info -Q mosh mosh-1.2.4p1 root@rel56[~] dig ftp.nluug.nl ; DiG 9.4.2-P2 ftp.nluug.nl ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 26971 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;ftp.nluug.nl. IN A ;; ANSWER SECTION: ftp.nluug.nl. 63662 IN A 192.87.102.43 ftp.nluug.nl. 63662 IN A 192.87.102.42 ;; Query time: 2 msec ;; SERVER: 192.168.222.10#53(192.168.222.10) ;; WHEN: Fri Nov 21 04:01:08 2014 ;; MSG SIZE rcvd: 62 On Fri, Nov 21, 2014 at 3:13 AM, John Smith hufflep...@bsdmail.com wrote: Sent: Thursday, November 20, 2014 at 8:06 PM From: John Smith hufflep...@bsdmail.com To: misc@openbsd.org Subject: No address associated with PKG_PATH mirror Hello, I get the following error when using any of the pkg_* commands:$ echo $PKG_PATH http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/[http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/] $ pkg_info -Q mosh Error from http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/[http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/][http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/[http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/]] ftp: ftp.nluug.nl: no address associated with namehttp:// ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/ is empty This seems to occur with any mirror I choose. I am able to access the directory via a web browser. Examining the logs in real-time with tcpdump doesn't reveal any blocks. Also, there are no errors written to /var/log/messages. Any ideas? Thanks (I apologize for the formatting. Here is the same message in plain text:) I get the following error when using any of the pkg_* commands: $ echo $PKG_PATH http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/[http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/] $ pkg_info -Q mosh Error from http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/[http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/] [http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/[http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/]] ftp: ftp.nluug.nl: no address associated with name http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/[http://ftp.nluug.nl/pub/OpenBSD/5.6/packages/amd64/] is empty This seems to occur with any mirror I choose. I am able to access the directory via a web browser. Examining the logs in real-time with tcpdump doesn't reveal any blocks. Also, there are no errors written to /var/log/messages. Any ideas? Thanks
Re: Why are there no PKG_PATH defaults?
This setup would be great and make life easier for the average user without making the story complicated (i.e. a system with downloads working out of the box without hassles) Also ports.tar.gz fetch would be one further hassle less. Il 24/set/2014 23:36 Romain FABBRI - Alien Consulting romain.fab...@alienconsulting.net ha scritto: One think that could be done without hammering servers when you install from CD would be to add a question to the install script : Would you like to define the PKG PATH ? : - [1] : propose mirrors based on the timezone given (and then provide a menu and you just have to select the proxy) - [2] : manually define PKG PATH (type the string, could even check if the path seems valid) - [3] : nope thanks But would it really help much ? Romain -Message d'origine- De : owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] De la part de Alexander Hall Envoyé : mercredi 24 septembre 2014 23:20 à : Ville Valkonen Cc : PPC Miscellaneous Discussions Objet : Re: Why are there no PKG_PATH defaults? On 09/24/14 23:09, Ville Valkonen wrote: Out of curiosity, what's wrong with the one that installer uses? Nothing, however the installer only cares about a mirror if you actually install from one of them. If you install from e.g. CD, you don't have a selected mirror. If you do install or upgrade (I'm pretty sure) from a mirror, /etc/pkg.conf will be updated accordingly. /Alexander -- Regards, Ville On 24 September 2014 19:34, Alexander Hall alexan...@beard.se wrote: On September 24, 2014 6:09:04 PM CEST, openda...@hushmail.com wrote: Indeed, the installer only creates that if you install from a mirror. Apart from that, as someone else pointed out, which mirror should one choose? Cool, I didn't know that. Then, in the event that someone installed via an ISO or some pre-defined VM (ie. a DigitalOcean droplets) -- how about a one-time script upon first root login to ask for such info? You do not have a `PKG_PATH` set for `pkg_add`. Would you like us to set it for you? (Y/n) y Choose your nearest mirror: 1. Continent 2. Whatever 3. ... There is currently no ports collection in `/usr/ports`. Would you like us to get it for you? (Y/n) I can't speak for others, but I'd be terribly annoyed by this. Also, the script isn't trivial. Feel free to give it a go, share and use it for your own sake, but I'd be surprised to see it go in. /Alexander Thanks! O.D. On 24. september 2014 at 1:05 PM, Alexander Hall wrote:On September 24, 2014 12:44:14 PM CEST, openda...@hushmail.com wrote: Because /etc/pkg.conf ? Sorry, no such file over here. Indeed, the installer only creates that if you install from a mirror. Apart from that, as someone else pointed out, which mirror should one choose? /Alexander O.D. On 23. september 2014 at 1:47 PM, Alexander Hall wrote:On September 23, 2014 3:00:41 PM CEST, openda...@hushmail.com wrote: Hi, Expanding on the whole http://en.wikipedia.org/wiki/Convention_over_configuration thing -- why aren't there any sane PKG_PATH defaults? Ie.: release=$(uname -r) architecture=$(uname -p) export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${a rchitecture}/ Because /etc/pkg.conf ? /Alexander Thanks! O.D.
Re: Why are there no PKG_PATH defaults?
On 25 September 2014 01:30, Dmitrij D. Czarkoff czark...@gmail.com wrote: openda...@hushmail.com said: Then, in the event that someone installed via an ISO or some pre-defined VM (ie. a DigitalOcean droplets) -- how about a one-time script upon first root login to ask for such info? You do not have a `PKG_PATH` set for `pkg_add`. Would you like us to set it for you? (Y/n) y Choose your nearest mirror: 1. Continent 2. Whatever 3. ... FWIW the idea of presenting the list of mirrors suddenly starts to make sense, as now there is no browser in base install. But Alexander Hall said: I can't speak for others, but I'd be terribly annoyed by this. I absolutely agree with this sentiment. In my opinion, the best way to present list of mirrors would be to provide a command for fetching it, either in pkg_add(1) or in root.mail (the message root recieves upon completion of installation). As I prefer the latter way, patch to root.mail follows. -- Dmitrij D. Czarkoff Index: root.mail === RCS file: /var/cvs/src/etc/root/root.mail,v retrieving revision 1.104 diff -u -p -r1.104 root.mail --- root.mail 15 Jul 2014 22:05:29 - 1.104 +++ root.mail 24 Sep 2014 22:05:12 - @@ -36,7 +36,9 @@ full list of packages for each architect ftp://ftp.openbsd.org/pub/OpenBSD/5.6/packages/ If you do not find a package you want on the CD, please go look at your -nearest FTP mirror site. +nearest FTP mirror site. To get a list of available mirrors, execute: + + ftp -o - http://ftp.openbsd.org/cgi-bin/ftplist.cgi Select your architecture and download the tarballs of your choice. For example to install the emacs package for amd64, execute: Not that this would be a voting thing but I like the direction where this is heading. More convenient than writing the address down or remembering it. -- Regards, Ville
Re: Why are there no PKG_PATH defaults?
Hi, Harald Dunkel wrote on Wed, Sep 24, 2014 at 07:14:21AM +0200: This is something that could be added to /etc/examples. See the attachment suggesting a first version. I hate that. Examples should not duplicate manual pages. That merely causes double maintenance effort for developers. Let's not make documentation maintenance harder on ourselves. It also doesn't make things easier for users, quite to the contrary. Chances are both copies of the documentation will eventually get out of sync, and then it's overtly confusing. And even if we manage to prevent explicit contradictions from creeping in, there will be some stuff documented only in one of the places, some stuff only in the other place. So now users have to look at *two* places where formerly it was sufficient to look only at one. They now have to read the double amount of text for almost the same information - and they have to stay very attententive because either copy might contain the bit of information they are searching for, buried among boring duplication. Even if we manage to keep the two completely in sync, such that both contain exactly the same information, it still improves nothing. Then we merely train users to not read the documentation, which we certainly don't want to do: It would hurt them, because in almost all other places, not reading the documentation usually leads to screwing up. In general, i think we should handle examples roughly as follows: 1. When something is completely trivial (like fullwidth=yes) and there is no way to not understand it from the text of the manual itself, there shouldn't be any example, neither in the manual nor in an example file. It would just make the documentation longer for no gain. 2. Examples make sense when something has a minimum level of complexity such that looking at the examples make understanding easier. Examples should focus on the parts hard to understand and never try to be exhaustive. If the total amount of examples required comfortably fits into the EXAMPLES section of the manual, that's where they should go, and there should be no separate examples file. 3. Only when something is so difficult that it requires a large amount of examples that would seem excessive in the manual, I would deem a separate example file appropriate. Don't take these as hard rules, each individual case requires good judgement how it's easiest for the average user. Note that some of the files in /etc/examples could use cleanup. It was the right thing to just move them and *not* mix moving and cleanup, but now it's time for cleanup. For example, from a *very* superficial scan, exports, ftpchroot, hosts.lpd, mixerctl.conf, rc.local, rc.securelevel, and rc.shutdown could be deleted outright, and ntpd.conf, printcap, rbootd.conf, sasyncd.conf, sensorsd.conf look suspicious. But that's a separate matter. Anyway, i oppose the addition of the file /etc/examples/pkg.conf, no matter what the content. I consider pkg.conf(1) a textbook example of a file format so trivial that any examples would be superfluous and distracting verbiage. Yours, Ingo # Set to yes if you really want to use the full width of the # terminal for the progressmeter. # fullwidth = yes # pkg_add(1) and pkg_delete(1) will syslog(3) installations, # updates and deletions by default. Set to 0 to avoid logging # entirely. Levels higher than 1 may log more information in # the future. # loglevel = 0 # URL to package repository updated during installation. Used # for accessing packages if the environment variable PKG_PATH # is not defined and no further options are defined. # installpath = # Set to yes to waive checksums during package deletions. # nochecksum = yes # Set to yes to display (done/total) number of package # messages. # ntogo = yes
Re: Why are there no PKG_PATH defaults?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Ingo, On 09/24/14 11:29, Ingo Schwarze wrote: Hi, Harald Dunkel wrote on Wed, Sep 24, 2014 at 07:14:21AM +0200: This is something that could be added to /etc/examples. See the attachment suggesting a first version. I hate that. Examples should not duplicate manual pages. That merely causes double maintenance effort for developers. Let's not make documentation maintenance harder on ourselves. It also doesn't make things easier for users, quite to the contrary. Chances are both copies of the documentation will eventually get out of sync, and then it's overtly confusing. And even if we manage to prevent explicit contradictions from creeping in, there will be some stuff documented only in one of the places, some stuff only in the other place. So now users have to look at *two* places where formerly it was sufficient to look only at one. They now have to read the double amount of text for almost the same information - and they have to stay very attententive because either copy might contain the bit of information they are searching for, buried among boring duplication. I completely agree, but that seems 2b the case for _all_ files in /etc/examples (or for config files in general). As a user I love to find a config file in /etc briefly showing me the most important options, their default value (something that is clearly missing in pkg.conf(5)) and some explaining words. One file to read and edit. Its a starting point. The man page isn't. Just imagine you had never configured dovecot before, and now you have to create a config file from scratch, using just the man pages. BTW, when I installed 5.6 for the first time, I thought that I made an installation error, since the usual /etc/sysctl.conf and /etc/ntp.conf and the others were gone. Its unexpected for openBSD that these files are hidden somewhere else. Of course I understand the intention to avoid upgrade problems. Regards Harri iQEcBAEBCAAGBQJUIptoAAoJEAqeKp5m04HLmDgIAIHW7Mv2LTVD0IW5vyQSwa8n e+7UvKcAqu3VIL28Z1zJMp0GyI4IbnqnnNECuBcyWIRBzHQXddL3r9kykfdjKEvH 723JIN1rlNl1DXd0yNt+2bX+6++9WScIdRmExEhH4w7IUKfOZqnDAHoY/DMUhe1/ g9+CcKh2yz5PtH500Qw6B0nImPvzNPUxZxqxtiLPWtoNnSrDACKPLXV6A/wtjDAQ +RJAByqrCbA+CknbzXLosa/46NyOfOwKBr92CmBYKGNkGQDg8LJgdbqcBhJOxje3 MQGfIxQXWQDMnIOnKFJ6ZcWji2n+s4flG8wZXSa2lHgMHxDLZAnK5nC9USPlrwM= =hr41 -END PGP SIGNATURE-
Re: Why are there no PKG_PATH defaults?
Because /etc/pkg.conf ? Sorry, no such file over here. O.D. On 23. september 2014 at 1:47 PM, Alexander Hall wrote:On September 23, 2014 3:00:41 PM CEST, openda...@hushmail.com wrote: Hi, Expanding on the whole http://en.wikipedia.org/wiki/Convention_over_configuration thing -- why aren't there any sane PKG_PATH defaults? Ie.: release=$(uname -r) architecture=$(uname -p) export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${architecture}/ Because /etc/pkg.conf ? /Alexander Thanks! O.D.
Re: Why are there no PKG_PATH defaults?
OpenBSD solution is to ask the user to choose a mirror at installation time. I don't see this preference being remembered after the installation though. O.D. On 23. september 2014 at 1:25 PM, ludovic coues wrote: why aren't there any sane PKG_PATH defaults? Ie.: release=$(uname -r) architecture=$(uname -p) export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${architecture}/ The point of such default would be to not change the server, resulting in a big load on it. Such problem prompted archlinux to throttle their main repository server to force user to choose a mirror more adapted to geographic situation. OpenBSD solution is to ask the user to choose a mirror at installation time. -- Cordialement, Coues Ludovic +336 148 743 42
Re: Why are there no PKG_PATH defaults?
Because your sane default includes ftp.openbsd.org, which is not sane at all. If PKG_PATH or /etc/pkg.conf were set to default to ftp.openbsd.org then that host would get hammered instead of the user being put in the position of choosing a local mirror. The proper local mirror should ofcourse be set during the installation. O.D. On 24. september 2014 at 5:37 AM, openbsd2012 wrote:| -Original Message- | From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On | Behalf Of openda...@hushmail.com | Sent: Tuesday, September 23, 2014 6:01 AM | Subject: Why are there no PKG_PATH defaults? ... | Expanding on the whole | http://en.wikipedia.org/wiki/Convention_over_configuration thing -- why | aren't there any sane PKG_PATH defaults? Ie.: | | release=$(uname -r) | architecture=$(uname -p) | | export | PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${arc | hitecture}/ | Because your sane default includes ftp.openbsd.org, which is not sane at all. If PKG_PATH or /etc/pkg.conf were set to default to ftp.openbsd.org then that host would get hammered instead of the user being put in the position of choosing a local mirror. -Breeno PS - In anticipation of the typical follow-up argument, whether or not there is a large existing base of lazy people who fail to choose a local mirror is not a valid argument for defaulting all users to ftp.openbsd.org. Such reasoning would merely exacerbate the trouble with the hypothetical status quo.
Re: Why are there no PKG_PATH defaults?
I think leave this to devs. to decide what they should and what they shouldn't provide. :) All we can do is remember echo installpath=ftp://ftp5.usa.openbsd.org/pub/OpenBSD/$(uname -r)/packages/$(uname -m) | sudo tee /etc/pkg.conf On Wed, Sep 24, 2014 at 4:15 PM, openda...@hushmail.com wrote: OpenBSD solution is to ask the user to choose a mirror at installation time. I don't see this preference being remembered after the installation though. O.D. On 23. september 2014 at 1:25 PM, ludovic coues wrote: why aren't there any sane PKG_PATH defaults? Ie.: release=$(uname -r) architecture=$(uname -p) export PKG_PATH= ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${architecture}/ The point of such default would be to not change the server, resulting in a big load on it. Such problem prompted archlinux to throttle their main repository server to force user to choose a mirror more adapted to geographic situation. OpenBSD solution is to ask the user to choose a mirror at installation time. -- Cordialement, Coues Ludovic +336 148 743 42
Re: Why are there no PKG_PATH defaults?
Just to point out if you do an install where you do select a mirror your mirror settings do seem to persist beyond the install, so it sounds like the problem is solved and user education is in order. *washes hands of the problem* -- Jason Barbier | jab...@serversave.us Pro Patria Vigilans
Re: Why are there no PKG_PATH defaults?
On 24 September 2014 14:12, Barbier, Jason jab...@serversave.us wrote: Just to point out if you do an install where you do select a mirror your mirror settings do seem to persist beyond the install, so it sounds like the problem is solved and user education is in order. *washes hands of the problem* -- Jason Barbier | jab...@serversave.us Pro Patria Vigilans And once you are behind a slow Internet connection and use a local medium... all you can do is to remember :( -- Regards, Ville
Re: Why are there no PKG_PATH defaults?
Hi, Harald Dunkel wrote on Wed, Sep 24, 2014 at 12:22:32PM +0200: I completely agree, but that seems 2b the case for _all_ files in /etc/examples (or for config files in general). Not really all. Take dhcpd.conf for example. Here the complexity comes from the fact that a wide variety of statements is supported, that most are unneeded for a typical simple configuration, but that it's all the same easy to forget one of the things that are needed for a typical simple configuration. Besides, even a simple configuration usually requires more than one level of nesting. So the example file can show: This is what you probably don't want to forget, and how to assemble it all. Another example that is not useless is the new httpd.conf. Yet another example that is useful is sysctl.conf, even though the reasons are different. It lists a selection of variables more likely to need tweaking than others. No doubt, there are more that already are useful, and maybe some could be made useful. As a user I love to find a config file in /etc briefly showing me the most important options, their default value (something that is clearly missing in pkg.conf(5)) Not true. If you read the options list in the manual carefully, the defaults of all five options are obvious: fullwidth = no loglevel = 1 installpath (unset) nochecksum = no ntogo = no and some explaining words. One file to read and edit. That's exactly why it's such a bad idea. Users don't read the manual, miss important stuff, and hurt themselves. Its a starting point. The man page isn't. That's not true. The pkg.conf(1) manual is a perfect example of how to do it, let me cite: The file /etc/pkg.conf contains system-wide options related to package handling, as a list of `keyword=value' lines. [...] Currently defined options are as follows: [... list ...] Concise, crystal clear, the perfect starting point. And it all fits on one screen (56 lines including headers and footers). Just imagine you had never configured dovecot before, and now you have to create a config file from scratch, using just the man pages. Well, dovecot definitely is the prime example of how *NOT* to do it. It's the ultimate mess. The example file is so long that you almost certainly don't want to read it completely, at least 95% of it is completely irrelevant for almost all users. And they gratuitiouly change large portions of it for each minor release, so keeping that file in sync is a nightmare. While i update all daemons as often as i can, dovecot is an exception. I update that one as rarely as i can, for the very reason of not wasting my time on that horrible mess of a config file that doesn't even deserve the name config file, it should rather be called misformatted documentation. BTW, when I installed 5.6 for the first time, I thought that I made an installation error, since the usual /etc/sysctl.conf and /etc/ntp.conf and the others were gone. Its unexpected for openBSD that these files are hidden somewhere else. Of course I understand the intention to avoid upgrade problems. Yeah, that's the downside of improvement, it's unavoidable that it causes surprise at first. But as long as things get simpler, not more complicated, that's acceptable, i think. Yours, Ingo
Re: Why are there no PKG_PATH defaults?
On September 24, 2014 12:44:14 PM CEST, openda...@hushmail.com wrote: Because /etc/pkg.conf ? Sorry, no such file over here. Indeed, the installer only creates that if you install from a mirror. Apart from that, as someone else pointed out, which mirror should one choose? /Alexander O.D. On 23. september 2014 at 1:47 PM, Alexander Hall wrote:On September 23, 2014 3:00:41 PM CEST, openda...@hushmail.com wrote: Hi, Expanding on the whole http://en.wikipedia.org/wiki/Convention_over_configuration thing -- why aren't there any sane PKG_PATH defaults? Ie.: release=$(uname -r) architecture=$(uname -p) export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${architecture}/ Because /etc/pkg.conf ? /Alexander Thanks! O.D.
Re: Why are there no PKG_PATH defaults?
Indeed, the installer only creates that if you install from a mirror. Apart from that, as someone else pointed out, which mirror should one choose? Cool, I didn't know that. Then, in the event that someone installed via an ISO or some pre-defined VM (ie. a DigitalOcean droplets) -- how about a one-time script upon first root login to ask for such info? You do not have a `PKG_PATH` set for `pkg_add`. Would you like us to set it for you? (Y/n) y Choose your nearest mirror: 1. Continent 2. Whatever 3. ... There is currently no ports collection in `/usr/ports`. Would you like us to get it for you? (Y/n) Thanks! O.D. On 24. september 2014 at 1:05 PM, Alexander Hall wrote:On September 24, 2014 12:44:14 PM CEST, openda...@hushmail.com wrote: Because /etc/pkg.conf ? Sorry, no such file over here. Indeed, the installer only creates that if you install from a mirror. Apart from that, as someone else pointed out, which mirror should one choose? /Alexander O.D. On 23. september 2014 at 1:47 PM, Alexander Hall wrote:On September 23, 2014 3:00:41 PM CEST, openda...@hushmail.com wrote: Hi, Expanding on the whole http://en.wikipedia.org/wiki/Convention_over_configuration thing -- why aren't there any sane PKG_PATH defaults? Ie.: release=$(uname -r) architecture=$(uname -p) export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${architecture}/ Because /etc/pkg.conf ? /Alexander Thanks! O.D.
Re: Why are there no PKG_PATH defaults?
| -Original Message- | From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On | Behalf Of openda...@hushmail.com | Sent: Tuesday, September 23, 2014 6:01 AM | Subject: Why are there no PKG_PATH defaults? ... | Expanding on the whole | http://en.wikipedia.org/wiki/Convention_over_configuration thing -- why | aren't there any sane PKG_PATH defaults? Ie.: | | release=$(uname -r) | architecture=$(uname -p) | | export | PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${arc | hitecture}/ | Because your sane default includes ftp.openbsd.org, which is not sane at all. If PKG_PATH or /etc/pkg.conf were set to default to ftp.openbsd.org then that host would get hammered instead of the user being put in the position of choosing a local mirror. -Breeno PS - In anticipation of the typical follow-up argument, whether or not there is a large existing base of lazy people who fail to choose a local mirror is not a valid argument for defaulting all users to ftp.openbsd.org. Such reasoning would merely exacerbate the trouble with the hypothetical status quo.
Re: Why are there no PKG_PATH defaults?
On September 24, 2014 6:09:04 PM CEST, openda...@hushmail.com wrote: Indeed, the installer only creates that if you install from a mirror. Apart from that, as someone else pointed out, which mirror should one choose? Cool, I didn't know that. Then, in the event that someone installed via an ISO or some pre-defined VM (ie. a DigitalOcean droplets) -- how about a one-time script upon first root login to ask for such info? You do not have a `PKG_PATH` set for `pkg_add`. Would you like us to set it for you? (Y/n) y Choose your nearest mirror: 1. Continent 2. Whatever 3. ... There is currently no ports collection in `/usr/ports`. Would you like us to get it for you? (Y/n) I can't speak for others, but I'd be terribly annoyed by this. Also, the script isn't trivial. Feel free to give it a go, share and use it for your own sake, but I'd be surprised to see it go in. /Alexander Thanks! O.D. On 24. september 2014 at 1:05 PM, Alexander Hall wrote:On September 24, 2014 12:44:14 PM CEST, openda...@hushmail.com wrote: Because /etc/pkg.conf ? Sorry, no such file over here. Indeed, the installer only creates that if you install from a mirror. Apart from that, as someone else pointed out, which mirror should one choose? /Alexander O.D. On 23. september 2014 at 1:47 PM, Alexander Hall wrote:On September 23, 2014 3:00:41 PM CEST, openda...@hushmail.com wrote: Hi, Expanding on the whole http://en.wikipedia.org/wiki/Convention_over_configuration thing -- why aren't there any sane PKG_PATH defaults? Ie.: release=$(uname -r) architecture=$(uname -p) export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${architecture}/ Because /etc/pkg.conf ? /Alexander Thanks! O.D.
Re: Why are there no PKG_PATH defaults?
I thought this kind of suggestion are not answered anymore on this list ... @Ingo Schwarze: why don't you remove the files in /etc/examples and put some examples in man pages, for the apps that have no such thing yet?
Re: Why are there no PKG_PATH defaults?
Hi Mihai, Mihai Popescu wrote on Wed, Sep 24, 2014 at 08:19:39PM +0200: I thought this kind of suggestion are not answered anymore on this list ... What i saw didn't look like a troll to me. Sorry for the noise in case i accidentally fed one. @Ingo Schwarze: why don't you remove the files in /etc/examples Not all of them should be removed. In some cases, having more or more complex examples than a manual can usefully contain seems helpful. The notable example of an example file that needs improvement is pf.conf - though putting the right things there isn't exactly trivial, so sending patches for that one requires *lots* of experience and knowledge. I think *some* example files can be removed, and maybe i might do that, if i come round to make specific suggestions and get OKs for them. and put some examples in man pages, for the apps that have no such thing yet? That may be useful in some cases, though i cannot say in which ones without looking at the details. If you think that a particular page can be improved by sparingly adding examples, feel free to send patches, that might speed up the process. Yours, Ingo
Re: Why are there no PKG_PATH defaults?
On 24 September 2014, Mihai Popescu mih...@gmail.com wrote: I thought this kind of suggestion are not answered anymore on this list ... @Ingo Schwarze: why don't you remove the files in /etc/examples and put some examples in man pages, for the apps that have no such thing yet? I believe the new sysmerge looks at /etc/examples? Regards, Liviu Daia
Re: Why are there no PKG_PATH defaults?
Out of curiosity, what's wrong with the one that installer uses? -- Regards, Ville On 24 September 2014 19:34, Alexander Hall alexan...@beard.se wrote: On September 24, 2014 6:09:04 PM CEST, openda...@hushmail.com wrote: Indeed, the installer only creates that if you install from a mirror. Apart from that, as someone else pointed out, which mirror should one choose? Cool, I didn't know that. Then, in the event that someone installed via an ISO or some pre-defined VM (ie. a DigitalOcean droplets) -- how about a one-time script upon first root login to ask for such info? You do not have a `PKG_PATH` set for `pkg_add`. Would you like us to set it for you? (Y/n) y Choose your nearest mirror: 1. Continent 2. Whatever 3. ... There is currently no ports collection in `/usr/ports`. Would you like us to get it for you? (Y/n) I can't speak for others, but I'd be terribly annoyed by this. Also, the script isn't trivial. Feel free to give it a go, share and use it for your own sake, but I'd be surprised to see it go in. /Alexander Thanks! O.D. On 24. september 2014 at 1:05 PM, Alexander Hall wrote:On September 24, 2014 12:44:14 PM CEST, openda...@hushmail.com wrote: Because /etc/pkg.conf ? Sorry, no such file over here. Indeed, the installer only creates that if you install from a mirror. Apart from that, as someone else pointed out, which mirror should one choose? /Alexander O.D. On 23. september 2014 at 1:47 PM, Alexander Hall wrote:On September 23, 2014 3:00:41 PM CEST, openda...@hushmail.com wrote: Hi, Expanding on the whole http://en.wikipedia.org/wiki/Convention_over_configuration thing -- why aren't there any sane PKG_PATH defaults? Ie.: release=$(uname -r) architecture=$(uname -p) export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${architecture}/ Because /etc/pkg.conf ? /Alexander Thanks! O.D.
Re: Why are there no PKG_PATH defaults?
On 09/24/14 23:09, Ville Valkonen wrote: Out of curiosity, what's wrong with the one that installer uses? Nothing, however the installer only cares about a mirror if you actually install from one of them. If you install from e.g. CD, you don't have a selected mirror. If you do install or upgrade (I'm pretty sure) from a mirror, /etc/pkg.conf will be updated accordingly. /Alexander -- Regards, Ville On 24 September 2014 19:34, Alexander Hall alexan...@beard.se wrote: On September 24, 2014 6:09:04 PM CEST, openda...@hushmail.com wrote: Indeed, the installer only creates that if you install from a mirror. Apart from that, as someone else pointed out, which mirror should one choose? Cool, I didn't know that. Then, in the event that someone installed via an ISO or some pre-defined VM (ie. a DigitalOcean droplets) -- how about a one-time script upon first root login to ask for such info? You do not have a `PKG_PATH` set for `pkg_add`. Would you like us to set it for you? (Y/n) y Choose your nearest mirror: 1. Continent 2. Whatever 3. ... There is currently no ports collection in `/usr/ports`. Would you like us to get it for you? (Y/n) I can't speak for others, but I'd be terribly annoyed by this. Also, the script isn't trivial. Feel free to give it a go, share and use it for your own sake, but I'd be surprised to see it go in. /Alexander Thanks! O.D. On 24. september 2014 at 1:05 PM, Alexander Hall wrote:On September 24, 2014 12:44:14 PM CEST, openda...@hushmail.com wrote: Because /etc/pkg.conf ? Sorry, no such file over here. Indeed, the installer only creates that if you install from a mirror. Apart from that, as someone else pointed out, which mirror should one choose? /Alexander O.D. On 23. september 2014 at 1:47 PM, Alexander Hall wrote:On September 23, 2014 3:00:41 PM CEST, openda...@hushmail.com wrote: Hi, Expanding on the whole http://en.wikipedia.org/wiki/Convention_over_configuration thing -- why aren't there any sane PKG_PATH defaults? Ie.: release=$(uname -r) architecture=$(uname -p) export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${architecture}/ Because /etc/pkg.conf ? /Alexander Thanks! O.D.
Re: Why are there no PKG_PATH defaults?
One think that could be done without hammering servers when you install from CD would be to add a question to the install script : Would you like to define the PKG PATH ? : - [1] : propose mirrors based on the timezone given (and then provide a menu and you just have to select the proxy) - [2] : manually define PKG PATH (type the string, could even check if the path seems valid) - [3] : nope thanks But would it really help much ? Romain -Message d'origine- De : owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] De la part de Alexander Hall Envoyé : mercredi 24 septembre 2014 23:20 À : Ville Valkonen Cc : PPC Miscellaneous Discussions Objet : Re: Why are there no PKG_PATH defaults? On 09/24/14 23:09, Ville Valkonen wrote: Out of curiosity, what's wrong with the one that installer uses? Nothing, however the installer only cares about a mirror if you actually install from one of them. If you install from e.g. CD, you don't have a selected mirror. If you do install or upgrade (I'm pretty sure) from a mirror, /etc/pkg.conf will be updated accordingly. /Alexander -- Regards, Ville On 24 September 2014 19:34, Alexander Hall alexan...@beard.se wrote: On September 24, 2014 6:09:04 PM CEST, openda...@hushmail.com wrote: Indeed, the installer only creates that if you install from a mirror. Apart from that, as someone else pointed out, which mirror should one choose? Cool, I didn't know that. Then, in the event that someone installed via an ISO or some pre-defined VM (ie. a DigitalOcean droplets) -- how about a one-time script upon first root login to ask for such info? You do not have a `PKG_PATH` set for `pkg_add`. Would you like us to set it for you? (Y/n) y Choose your nearest mirror: 1. Continent 2. Whatever 3. ... There is currently no ports collection in `/usr/ports`. Would you like us to get it for you? (Y/n) I can't speak for others, but I'd be terribly annoyed by this. Also, the script isn't trivial. Feel free to give it a go, share and use it for your own sake, but I'd be surprised to see it go in. /Alexander Thanks! O.D. On 24. september 2014 at 1:05 PM, Alexander Hall wrote:On September 24, 2014 12:44:14 PM CEST, openda...@hushmail.com wrote: Because /etc/pkg.conf ? Sorry, no such file over here. Indeed, the installer only creates that if you install from a mirror. Apart from that, as someone else pointed out, which mirror should one choose? /Alexander O.D. On 23. september 2014 at 1:47 PM, Alexander Hall wrote:On September 23, 2014 3:00:41 PM CEST, openda...@hushmail.com wrote: Hi, Expanding on the whole http://en.wikipedia.org/wiki/Convention_over_configuration thing -- why aren't there any sane PKG_PATH defaults? Ie.: release=$(uname -r) architecture=$(uname -p) export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${a rchitecture}/ Because /etc/pkg.conf ? /Alexander Thanks! O.D.
Re: Why are there no PKG_PATH defaults?
openda...@hushmail.com said: Then, in the event that someone installed via an ISO or some pre-defined VM (ie. a DigitalOcean droplets) -- how about a one-time script upon first root login to ask for such info? You do not have a `PKG_PATH` set for `pkg_add`. Would you like us to set it for you? (Y/n) y Choose your nearest mirror: 1. Continent 2. Whatever 3. ... FWIW the idea of presenting the list of mirrors suddenly starts to make sense, as now there is no browser in base install. But Alexander Hall said: I can't speak for others, but I'd be terribly annoyed by this. I absolutely agree with this sentiment. In my opinion, the best way to present list of mirrors would be to provide a command for fetching it, either in pkg_add(1) or in root.mail (the message root recieves upon completion of installation). As I prefer the latter way, patch to root.mail follows. -- Dmitrij D. Czarkoff Index: root.mail === RCS file: /var/cvs/src/etc/root/root.mail,v retrieving revision 1.104 diff -u -p -r1.104 root.mail --- root.mail 15 Jul 2014 22:05:29 - 1.104 +++ root.mail 24 Sep 2014 22:05:12 - @@ -36,7 +36,9 @@ full list of packages for each architect ftp://ftp.openbsd.org/pub/OpenBSD/5.6/packages/ If you do not find a package you want on the CD, please go look at your -nearest FTP mirror site. +nearest FTP mirror site. To get a list of available mirrors, execute: + + ftp -o - http://ftp.openbsd.org/cgi-bin/ftplist.cgi Select your architecture and download the tarballs of your choice. For example to install the emacs package for amd64, execute:
Why are there no PKG_PATH defaults?
Hi, Expanding on the whole http://en.wikipedia.org/wiki/Convention_over_configuration thing -- why aren't there any sane PKG_PATH defaults? Ie.: release=$(uname -r) architecture=$(uname -p) export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${architecture}/ Thanks! O.D.
Re: Why are there no PKG_PATH defaults?
On September 23, 2014 3:00:41 PM CEST, openda...@hushmail.com wrote: Hi, Expanding on the whole http://en.wikipedia.org/wiki/Convention_over_configuration thing -- why aren't there any sane PKG_PATH defaults? Ie.: release=$(uname -r) architecture=$(uname -p) export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${architecture}/ Because /etc/pkg.conf ? /Alexander Thanks! O.D.
Re: Why are there no PKG_PATH defaults?
On 09/23/14 15:48, Alexander Hall wrote: On September 23, 2014 3:00:41 PM CEST, openda...@hushmail.com wrote: Hi, Expanding on the whole http://en.wikipedia.org/wiki/Convention_over_configuration thing -- why aren't there any sane PKG_PATH defaults? Ie.: release=$(uname -r) architecture=$(uname -p) export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/${release}/packages/${architecture}/ Because /etc/pkg.conf ? This is something that could be added to /etc/examples. See the attachment suggesting a first version. Regards Harri # Set to yes if you really want to use the full width of the # terminal for the progressmeter. # fullwidth = yes # pkg_add(1) and pkg_delete(1) will syslog(3) installations, # updates and deletions by default. Set to 0 to avoid logging # entirely. Levels higher than 1 may log more information in # the future. # loglevel = 0 # URL to package repository updated during installation. Used # for accessing packages if the environment variable PKG_PATH # is not defined and no further options are defined. # installpath = # Set to yes to waive checksums during package deletions. # nochecksum = yes # Set to yes to display (done/total) number of package # messages. # ntogo = yes signature.asc Description: OpenPGP digital signature
Re: ports not detecting packages in PKG_PATH
But you wrote that you upgraded ports from release to current. Did you upgrade your system to current too? Every time use mirrors for packages, it saves bandwidth and you can have couple of them in PKG_PATH. Quoth section 15 of the FAQ: Do NOT check out a -current ports tree and expect it to work on a -release or -stable system. This is one of the most common errors and you will irritate people when you ask for help about why nothing seems to work! D'oh! Sorry, I misread that originally, and I had thought that it was saying that we shouldn't mix different branches of ports together, not different branches of ports and the system. Indeed, that exactly what I've done. My apologies, a classic RTFM. -Ersin -- Ersin Y. Akinci -- ersinakinci.com What Digital Revolution? -- www.whatdigitalrevolution.com Thinking critically about digital worlds.
Re: ports not detecting packages in PKG_PATH
On Wed, Nov 10, 2010 at 1:48 AM, Ersin Akinci ersin.aki...@gmail.comwrote: Do the packages in current normally find themselves in the next release? Yes.
Re: ports not detecting packages in PKG_PATH
On Wed, Nov 10, 2010 at 8:59 AM, Ersin Akinci ersin.aki...@gmail.com wrote: But you wrote that you upgraded ports from release to current. Did you upgrade your system to current too? Every time use mirrors for packages, it saves bandwidth and you can have couple of them in PKG_PATH. Quoth section 15 of the FAQ: Do NOT check out a -current ports tree and expect it to work on a -release or -stable system. This is one of the most common errors and you will irritate people when you ask for help about why nothing seems to work! D'oh! B Sorry, I misread that originally, and I had thought that it was saying that we shouldn't mix different branches of ports together, not different branches of ports and the system. B Indeed, that exactly what I've done. My apologies, a classic RTFM. You found that so no problem ;-) Now you can do rm -rf /usr/ports and then unpack ports.tar.gz for 4.8 release again -Ersin -- Ersin Y. Akinci -- ersinakinci.com What Digital Revolution? -- www.whatdigitalrevolution.com Thinking critically about digital worlds.
Re: ports not detecting packages in PKG_PATH
On Wed, Nov 10, 2010 at 1:24 PM, Paolo Aglialoro paol...@gmail.com wrote: Every time use mirrors for packages, it saves bandwidth and you can have couple of them in PKG_PATH. By which exact syntax? It's written in FAQ and in man. Use colon ( : ) for separation of entries.
Re: ports not detecting packages in PKG_PATH
You found that so no problem ;-) Now you can do rm -rf /usr/ports and then unpack ports.tar.gz for 4.8 release again I just wish there was some way to get gnash 0.88 on stable...that was really the only reason I tried to upgrade. Do the packages in current normally find themselves in the next release? I noticed that Gnash .83p4 is in 4.8 and was released to ports on June 25th, just a few months before 4.8's release...so maybe we can get the YouTube-y goodness of .88 in time for 4.9 =D?? -- Ersin Y. Akinci -- ersinakinci.com What Digital Revolution? -- www.whatdigitalrevolution.com Thinking critically about digital worlds.
Re: ports not detecting packages in PKG_PATH
On 2010-11-10, Paolo Aglialoro paol...@gmail.com wrote: Every time use mirrors for packages, it saves bandwidth and you can have couple of them in PKG_PATH. By which exact syntax? pkg_add(1) gives you the syntax, personally I don't see much advantage to listing more than one mirror there, if you use releases all mirrors should have all the files anyway, if you use snapshots you increase the chance of mismatching packages from several different builds.
Re: ports not detecting packages in PKG_PATH
Every time use mirrors for packages, it saves bandwidth and you can have couple of them in PKG_PATH. By which exact syntax?
Re: ports not detecting packages in PKG_PATH
THX to all for insight On Wed, Nov 10, 2010 at 1:48 PM, Stuart Henderson s...@spacehopper.orgwrote: On 2010-11-10, Paolo Aglialoro paol...@gmail.com wrote: Every time use mirrors for packages, it saves bandwidth and you can have couple of them in PKG_PATH. By which exact syntax? pkg_add(1) gives you the syntax, personally I don't see much advantage to listing more than one mirror there, if you use releases all mirrors should have all the files anyway, if you use snapshots you increase the chance of mismatching packages from several different builds.
Re: ports not detecting packages in PKG_PATH
On Wed, 10 Nov 2010 08:39:35 +0100 Tomas Bodzar tomas.bod...@gmail.com wrote: Sorry, I should have specified that I have FETCH_PACKAGES=Yes in /etc/mk.conf. I found when using fetch_packages I had to use make install rather than make package. Hardly a big deal, but is that expected?
Re: ports not detecting packages in PKG_PATH
On Wed, Nov 10, 2010 at 05:42:24PM +, Kevin Chadwick wrote: On Wed, 10 Nov 2010 08:39:35 +0100 Tomas Bodzar tomas.bod...@gmail.com wrote: Sorry, I should have specified that I have FETCH_PACKAGES=Yes in /etc/mk.conf. I found when using fetch_packages I had to use make install rather than make package. Hardly a big deal, but is that expected? Yes
ports not detecting packages in PKG_PATH
Hi, I recently upgraded my ports tree from 4.8 release to current, but now it's not detecting any dependency packages in my PKG_PATH. PKG_PATH is set to the main openbsd.org package site and pkg_add works perfectly fine. I did notice that I was trying to use ports earlier tonight with a different PKG_PATH set to a mirror that was apparently offline, and that's when I changed it to the master site. Is ports perhaps remembering the wrong site? Valete, Ersin -- Ersin Y. Akinci -- ersinakinci.com What Digital Revolution? -- www.whatdigitalrevolution.com Thinking critically about digital worlds.
Re: ports not detecting packages in PKG_PATH
read this first http://www.openbsd.org/faq/faq15.html ports don't use PKG_PATH, but AnonCVS for updates/upgrades. Ports are using PKG_PATH only when you set FETCH_PACKAGES see here http://www.openbsd.org/cgi-bin/man.cgi?query=portssektion=7 Sorry, I should have specified that I have FETCH_PACKAGES=Yes in /etc/mk.conf. -- Ersin Y. Akinci -- ersinakinci.com What Digital Revolution? -- www.whatdigitalrevolution.com Thinking critically about digital worlds.
Re: ports not detecting packages in PKG_PATH
On Wed, Nov 10, 2010 at 8:01 AM, Ersin Akinci ersin.aki...@gmail.com wrote: Hi, I recently upgraded my ports tree from 4.8 release to current, but now it's not detecting any dependency packages in my PKG_PATH. B PKG_PATH is set to the main openbsd.org package site and pkg_add works perfectly fine. B I did notice that I was trying to use ports earlier tonight with a different PKG_PATH set to a mirror that was apparently offline, and that's when I changed it to the master site. B Is ports perhaps remembering the wrong site? read this first http://www.openbsd.org/faq/faq15.html ports don't use PKG_PATH, but AnonCVS for updates/upgrades. Ports are using PKG_PATH only when you set FETCH_PACKAGES see here http://www.openbsd.org/cgi-bin/man.cgi?query=portssektion=7 Valete, Ersin -- Ersin Y. Akinci -- ersinakinci.com What Digital Revolution? -- www.whatdigitalrevolution.com Thinking critically about digital worlds.
Re: ports not detecting packages in PKG_PATH
On Wed, Nov 10, 2010 at 8:32 AM, Ersin Akinci ersin.aki...@gmail.com wrote: read this first http://www.openbsd.org/faq/faq15.html ports don't use PKG_PATH, but AnonCVS for updates/upgrades. Ports are using PKG_PATH only when you set FETCH_PACKAGES see here http://www.openbsd.org/cgi-bin/man.cgi?query=portssektion=7 Sorry, I should have specified that I have FETCH_PACKAGES=Yes in /etc/mk.conf. But you wrote that you upgraded ports from release to current. Did you upgrade your system to current too? Every time use mirrors for packages, it saves bandwidth and you can have couple of them in PKG_PATH. -- Ersin Y. Akinci -- ersinakinci.com What Digital Revolution? -- www.whatdigitalrevolution.com Thinking critically about digital worlds.
4.6 upgrade problem with 'pkg_add -u' and PKG_PATH
I am having trouble upgrading to 4.6. I always upgrade from a local master repository. First, from the latter I set up reverse port forwarding on the target server so that PKG_PATH=http://localhost:/ Then I do: pkg_add -v -ui -F update -F updatedepends -F alwaysupdate The error I get is: -- Error from http://localhost:/: ftp: Invalid URL (no file after host): http://localhost:/ No packages available in the PKG_PATH -- Using 'lynx http://localhost:/' I get a view of all my packages and I've been using this method for quite a few upgrades now. What's wrong? Thanks for any help. -- /jm
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
Help with PKG_PATH=
Today i was installing OpenBSD 4.5 and i type: export PKG_PATH=ftp://tp.openbsd.org/pub/OpenBSD/4.5/packages/i386/ chmod u=rwx /home PKG_CACHE=/home pkg_add k3b But when i type pkg_add k3b, is not working, and the url says ftp://tp.openbsd.org//pub/OpenBSD/4.5/packages/i386/;. Strange, isn't it? (the double //) I'ts not my fault, so i don't what what happens. Thank you very much.
Re: Help with PKG_PATH=
On Thu, May 14, 2009 at 10:41 AM, Jose Perez Rodriguez juangmgald...@gmail.com wrote: Today i was installing OpenBSD 4.5 and i type: export PKG_PATH=ftp://tp.openbsd.org/pub/OpenBSD/4.5/packages/i386/ tp.openbsd.org?
Re: Help with PKG_PATH=
On 2009-05-14, Jose Perez Rodriguez juangmgald...@gmail.com wrote: Today i was installing OpenBSD 4.5 and i type: export PKG_PATH=ftp://tp.openbsd.org/pub/OpenBSD/4.5/packages/i386/ chmod u=rwx /home PKG_CACHE=/home pkg_add k3b But when i type pkg_add k3b, is not working, and the url says ftp://tp.openbsd.org//pub/OpenBSD/4.5/packages/i386/;. Strange, isn't it? (the double //) I'ts not my fault, so i don't what what happens. Thank you very much. the double / is fixed in -current. but unless you're using a fairly strict proxy server, that's not your problem. as the other poster pointed out, the hostname is wrong, s/tp/ftp/.
Re: Help with PKG_PATH=
Hi --- On Thu, 5/14/09, Jose Perez Rodriguez juangmgald...@gmail.com wrote: From: Jose Perez Rodriguez juangmgald...@gmail.com Subject: Help with PKG_PATH= To: misc@openbsd.org Date: Thursday, May 14, 2009, 6:41 PM Today i was installing OpenBSD 4.5 and i type: export PKG_PATH=ftp://tp.openbsd.org/pub/OpenBSD/4.5/packages/i386/ chmod u=rwx /home PKG_CACHE=/home pkg_add k3b But when i type pkg_add k3b, is not working, and the url says ftp://tp.openbsd.org//pub/OpenBSD/4.5/packages/i386/;. Strange, isn't it? (the double //) I'ts not my fault, so i don't what what happens. Thank you very much. Please correct the typo in the ftp url, and delete the last slash (/) Regards.
Re: Help with PKG_PATH=
On Thu, May 14, 2009 at 11:30:52AM -0700, Francisco Valladolid Hdez. wrote: Hi --- On Thu, 5/14/09, Jose Perez Rodriguez juangmgald...@gmail.com wrote: From: Jose Perez Rodriguez juangmgald...@gmail.com Subject: Help with PKG_PATH= To: misc@openbsd.org Date: Thursday, May 14, 2009, 6:41 PM Today i was installing OpenBSD 4.5 and i type: export PKG_PATH=ftp://tp.openbsd.org/pub/OpenBSD/4.5/packages/i386/ chmod u=rwx /home PKG_CACHE=/home pkg_add k3b But when i type pkg_add k3b, is not working, and the url says ftp://tp.openbsd.org//pub/OpenBSD/4.5/packages/i386/;. Strange, isn't it? (the double //) I'ts not my fault, so i don't what what happens. Thank you very much. Please correct the typo in the ftp url, and delete the last slash (/) ^ there's no problem with that. it used to be required, even. Regards. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: Help with PKG_PATH=
On Thu, May 14, 2009 at 01:39:13PM -0700, Fortunato wrote: # pwd /root/Desktop # ls -l openbgpd-4.4.1.tgz -rw-r--r-- 1 root wheel 163070 May 13 18:08 openbgpd-4.4.1.tgz # export PKG_PATH=/root/Desktop # pkg_add openbgpd-4.4.1.tgz Can't find openbgpd-4.4.1.tgz /usr/sbin/pkg_add: openbgpd-4.4.1.tgz:Fatal error openbgpd is not a package. It's included in the base operating system (assuming you're running OpenBSD). $ which bgpd /usr/sbin/bgpd -ME
Re: Help with PKG_PATH=
On Thu, May 14, 2009 at 01:39:13PM -0700, Fortunato wrote: I'm also having a problem but with PKG_PATH: # pwd /root/Desktop # ls -l openbgpd-4.4.1.tgz -rw-r--r-- 1 root wheel 163070 May 13 18:08 openbgpd-4.4.1.tgz # export PKG_PATH=/root/Desktop # pkg_add openbgpd-4.4.1.tgz Can't find openbgpd-4.4.1.tgz /usr/sbin/pkg_add: openbgpd-4.4.1.tgz:Fatal error openbgdp-4.4.1.tgz is a source tarball, not an OpenBSD binary package (imo, adding '-op' [Openbsd Package] to the package names would be a good way to avoid this confusion, but anyway) and OpenBGPD is bgpd(8) on OpenBSD. if you want a newer version of OpenBGPD than what's in OpenBSD 4.4, it's probably easiest to upgrade to 4.5. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: Help with PKG_PATH=
Eee??? http://www.openbgpd.org/ Why are you trying something with some package?OpenBGPD is in base. And /root/Desktop ? Are you using Firefox under root?Crazy. 2009/5/14 Fortunato fortunato.montre...@earthlink.net: -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Jacob Meuser Sent: Thursday, May 14, 2009 12:48 PM To: misc@openbsd.org Subject: Re: Help with PKG_PATH= On Thu, May 14, 2009 at 11:30:52AM -0700, Francisco Valladolid Hdez. wrote: Hi --- On Thu, 5/14/09, Jose Perez Rodriguez juangmgald...@gmail.com wrote: From: Jose Perez Rodriguez juangmgald...@gmail.com Subject: Help with PKG_PATH= To: misc@openbsd.org Date: Thursday, May 14, 2009, 6:41 PM Today i was installing OpenBSD 4.5 and i type: export PKG_PATH=ftp://tp.openbsd.org/pub/OpenBSD/4.5/packages/i386/ chmod u=rwx /home PKG_CACHE=/home pkg_add k3b But when i type pkg_add k3b, is not working, and the url says ftp://tp.openbsd.org//pub/OpenBSD/4.5/packages/i386/;. Strange, isn't it? (the double //) I'ts not my fault, so i don't what what happens. Thank you very much. Please correct the typo in the ftp url, and delete the last slash (/) B B B B B B B B B B B B B B B B B B B B B B B ^ there's no problem with that. B it used to be required, even. Regards. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org Buon giorno, I'm also having a problem but with PKG_PATH: B # pwd B /root/Desktop B # ls -l openbgpd-4.4.1.tgz B -rw-r--r-- B 1 root B wheel B 163070 May 13 18:08 openbgpd-4.4.1.tgz B # export PKG_PATH=/root/Desktop B # pkg_add openbgpd-4.4.1.tgz B Can't find openbgpd-4.4.1.tgz B /usr/sbin/pkg_add: openbgpd-4.4.1.tgz:Fatal error I've also tried a direct download: B # export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/OpenBGPD B # pkg_add openbgpd-4.4.1.tgz B Error from ftp://ftp.openbsd.org//pub/OpenBSD/OpenBGPD/openbgpd-4.4.1.tgz: B ftp: Writing -: Broken pipe B Error from ftp://ftp.openbsd.org//pub/OpenBSD/OpenBGPD/openbgpd-4.4.1.tgz: B ftp: Writing -: Broken pipe B Error from ftp://ftp.openbsd.org//pub/OpenBSD/OpenBGPD/openbgpd-4.4.1.tgz: B ftp: Writing -: Broken pipe B Error from ftp://ftp.openbsd.org//pub/OpenBSD/OpenBGPD/openbgpd-4.4.1.tgz: B ftp: Writing -: Broken pipe B Error from ftp://ftp.openbsd.org//pub/OpenBSD/OpenBGPD/openbgpd-4.4.1.tgz: B ftp: Writing -: Broken pipe B Error from ftp://ftp.openbsd.org//pub/OpenBSD/OpenBGPD/openbgpd-4.4.1.tgz: B ftp: Writing -: Broken pipe B Can't find openbgpd-4.4.1.tgz B /usr/sbin/pkg_add: openbgpd-4.4.1.tgz:Fatal error B # uname -a B OpenBSD NY.tpn-af.mil 4.4 GENERIC#1021 i386 I suspect this has more to do with the actual package. Any ideas? Ciao for now, -- http://www.openbsd.org/lyrics.html
Re: Help with PKG_PATH=
Newbie slap to head - D'OH! I'm gonna have to memorize the standard package: http://www.openbsd.org/faq/faq1.html#Included Dankeschoen... -Original Message- From: Mike Erdely m...@erdelynet.com Sent: May 14, 2009 1:59 PM To: Fortunato fortunato.montre...@earthlink.net Cc: misc@openbsd.org Subject: Re: Help with PKG_PATH= On Thu, May 14, 2009 at 01:39:13PM -0700, Fortunato wrote: # pwd /root/Desktop # ls -l openbgpd-4.4.1.tgz -rw-r--r-- 1 root wheel 163070 May 13 18:08 openbgpd-4.4.1.tgz # export PKG_PATH=/root/Desktop # pkg_add openbgpd-4.4.1.tgz Can't find openbgpd-4.4.1.tgz /usr/sbin/pkg_add: openbgpd-4.4.1.tgz:Fatal error openbgpd is not a package. It's included in the base operating system (assuming you're running OpenBSD). $ which bgpd /usr/sbin/bgpd -ME
Re: Help with PKG_PATH=
It doesn't matter because it leads to error in future.You will be learned to work as root and you will often forgot use normal user account.You can trust me.I saw it many times before even with more knowledgeable people in Unix area then I'm. Dne 14. kvDten 2009 23:11 Fortunato fortunato.montre...@earthlink.net napsal(a): It's not a production system, just a sandbox. Yeah... I'm gonna have to memorize the standard packages - http://www.openbsd.org/faq/faq1.html#Included -Original Message- From: TomC!E! BodEC!r tomas.bod...@gmail.com Sent: May 14, 2009 2:08 PM To: Fortunato fortunato.montre...@earthlink.net Cc: OpenBSD-misc list misc@openbsd.org Subject: Re: Help with PKG_PATH= Eee??? http://www.openbgpd.org/ Why are you trying something with some package?OpenBGPD is in base. And /root/Desktop B ? Are you using Firefox under root?Crazy. 2009/5/14 Fortunato fortunato.montre...@earthlink.net: -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Jacob Meuser Sent: Thursday, May 14, 2009 12:48 PM To: misc@openbsd.org Subject: Re: Help with PKG_PATH= On Thu, May 14, 2009 at 11:30:52AM -0700, Francisco Valladolid Hdez. wrote: Hi --- On Thu, 5/14/09, Jose Perez Rodriguez juangmgald...@gmail.com wrote: From: Jose Perez Rodriguez juangmgald...@gmail.com Subject: Help with PKG_PATH= To: misc@openbsd.org Date: Thursday, May 14, 2009, 6:41 PM Today i was installing OpenBSD 4.5 and i type: export PKG_PATH=ftp://tp.openbsd.org/pub/OpenBSD/4.5/packages/i386/ chmod u=rwx /home PKG_CACHE=/home pkg_add k3b But when i type pkg_add k3b, is not working, and the url says ftp://tp.openbsd.org//pub/OpenBSD/4.5/packages/i386/;. Strange, isn't it? (the double //) I'ts not my fault, so i don't what what happens. Thank you very much. Please correct the typo in the ftp url, and delete the last slash (/) B B B B B B B B B B B B B B B B B B B B B B B ^ there's no problem with that. B it used to be required, even. Regards. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org Buon giorno, I'm also having a problem but with PKG_PATH: B # pwd B /root/Desktop B # ls -l openbgpd-4.4.1.tgz B -rw-r--r-- B 1 root B wheel B 163070 May 13 18:08 openbgpd-4.4.1.tgz B # export PKG_PATH=/root/Desktop B # pkg_add openbgpd-4.4.1.tgz B Can't find openbgpd-4.4.1.tgz B /usr/sbin/pkg_add: openbgpd-4.4.1.tgz:Fatal error I've also tried a direct download: B # export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/OpenBGPD B # pkg_add openbgpd-4.4.1.tgz B Error from ftp://ftp.openbsd.org//pub/OpenBSD/OpenBGPD/openbgpd-4.4.1.tgz: B ftp: Writing -: Broken pipe B Error from ftp://ftp.openbsd.org//pub/OpenBSD/OpenBGPD/openbgpd-4.4.1.tgz: B ftp: Writing -: Broken pipe B Error from ftp://ftp.openbsd.org//pub/OpenBSD/OpenBGPD/openbgpd-4.4.1.tgz: B ftp: Writing -: Broken pipe B Error from ftp://ftp.openbsd.org//pub/OpenBSD/OpenBGPD/openbgpd-4.4.1.tgz: B ftp: Writing -: Broken pipe B Error from ftp://ftp.openbsd.org//pub/OpenBSD/OpenBGPD/openbgpd-4.4.1.tgz: B ftp: Writing -: Broken pipe B Error from ftp://ftp.openbsd.org//pub/OpenBSD/OpenBGPD/openbgpd-4.4.1.tgz: B ftp: Writing -: Broken pipe B Can't find openbgpd-4.4.1.tgz B /usr/sbin/pkg_add: openbgpd-4.4.1.tgz:Fatal error B # uname -a B OpenBSD NY.tpn-af.mil 4.4 GENERIC#1021 i386 I suspect this has more to do with the actual package. Any ideas? Ciao for now, -- http://www.openbsd.org/lyrics.html -- http://www.openbsd.org/lyrics.html
Re: Help with PKG_PATH=
;-) It's nothing IT specific.People just make mistakes.Even me.But there is a possibility that someone can learn from it :-) PS:Everyone is newbie.We will be pro in coffin :-D 2009/5/14 Fortunato fortunato.montre...@earthlink.net: Newbie slap to head - D'OH! I'm gonna have to memorize the standard package: B http://www.openbsd.org/faq/faq1.html#Included Dankeschoen... -Original Message- From: Mike Erdely m...@erdelynet.com Sent: May 14, 2009 1:59 PM To: Fortunato fortunato.montre...@earthlink.net Cc: misc@openbsd.org Subject: Re: Help with PKG_PATH= On Thu, May 14, 2009 at 01:39:13PM -0700, Fortunato wrote: B # pwd B /root/Desktop B # ls -l openbgpd-4.4.1.tgz B -rw-r--r-- B 1 root B wheel B 163070 May 13 18:08 openbgpd-4.4.1.tgz B # export PKG_PATH=/root/Desktop B # pkg_add openbgpd-4.4.1.tgz B Can't find openbgpd-4.4.1.tgz B /usr/sbin/pkg_add: openbgpd-4.4.1.tgz:Fatal error openbgpd is not a package. B It's included in the base operating system (assuming you're running OpenBSD). $ which bgpd /usr/sbin/bgpd -ME -- http://www.openbsd.org/lyrics.html
Re: pkg_add adds an extra / to pkg_path
Hello, Checking on my own box (running 4.1), $PKG_PATH echoes ; ftp://ftp.stacken.kth.se/pub/OpenBSD/4.1/packages/i386/ # uname -a OpenBSD ## 4.1 GENERIC.MP#1225 i386 I have export PKG_PATH=ftp://ftp.stacken.kth.se/pub/OpenBSD/4.1/packages/i386/ Set in my .profile, and it works for me. From the error message you are getting, it seems it cannot find the host ftp.openbsd.org... Can you connect to it from a command line (i.e ftp ftp.openbsd.org)? Also, make sure that your uname -r corresponds with the version directory for the ftp path... Simon. On Tue Feb 3 8:51 , Siju George sent: Hi, I have this in my PKG_PATH variable $ echo $PKG_PATH ftp://ftp.openbsd.org/pub/OpenBSD/4.4/packages/i386/ $ When I try to update a package it shows an error $ sudo pkg_add -ui firefox3 Error from ftp://ftp.openbsd.org//pub/OpenBSD/4.4/packages/i386/: ftp: connect: Connection refused ftp: Can't connect or login to host `ftp.openbsd.org' No packages available in the PKG_PATH Looking for updates: complete Cannot find updates for esound-0.2.38v0 glitz-0.5.6p0 firefox3-3.0.1p3 nspr-4.7.1p0 desktop-file-utils-0.15 libaudiofile-0.2.6p0 nss-3.12 hicolor-icon-theme-0.10p1 png-1.2.28 sqlite3-3.5.9p0 jpeg-6bp3 glib2-2.16.4p1 tiff-3.8.2p0 atk-1.22.0 libiconv-1.12 pango-1.20.0p0 cairo-1.6.4 gettext-0.17 pcre-7.7p0 gtk+2-2.12.11 Proceed? [y/N] y $ I noticed in the line Error from ftp://ftp.openbsd.org//pub/OpenBSD/4.4/packages/i386/: there are two forward slashes after the ftp.openbsd.org part. Is that what is causing the trouble? How do I solve this? Thanks --Siju - Fe din egen, gratis e-postadresse pe Start.no
Re: pkg_add adds an extra / to pkg_path
On Tue, Feb 3, 2009 at 1:41 PM, Simen Stavdal sstav...@start.no wrote: From the error message you are getting, it seems it cannot find the host ftp.openbsd.org... Can you connect to it from a command line (i.e ftp ftp.openbsd.org)? No I was not able to. When I fixed that the update is working. Thankyou so much Simon :-)
Re: pkg_add adds an extra / to pkg_path
In gmane.os.openbsd.misc, Siju George wrote: I have this in my PKG_PATH variable $ echo $PKG_PATH ftp://ftp.openbsd.org/pub/OpenBSD/4.4/packages/i386/ $ When I try to update a package it shows an error $ sudo pkg_add -ui firefox3 Error from ftp://ftp.openbsd.org//pub/OpenBSD/4.4/packages/i386/: ftp: connect: Connection refused ftp: Can't connect or login to host `ftp.openbsd.org' ... I noticed in the line Error from ftp://ftp.openbsd.org//pub/OpenBSD/4.4/packages/i386/: there are two forward slashes after the ftp.openbsd.org part. Is that what is causing the trouble? How do I solve this? This diff removes the extra / and hasn't broken anything yet in my testing (add/update with ftp and http): Index: PackageRepository.pm === RCS file: /data/cvsroot/open/anoncvs/cvs/src/usr.sbin/pkg_add/OpenBSD/PackageRepository.pm,v retrieving revision 1.62 diff -u -p -r1.62 PackageRepository.pm --- PackageRepository.pm2 Feb 2009 20:41:47 - 1.62 +++ PackageRepository.pm3 Feb 2009 10:54:24 - @@ -394,7 +394,7 @@ sub baseurl { my $self = shift; - return //$self-{host}/$self-{path}; + return //$self-{host}$self-{path}; } sub parse_url
Re: pkg_add adds an extra / to pkg_path
On 2009-02-03, Stuart Henderson s...@spacehopper.org wrote: In gmane.os.openbsd.misc, Siju George wrote: I have this in my PKG_PATH variable $ echo $PKG_PATH ftp://ftp.openbsd.org/pub/OpenBSD/4.4/packages/i386/ $ When I try to update a package it shows an error $ sudo pkg_add -ui firefox3 Error from ftp://ftp.openbsd.org//pub/OpenBSD/4.4/packages/i386/: ftp: connect: Connection refused ftp: Can't connect or login to host `ftp.openbsd.org' ... I noticed in the line Error from ftp://ftp.openbsd.org//pub/OpenBSD/4.4/packages/i386/: there are two forward slashes after the ftp.openbsd.org part. Is that what is causing the trouble? How do I solve this? This diff removes the extra / and hasn't broken anything yet in my testing (add/update with ftp and http): ftp, http, and scp. d Index: PackageRepository.pm === RCS file: /data/cvsroot/open/anoncvs/cvs/src/usr.sbin/pkg_add/OpenBSD/PackageRepository.pm,v retrieving revision 1.62 diff -u -p -r1.62 PackageRepository.pm --- PackageRepository.pm 2 Feb 2009 20:41:47 - 1.62 +++ PackageRepository.pm 3 Feb 2009 10:54:24 - @@ -394,7 +394,7 @@ sub baseurl { my $self = shift; - return //$self-{host}/$self-{path}; + return //$self-{host}$self-{path}; } sub parse_url
Re: pkg_add adds an extra / to pkg_path
On 2/3/09, Stuart Henderson s...@spacehopper.org wrote: This diff removes the extra / and hasn't broken anything yet in my testing (add/update with ftp and http): Hi, This Diff failed to apply. Hmm... Looks like a unified diff to me... The text leading up to this was: -- |Index: PackageRepository.pm |=== |RCS file: /data/cvsroot/open/anoncvs/cvs/src/usr.sbin/pkg_add/OpenBSD/PackageRepository.pm,v |retrieving revision 1.62 |diff -u -p -r1.62 PackageRepository.pm |--- PackageRepository.pm2 Feb 2009 20:41:47 - 1.62 |+++ PackageRepository.pm3 Feb 2009 10:54:24 - -- Patching file PackageRepository.pm using Plan A... Hunk #1 failed at 394. 1 out of 1 hunks failed--saving rejects to PackageRepository.pm.rej done # cat PackageRepository.pm.rej @@ -394,7 +394,7 @@ { my $self = shift; - return //$self-{host}/$self-{path}; + return //$self-{host}$self-{path}; } sub parse_url # What did I do Wrong? The command I Issued was # pwd /usr/src/usr.sbin/pkg_add/OpenBSD # patch PackageRepository.pm /var/software/patches/PackageRepository.pm Thanks Siju Index: PackageRepository.pm === RCS file: /data/cvsroot/open/anoncvs/cvs/src/usr.sbin/pkg_add/OpenBSD/PackageRepository.pm,v retrieving revision 1.62 diff -u -p -r1.62 PackageRepository.pm --- PackageRepository.pm2 Feb 2009 20:41:47 - 1.62 +++ PackageRepository.pm3 Feb 2009 10:54:24 - @@ -394,7 +394,7 @@ sub baseurl { my $self = shift; - return //$self-{host}/$self-{path}; + return //$self-{host}$self-{path}; } sub parse_url
Re: pkg_add adds an extra / to pkg_path
On Tue, 3 Feb 2009 19:28:36 +0530 Siju George sgeorge...@gmail.com wrote: What did I do Wrong? The command I Issued was # pwd /usr/src/usr.sbin/pkg_add/OpenBSD # patch PackageRepository.pm /var/software/patches/PackageRepository.pm # man diff # man patch # cd /usr/src/usr.sbin/pkg_add/OpenBSD # patch -p0 /var/software/patches/PackageRepository.pm ^if that is the file where you saved the diff ^-p0 won't work for every diff you might encounter