bsd-lists at hush.com
2013-Jul-06 03:38 UTC
When will subversion be ready for updating/upgrading src && ports?
Greetings, Well after posting a couple of questions to the list regarding questions I had before migrating from (cv)sup to subversion, I took the leap: mv /usr/src/ /usr/src.old/ mkdir /usr/src mv /usr/ports/ /usr/ports.old/ mkdir /usr/ports rm -fr /var/db/sup/* rm -fr /var/db/portsnap/* svn checkout svn://svn.freebsd.org/base/stable/8 /usr/src svn checkout svn://svn.freebsd.org/ports/head /usr/ports I then performed a portmaster -a which left me with a non-working X desktop. Turned out to be a problem with the Nvidia driver -- was 2.9.40, now 3.10.14. But loading it in loader.conf didn't create /dev/nvidia0, or /dev/nvidiactl To make a long story short, I attempted to update my src && ports, and try agaiin; svn update svn://svn.freebsd.org/ports/head /usr/ports FAILED! I don't have the exact output So I tried: cd /usr/ports svn update Which replied: svn: E155036: Please see the 'svn upgrade' command svn: E155036: The working copy at '/usr/ports' is too old (format 29) to work with client version '1.8.0 (r1490375)' (expects f ormat 31). You need to upgrade the working copy first. So I guess subversion isn't (yet) designed for this sort of stuff, which leaves me with a useless box. :( Thank you for all your time, and consideration. --chris
Jeremy Chadwick
2013-Jul-06 03:44 UTC
When will subversion be ready for updating/upgrading src && ports?
On Fri, Jul 05, 2013 at 08:38:07PM -0700, bsd-lists at hush.com wrote:> Greetings, > Well after posting a couple of questions to the list regarding questions I had before > migrating from (cv)sup to subversion, I took the leap: > > mv /usr/src/ /usr/src.old/ > > mkdir /usr/src > > mv /usr/ports/ /usr/ports.old/ > > mkdir /usr/ports > > rm -fr /var/db/sup/* > rm -fr /var/db/portsnap/* > > svn checkout svn://svn.freebsd.org/base/stable/8 /usr/src > > svn checkout svn://svn.freebsd.org/ports/head /usr/ports > > I then performed a portmaster -a > > which left me with a non-working X desktop. > Turned out to be a problem with the Nvidia driver -- was 2.9.40, now 3.10.14. > But loading it in loader.conf didn't create /dev/nvidia0, or /dev/nvidiactl > To make a long story short, I attempted to update my src && ports, and try agaiin; > > svn update svn://svn.freebsd.org/ports/head /usr/ports > FAILED! I don't have the exact outputIncorrect syntax -- should be one of the following (your choice): cd /usr/ports && svn update svn update /usr/ports> So I tried: > cd /usr/ports > svn update > Which replied: > svn: E155036: Please see the 'svn upgrade' command > svn: E155036: The working copy at '/usr/ports' > is too old (format 29) to work with client version '1.8.0 (r1490375)' (expects f > ormat 31). You need to upgrade the working copy first. > > So I guess subversion isn't (yet) designed for this sort of stuff, which leaves me with a useless box. :(Incorrect. Please look very, VERY closely at what the command is that it's telling you to use. Read it 4 times over. Pay close attention. The explanation: You installed subversion 1.7 or earlier when you originally started (i.e. subversion-1.7 or 1.6 or something else was installed). No problem. You then updated your ports tree. No problem. You then ran portmaster -a to upgrade/update all your ports (rebuild them). No problem. However this updated subversion to the latest in ports, which is 1.8. The subversion metadata (stored in the .svn directories, ex. /usr/src/.svn, /usr/ports/.svn, etc.) has changed as of 1.8. This is why you need to do "svn upgrade" in those directories. This is a one-time thing you have to do. That's all. -- | Jeremy Chadwick jdc at koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB |
Erich Dollansky
2013-Jul-06 03:55 UTC
When will subversion be ready for updating/upgrading src && ports?
Hi, On Fri, 05 Jul 2013 20:38:07 -0700 bsd-lists at hush.com wrote:> Greetings, > Well after posting a couple of questions to the list regarding > questions I had before migrating from (cv)sup to subversion, I took > the leap: > > mv /usr/src/ /usr/src.old/ > > mkdir /usr/src > > mv /usr/ports/ /usr/ports.old/ > > mkdir /usr/ports > > rm -fr /var/db/sup/* > rm -fr /var/db/portsnap/* > > svn checkout svn://svn.freebsd.org/base/stable/8 /usr/src > > svn checkout svn://svn.freebsd.org/ports/head /usr/ports > > I then performed a portmaster -a > > which left me with a non-working X desktop. > Turned out to be a problem with the Nvidia driver -- was 2.9.40, now > 3.10.14. But loading it in loader.conf didn't create /dev/nvidia0, > or /dev/nvidiactl To make a long story short, I attempted to update > my src && ports, and try agaiin; > > svn update svn://svn.freebsd.org/ports/head /usr/ports > FAILED! I don't have the exact output > So I tried: > cd /usr/ports > svn update > Which replied: > svn: E155036: Please see the 'svn upgrade' command > svn: E155036: The working copy at '/usr/ports' > is too old (format 29) to work with client version '1.8.0 > (r1490375)' (expects f ormat 31). You need to upgrade the working > copy first.you need a big pipe for svn. I also do not understand why a program is not able to handle a format change automatically.> > So I guess subversion isn't (yet) designed for this sort of stuff, > which leaves me with a useless box. :(What did I say a long time ago? It takes time to get this up but not a cut-off date. Erich> > Thank you for all your time, and consideration. > > --chris > > _______________________________________________ > freebsd-stable at freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe at freebsd.org"
David Wolfskill
2013-Jul-06 04:00 UTC
When will subversion be ready for updating/upgrading src && ports?
On Fri, Jul 05, 2013 at 08:38:07PM -0700, bsd-lists at hush.com wrote:> ... > svn checkout svn://svn.freebsd.org/ports/head /usr/ports > > I then performed a portmaster -aPrior to updating installed ports, review of ports/UPDATING is more than just a good idea.> which left me with a non-working X desktop. > Turned out to be a problem with the Nvidia driver -- was 2.9.40, now 3.10.14. > But loading it in loader.conf didn't create /dev/nvidia0, or /dev/nvidiactlI am using nvidia-driver-310.44_1 successfully.> To make a long story short, I attempted to update my src && ports, and try agaiin; > > svn update svn://svn.freebsd.org/ports/head /usr/ports > FAILED! I don't have the exact outputIs /usr/ports a real directly, or a symlink? (In my case, it is a symlink, so I needed to take a bit of evasive action after I updated svn to 1.8.)> So I tried: > cd /usr/ports > svn update > Which replied: > svn: E155036: Please see the 'svn upgrade' command > svn: E155036: The working copy at '/usr/ports' > is too old (format 29) to work with client version '1.8.0 (r1490375)' (expects f > ormat 31). You need to upgrade the working copy first. > > So I guess subversion isn't (yet) designed for this sort of stuff,That's a fairly classic non sequitur. I only have logs for the last year of using SVN to perform 2 update/build/smoke-test cycles/day for each of a couple of machines -- 1 set for stable/9; the other for head. I also update the installed ports under stable/9 (daily). (The two machines are my laptop and a "build machine.") And then I actually use the resulting stable/9 snapshot on my laptop for day-to-day activities -- until the next day, when it's "lather, rinse, repeat." Then there are few machines I only update weekly. Regarding the "svn: E155036: Please see the 'svn upgrade' command ..." message, that means that because you updated svn (probably from 1.7 to 1.8), you need to use the "svn upgrade" command on your previously-created working copies in order to use the new svn command on them.> which leaves me with a useless box. :( > > Thank you for all your time, and consideration.Always set things up so you have a usable fallback. Whether that's by making backups and restoring from them or some other mechanism, that's up to you. (I tend to set machines up to be able to boot from multiple slices, which can be a suitable strategy, but it's certainly not as easy as falling off a log.) You may see my more recent update history on an assortment of machines at <http://www.catwhisker.org/~david/FreeBSD/history/>. 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/20130705/76f702f1/attachment.sig>