Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 23 Apr 2014 11:41:02 +0000 (UTC)
From:      "Thomas Mueller" <mueller6724@bellsouth.net>
To:        freebsd-ports@freebsd.org 
Subject:   Re: Subversion can't update ports tree: bug somewhere?
Message-ID:  <309716.11151.bm@smtp116.sbc.mail.bf1.yahoo.com>
References:  <876212.25244.bm@smtp113.sbc.mail.ne1.yahoo.com> <20140422131101.GO1321@albert.catwhisker.org> <53566F1D.20401@gwdg.de>

next in thread | previous in thread | raw e-mail | index | archive | help
from David Wolfskill:

> Hmm....  Well, as a reality check:
        
> g1-252(9.2-S)[1] ls -lTiao /usr/ports/x11/libxcb/files/patch-64bit-packed
> 8353468 -rw-r--r--  1 cvsupin  cvsupin  - 3923 Apr 17 03:57:07 2014 /usr/ports/x11/libxcb/files/patch-64bit-packed
> g1-252(9.2-S)[2] uname -a
> FreeBSD g1-252.catwhisker.org 9.2-STABLE FreeBSD 9.2-STABLE #721  r264748M/264752:902511: Tue Apr 22 04:44:32 PDT 2014
> root@g1-252.catwhisker.org:/usr/obj/usr/src/sys/CANARY  i386
> g1-252(9.2-S)[3] date
> Tue Apr 22 06:07:34 PDT 2014
g1-252(9.2-S)[4]

> What happens if you:

> cd /usr/ports/x11/libxcb/files && svn revert patch-64bit-packed
        
?

> If that fails, you might try:

> cd /usr/ports/x11/libxcb && rm -fr files && svn up files

> Oh -- further stage in the reality check:

> g1-252(9.2-S)[4] svn info /usr/ports/
> Path: /usr/ports
> Working Copy Root Path: /usr/ports
> URL: file:///svn/freebsd/ports/head
> Relative URL: ^/head
> Repository Root: file:///svn/freebsd/ports
> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
> Revision: 351803
> Node Kind: directory
> Schedule: normal
> Last Changed Author: bapt
> Last Changed Rev: 351803
> Last Changed Date: 2014-04-22 03:29:18 -0700 (Tue, 22 Apr 2014)
 
> g1-252(9.2-S)[5]
 
> (I use a private mirror of the repo.  This is on my laptop; I like
> having a repo handy even if I'm commuting on the train & thus offline.)

> Where is your repo?

I tried the first suggestion, and it worked, and I didn't have to go deeper.

Not being really familiar with the inner workings of subversion, I wouldn't have thought of that fix.

I mentioned running svn from both NetBSD and FreeBSD, so it was from NetBSD pkgsrc and FreeBSD ports.

Repo was from svn://svn.freebsd.org .

from Rainer Hurling:

> It is unlikely, but did you try 'svn upgrade' and after it 'svn update'?

No, I didn't: thought that was for upgrading subversion from 1.6.x to 1.7.x or 1.8.x or from 1.7.x to 1.8.x, not needed when upgrading from 1.8.x to a newer release within 1.8.* .
                
Tom




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?309716.11151.bm>