I've been using svn updates for some time with no problems rebuilding
daily.
Version of my last successful update.
# uname -a
FreeBSD home.encontacto.net 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #503
r252026: Thu Jun 20 06:41:28 CDT 2013
root at home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO
amd64
# cd /usr/src && svn up /usr/src
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: The working copy at '/usr/src'
is too old (format 29) to work with client version '1.8.0 (r1490375)'
(expects format 31). You need to upgrade the working copy first.
# cd /usr/ports && /usr/local/bin/svn up /usr/ports
Updating '.':
svn: E170000: Unrecognized URL scheme for '
https://svn0.us-west.freebsd.org/ports/head'
Today was the first day that I have seen this. The error message leads me
to believe that I am out of date but have tried to find a way to upgrade
and haven't been successful.
The ports versions have not changed for svn didn't update them today. Maybe
I should update differently?
Thanks,
ed
-------------------------------------------------------------------------------------------------
--
Bienes Ra?ces in Coatepec, Veracruz, Mexico
http://www.facebook.com/pages/Inmobiliaria-Bienes-Raices-httpEcoManiainfo/102249989850215?sk=photos_albums
On Fri, Jun 21, 2013 at 05:45:42PM -0500, Edwin L. Culp W. wrote:> I've been using svn updates for some time with no problems rebuilding > daily. > > Version of my last successful update. > # uname -a > FreeBSD home.encontacto.net 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #503 > r252026: Thu Jun 20 06:41:28 CDT 2013 > root at home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO > amd64 > > # cd /usr/src && svn up /usr/src > svn: E155036: Please see the 'svn upgrade' command > svn: E155036: The working copy at '/usr/src' > is too old (format 29) to work with client version '1.8.0 (r1490375)' > (expects format 31). You need to upgrade the working copy first.You need to do as the above message suggests: "svn upgrade /usr/src". (Note that "svn up" is short for "svn update", which is different from "svn upgrade".) This is a result of the svn client (now) being 1.8.x, vs. the last successful "svn up", when it was 1.7.x.> # cd /usr/ports && /usr/local/bin/svn up /usr/ports > Updating '.': > svn: E170000: Unrecognized URL scheme for ' > https://svn0.us-west.freebsd.org/ports/head'This is likely an issue of the new 1.8.x svn client not being built with SERF support. Please see ports/UPDATING, entry 20130619.> ...Peace, david -- David H. Wolfskill david at catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20130621/259b83aa/attachment.sig>
Thanks, David. I'm still not able to update my ports. I was able to build a new world with no problem. # uname -a FreeBSD home.encontacto.net 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #505 r252094: Sat Jun 22 06:48:06 CDT 2013 root at home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO amd64 but when I try to update my ports I get: # /usr/local/bin/svn up /usr/ports Updating '/usr/ports': svn: E170000: Unrecognized URL scheme for ' https://svn0.us-west.freebsd.org/ports/head' And I though I was finally using svn without problems. The only thing interesting about this error was it's needing neon that I rebuilt and reinstalled just in case but no prize. Thanks for suggestions. ed -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 203 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20130622/4965ba60/attachment.sig>