Re: Updating ports from CVS question

2014-11-09 Thread Stuart Henderson
On 2014-11-07, Steve Williams st...@williamsitconsulting.com wrote:

 Having the ports.tar.gz that corresponds to the snapshot you install is 
 nice because 2 months down the road you can compile/install something 
 that will work on your system even when there is no package available 
 that will work on your system.

 If you try to cvs up your ports to -current 2 months after installing a 
 snapshot, odds are that something won't compile. OpenBSD works FANTASTIC 
 as long as you keep things consistent. Follow base, -current, or 
 snapshots.  Don't try to mix and match and you should have smooth sailing.

You can always cvs up -D 2014/10/01 or similar ... I don't think
I ever used ports.tar.gz. But then, if I'm running -current and packages
don't install, I usually take that as a cue to spend 10 minutes or so
updating the system and packages ;)



Updating ports from CVS question

2014-11-07 Thread Jungle Boogie

Hello All,

# uname -a
OpenBSD jackknife.my.domain 5.6 GENERIC.MP#0 i386

This system should be -current as of last night.

I'm trying to build ports:
# cd /usr
# cvs -qd anon...@anoncvs.usa.openbsd.org:/cvs get -rOPENBSD_`uname -r | sed 
's/\./_/'` -P ports


Problem is that I got impatient and thought ports were hanging somewhere 
around the x11 stuff so I stupidly ^C


Now after rebooting the machine several times, I cannot connect back to 
anoncvs.usa.openbsd.org and the other mirrors don't do much. Meaning I can 
connect but no other message indicates ports are being downloaded.


For awhile the error message was that my IP address has a connection already 
but now it looks like the connection is dropped altogether as there's no message.


Although, I can open a telnet connection to the cvs port:
telnet anoncvs.usa.openbsd.org 2401
Trying 149.20.54.217...
Connected to anoncvs.usa.openbsd.org.
Escape character is '^]'.

cvs [pserver aborted]: bad auth protocol start:

Connection closed by foreign host.

Any recommendations on what to do?

--
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si



Re: Updating ports from CVS question

2014-11-07 Thread Steve Williams

Hi,

It is 1000 times faster (or some value... but wayyy faster)  to just ftp 
the ports.tar.gz file over when compared to using CVS.


Just saying...

Cheers,
Steve Williams

On 11/7/2014 8:47 AM, Jungle Boogie wrote:

Hello All,

# uname -a
OpenBSD jackknife.my.domain 5.6 GENERIC.MP#0 i386

This system should be -current as of last night.

I'm trying to build ports:
# cd /usr
# cvs -qd anon...@anoncvs.usa.openbsd.org:/cvs get -rOPENBSD_`uname -r 
| sed 's/\./_/'` -P ports


Problem is that I got impatient and thought ports were hanging 
somewhere around the x11 stuff so I stupidly ^C


Now after rebooting the machine several times, I cannot connect back 
to anoncvs.usa.openbsd.org and the other mirrors don't do much. 
Meaning I can connect but no other message indicates ports are being 
downloaded.


For awhile the error message was that my IP address has a connection 
already but now it looks like the connection is dropped altogether as 
there's no message.


Although, I can open a telnet connection to the cvs port:
telnet anoncvs.usa.openbsd.org 2401
Trying 149.20.54.217...
Connected to anoncvs.usa.openbsd.org.
Escape character is '^]'.

cvs [pserver aborted]: bad auth protocol start:

Connection closed by foreign host.

Any recommendations on what to do?




Re: Updating ports from CVS question

2014-11-07 Thread Jungle Boogie

Dear Steve,

From: Steve Williams st...@williamsitconsulting.com
Sent:  Fri, 07 Nov 2014 09:11:51 -0700
To: misc@openbsd.org
Subject: Re: Updating ports from CVS question


Hi,

It is 1000 times faster (or some value... but wayyy faster)  to just ftp the
ports.tar.gz file over when compared to using CVS.



Great idea! How do you update your ports, then? Just download a new 
ports.tar.gz file or:

# cd /usr/ports
# cvs -d anon...@anoncvs.usa.openbsd.org:/cvs -q up -rOPENBSD_`uname -r | sed 
's/\./_/'` -Pd




Just saying...

Cheers,
Steve Williams




--
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si



Re: Updating ports from CVS question

2014-11-07 Thread Ingo Schwarze
Jungle Boogie wrote on Fri, Nov 07, 2014 at 08:20:36AM -0800:

 Great idea! How do you update your ports, then?
 Just download a new ports.tar.gz file

If you are running -stable, that doesn't help.
The file ports.tar.gz doesn't get updated for -stable after release.

 or:
 # cd /usr/ports
 # cvs -d anon...@anoncvs.usa.openbsd.org:/cvs -q up -rOPENBSD_`uname
 -r | sed 's/\./_/'` -Pd

Yes, you start from ports.tar.gz, and then, you update that tree
with cvs(1) as needed.

I don't like your uname(1) hackery, though.  It's unsafe, giving you
a false sense of security.  For example, i'm running -current, but
your uname(1) says, on my -current machine:

   $ uname -r | sed 's/\./_/'
  5_6
   $ uname -a
  OpenBSD isnote.usta.de 5.6 GENERIC.MP#5 i386

To update my ports tree, i have to do:

   $ cd /usr/ports  cvs -d ... up -dP

without any -r argument, but your uname(1) would give me a bogus -r
argument, so in some situations, it does the wrong thing.

I'd recommend that you just supply the correct -r by hand if needed.

KISS!

Yours,
  Ingo



Re: Updating ports from CVS question

2014-11-07 Thread Stuart Henderson
On 2014-11-07, Jungle Boogie jungleboog...@gmail.com wrote:
 Hello All,

 # uname -a
 OpenBSD jackknife.my.domain 5.6 GENERIC.MP#0 i386

 This system should be -current as of last night.

 I'm trying to build ports:
 # cd /usr
 # cvs -qd anon...@anoncvs.usa.openbsd.org:/cvs get -rOPENBSD_`uname -r | sed 
 's/\./_/'` -P ports

 Problem is that I got impatient and thought ports were hanging somewhere 
 around the x11 stuff so I stupidly ^C

 Now after rebooting the machine several times, I cannot connect back to 
 anoncvs.usa.openbsd.org and the other mirrors don't do much. Meaning I can 
 connect but no other message indicates ports are being downloaded.

If you have already fetched most of the tree, you will have to wait a
while before you start seeing any additional output from cvs.

If you are getting impatient, you can watch it change directory as
it does stuff:

pkg_add gnuwatch; gnuwatch --interval=0.5 ps -Ocwd | grep [c]vs



Re: Updating ports from CVS question

2014-11-07 Thread Jungle Boogie

Dear Ingo, Misc

From: Ingo Schwarze schwa...@usta.de
Sent:  Fri, 7 Nov 2014 19:18:08 +0100
To: Jungle Boogie Cc: misc@openbsd.org
Subject: Re: Updating ports from CVS question


Jungle Boogie wrote on Fri, Nov 07, 2014 at 08:20:36AM -0800:


Great idea! How do you update your ports, then?
Just download a new ports.tar.gz file


If you are running -stable, that doesn't help.
The file ports.tar.gz doesn't get updated for -stable after release.


or:
# cd /usr/ports
# cvs -d anon...@anoncvs.usa.openbsd.org:/cvs -q up -rOPENBSD_`uname
-r | sed 's/\./_/'` -Pd


Yes, you start from ports.tar.gz, and then, you update that tree
with cvs(1) as needed.

I don't like your uname(1) hackery, though.  It's unsafe, giving you
a false sense of security.  For example, i'm running -current, but
your uname(1) says, on my -current machine:

$ uname -r | sed 's/\./_/'
   5_6
$ uname -a
   OpenBSD isnote.usta.de 5.6 GENERIC.MP#5 i386


I followed directions here:
http://www.bsdnow.tv/tutorials/stable-current-obsd

I did skip one reboot, though.

Also, I went from 5.6 -release to -current and now looking at the directions, 
following a snapshot is recommended. I would expect my uname to update, though.





To update my ports tree, i have to do:

$ cd /usr/ports  cvs -d ... up -dP

without any -r argument, but your uname(1) would give me a bogus -r
argument, so in some situations, it does the wrong thing.

I'd recommend that you just supply the correct -r by hand if needed.


I think I'll rebuild the machine based on a snapshot THEN update to -current!



KISS!

Yours,
   Ingo





--
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si



Re: Updating ports from CVS question

2014-11-07 Thread Steve Williams
On 11/7/2014 1:37 PM, Jungle Boogie wrote:
 Dear Ingo, Misc
 
 From: Ingo Schwarze schwa...@usta.de
 Sent:  Fri, 7 Nov 2014 19:18:08 +0100
 To: Jungle Boogie Cc: misc@openbsd.org
 Subject: Re: Updating ports from CVS question
 
 Jungle Boogie wrote on Fri, Nov 07, 2014 at 08:20:36AM -0800:

 Great idea! How do you update your ports, then?
 Just download a new ports.tar.gz file

 If you are running -stable, that doesn't help.
 The file ports.tar.gz doesn't get updated for -stable after release.

 or:
 # cd /usr/ports
 # cvs -d anon...@anoncvs.usa.openbsd.org:/cvs -q up -rOPENBSD_`uname
 -r | sed 's/\./_/'` -Pd

 Yes, you start from ports.tar.gz, and then, you update that tree
 with cvs(1) as needed.

 I don't like your uname(1) hackery, though.  It's unsafe, giving you
 a false sense of security.  For example, i'm running -current, but
 your uname(1) says, on my -current machine:

 $ uname -r | sed 's/\./_/'
5_6
 $ uname -a
OpenBSD isnote.usta.de 5.6 GENERIC.MP#5 i386

 I followed directions here:
 http://www.bsdnow.tv/tutorials/stable-current-obsd

 I did skip one reboot, though.

 Also, I went from 5.6 -release to -current and now looking at the 
 directions, following a snapshot is recommended. I would expect my 
 uname to update, though.



 To update my ports tree, i have to do:

 $ cd /usr/ports  cvs -d ... up -dP

 without any -r argument, but your uname(1) would give me a bogus -r
 argument, so in some situations, it does the wrong thing.

 I'd recommend that you just supply the correct -r by hand if needed.

 I think I'll rebuild the machine based on a snapshot THEN update to 
 -current!


 KISS!

 Yours,
Ingo




Hi,

It has been stated multiple times on this list that snapshots do not 
necessarily equate to -current.  I think it's generally in reference to 
the base system and not ports, but it is something to be aware of.

From: http://www.openbsd.org/faq/faq5.html
Third, snapshots often contain experimental code that isn't yet 
committed to the tree.

It has been my experience that if you want to follow snapshots, then it 
is best to download the ports.tar.gz at the time that you install the 
snapshot.  This has the greatest chance of success (though not 
guaranteed), as the cvs and the snapshot can be out of date.  For 
example, a snapshot may be complied on Monday, you download it on 
Thursday, and in the meantime, someone has updated a port in CVS. It's 
only bitten me a couple of times in the last 10 years, but when it does, 
it really sucks.  What you think should be a 5 minute operation turns 
into a system upgrade!  lol

Using ports and snapshots (rather than packages) can be quite resource 
intensive.  For giggles,yesterday I compiled a few ports that I normally 
use packages for (I wanted to test my VM, as well as see what it took to 
compile mariadb).  To compile, the dependencies for 2 of the packages I 
usually install pulled (ftp/compile) around 100 packages.  I ended up with
 5 versions of autoconf
 2 versions of automake
and TONS of things I would not normally install...

Having the ports.tar.gz that corresponds to the snapshot you install is 
nice because 2 months down the road you can compile/install something 
that will work on your system even when there is no package available 
that will work on your system.

If you try to cvs up your ports to -current 2 months after installing a 
snapshot, odds are that something won't compile. OpenBSD works FANTASTIC 
as long as you keep things consistent. Follow base, -current, or 
snapshots.  Don't try to mix and match and you should have smooth sailing.

That's just been my personal experience.  Other people way more 
authoritative may have much wiser advice.

Cheers,
Steve Williams