Finally getting a chance to look at this again, and I had a couple of questions.
One, am I right that cvs co and cvs get are basically the same thing? (get, per http://www.openbsd.org/anoncvs.html , and co, per http://www.openbsd.org/faq/faq5.html#Bld .) The other, assuming that the last package showing update (U) before the broken pipe is now something like x11/xfce4, would it make sense to, with the current working directory still at /usr, issue sudo cvs -d$CVSROOT co -P ports/x11 or cvs -qd anon...@anoncvs.jp.openbsd.org:/cvs get -P ports/x11 just to be really, really, paranoid sure? (Noting that xmris now seems to be gone). Oh, BTW, the output of the command Ingo suggested, find /usr/ports -name pobj -prune -o -type d -empty -print is empty. (Thanks, Ingo, now I need to dig around and see if I can find where I read about files named pobj again.) -- Joel Rees On Mon, Aug 18, 2014 at 9:01 PM, Ingo Schwarze <schwa...@usta.de> wrote: > Hi Joel, > > Joel Rees wrote on Mon, Aug 18, 2014 at 08:27:23PM +0900: > > > $ date > > Mon Aug 18 19:09:34 JST 2014 > > $ sudo cvs -d$CVSROOT co -P ports > > Unrelated: > There is no need to check out the source trees as root. > Just chmod -R the whole things to a regular user account > (for example your own) and use that account for updating > and building in the future. > > > Password: > > cvs server: Updating ports > > ... > > cvs server: Updating ports/x11/yeahlaunch/pkg > > cvs server: Updating ports/xmris > > cvs server: Updating ports/xmris/files > > cvs server: Updating ports/xmris/patches > > cvs server: Updating ports/xmris/pkg > > cvs server: Updating ports/xmris/scripts > > ----------------------------- > > (stalls here for more than fifteen minutes while the disks are very > > busy doing something on the laptop. ps wwaux doesn't show anything > > that catches my eye, just the normal stuff, with the cvs command and > > the ssh session associated with it. Finally, it looks like it times > > out.) > > It doesn't sound like anything is wrong here, that seems completely > normal behaviour. What is does is create all the directories that > have ever existed in the ports tree and update them to HEAD state. > After that, it goes through the whole tree again, pruning empty > directories, that is, those that were created in the past but no > longer contain any files in HEAD. It is completely normal for that > to take considerable time and do considerable I/O, that's not a > stall. The ports tree is a big beast. > > By the way, ports/xmris never made any sense, it was an accidental > bogus commit as you can see here: > > http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/xmris/Attic/Makefile > > It just happens to be the (alphabetically) last directory below ports, > after which the pruning starts. > > Did you try *using* your checkout? > I don't see why it shouldn't work. > > > ----------------------------- > > Write failed: Broken pipe > > That is slightly strange, not sure what is going on here. But at > the worst, that might cause some empty directories being left in your > tree, which likely won't hurt. Can you please show the result of: > > find /usr/ports -name pobj -prune -o -type d -empty -print > > Yours, > Ingo
