[N8VEM: 15987] transition to new subversion server for RomWBW, FdTst, and XModem (please read)

[Douglas Goodall]

Friends,

The migration is complete off the old server, onto a new and
much higher powered server, with a fatter pipe to the Internet.

Our thanks to Wayne for the migration and continued admin
of the subversion system provided for B8VEM use.

The new subversion URL's are now...

svn co svn://ichibrosan.com/RomWBW

svn co svn://ichibrosan.com/FdTst

svn co svn://ichibrosan.com/XModem

Have fun...

Douglas Goodall

p.s. ichibrosan.com is my new domain that replaces goodall.com
which I recently sold as part of my old company.

---http://www.linkedin.com/in/douglasgoodall

[Wayne Warthen]

Thanks for continued support hosting this service Douglas.

For those of you using the TortoiseSVN, it is very easy to convert to the
new server. Just right click on the working directory, choose TortoiseSVN,
then Relocate... In the dialog box you see, just change the "To URL" from "
svn://server.goodall.com/RomWBW" to "svn://ichibrosan.com/RomWBW", and
click OK.

That's it. You should be able to use the update function to retrieve the
latest source code.

Thanks,

Wayne

[Bill Lewis]

Thanks Douglas and Wayne. SVN Relocate worked fine.

Bill

Post by Wayne Warthen
Thanks for continued support hosting this service Douglas.
For those of you using the TortoiseSVN, it is very easy to convert to the
new server. Just right click on the working directory, choose TortoiseSVN,
then Relocate... In the dialog box you see, just change the "To URL" from "
svn://server.goodall.com/RomWBW" to "svn://ichibrosan.com/RomWBW", and
click OK.
That's it. You should be able to use the update function to retrieve the
latest source code.
Thanks,
Wayne

[Earl Baugh]

Doug,

Quick question, I'm trying to check out "Release" which I had checked
out before /tags/Release, but that doesn't seem to exist any more.
That just a hiccup on the migration?

Also, for some reason I had a link to what I thought was the code for
the firmware of the S2I board... but that also seems to be broken
(but then again, I don't recall if I had actually gotten that to
work... but I had seen it somewhere...)

Anyway, just wondering.

Earl

On Thu, Jun 20, 2013 at 10:46 PM, Douglas Goodall

Post by Douglas Goodall
Friends,
The migration is complete off the old server, onto a new and
much higher powered server, with a fatter pipe to the Internet.
Our thanks to Wayne for the migration and continued admin
of the subversion system provided for B8VEM use.
The new subversion URL's are now...
svn co svn://ichibrosan.com/RomWBW
svn co svn://ichibrosan.com/FdTst
svn co svn://ichibrosan.com/XModem
Have fun...
Douglas Goodall
p.s. ichibrosan.com is my new domain that replaces goodall.com
which I recently sold as part of my old company.
---http://www.linkedin.com/in/douglasgoodall
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/groups/opt_out.

[Wayne Warthen]

Hi Earl,

The missing "Release" branch was just a temporary issue due to the new
release of RomWBW. I removed it and forgot to put it back pointing to the
latest release. I have corrected this problem and it back now.

Regarding S2I, that repostory was just a test repository. It did not
contain the latest code. I removed it as part of the server migration
because it did not have current source code. The current source code is
available on the Wiki. I will put S2I back in the repository in the near
future though.

Thanks,

Wayne

Post by Earl Baugh
Doug,
Quick question, I'm trying to check out "Release" which I had checked
out before /tags/Release, but that doesn't seem to exist any more.
That just a hiccup on the migration?
Also, for some reason I had a link to what I thought was the code for
the firmware of the S2I board... but that also seems to be broken
(but then again, I don't recall if I had actually gotten that to
work... but I had seen it somewhere...)
Anyway, just wondering.
Earl
On Thu, Jun 20, 2013 at 10:46 PM, Douglas Goodall

Post by Douglas Goodall
Friends,
The migration is complete off the old server, onto a new and
much higher powered server, with a fatter pipe to the Internet.
Our thanks to Wayne for the migration and continued admin
of the subversion system provided for B8VEM use.
The new subversion URL's are now...
svn co svn://ichibrosan.com/RomWBW
svn co svn://ichibrosan.com/FdTst
svn co svn://ichibrosan.com/XModem
Have fun...
Douglas Goodall
p.s. ichibrosan.com is my new domain that replaces goodall.com
which I recently sold as part of my old company.
---http://www.linkedin.com/in/douglasgoodall
--
You received this message because you are subscribed to the Google

Groups

Post by Douglas Goodall
"N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send

an

Post by Douglas Goodall
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/groups/opt_out.

[Earl Baugh]

Thanks for the clarification... makes me feel better that I wasn't
imagining stuff :-)

Earl

Post by Wayne Warthen
Hi Earl,
The missing "Release" branch was just a temporary issue due to the new
release of RomWBW. I removed it and forgot to put it back pointing to the
latest release. I have corrected this problem and it back now.
Regarding S2I, that repostory was just a test repository. It did not
contain the latest code. I removed it as part of the server migration
because it did not have current source code. The current source code is
available on the Wiki. I will put S2I back in the repository in the near
future though.
Thanks,
Wayne

Post by Earl Baugh
Doug,
Quick question, I'm trying to check out "Release" which I had checked
out before /tags/Release, but that doesn't seem to exist any more.
That just a hiccup on the migration?
Also, for some reason I had a link to what I thought was the code for
the firmware of the S2I board... but that also seems to be broken
(but then again, I don't recall if I had actually gotten that to
work... but I had seen it somewhere...)
Anyway, just wondering.
Earl
On Thu, Jun 20, 2013 at 10:46 PM, Douglas Goodall

Post by Douglas Goodall
Friends,
The migration is complete off the old server, onto a new and
much higher powered server, with a fatter pipe to the Internet.
Our thanks to Wayne for the migration and continued admin
of the subversion system provided for B8VEM use.
The new subversion URL's are now...
svn co svn://ichibrosan.com/RomWBW
svn co svn://ichibrosan.com/FdTst
svn co svn://ichibrosan.com/XModem
Have fun...
Douglas Goodall
p.s. ichibrosan.com is my new domain that replaces goodall.com
which I recently sold as part of my old company.
---http://www.linkedin.com/in/douglasgoodall
--
You received this message because you are subscribed to the Google
Groups
"N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/groups/opt_out.

[Bill Lewis]

Has anyone tried the newest TortoiseSVN 1.8.0 yet?

Migrating working copies is one-way to 1.8. You can't go back.

[Wayne Warthen]

I have not tried it yet. If I understand correctly, this should not affect
the server-side repository at all, so all client versions should still be
able to access the server repository and checkout/checkin without any
issues. The main thing to keep in mind is if you had multiple, different
client tools pointing at the same local working copy, they would all need
to be migrated to the new version.

If you wanted to go back to an older client, you could always just do a
complete new checkout from the server I guess.

--Wayne

Post by Bill Lewis
Has anyone tried the newest TortoiseSVN 1.8.0 yet?
Migrating working copies is one-way to 1.8. You can't go back.

[roman fulek]

Hi, is this domain ichibrosan.com<http://www.google.com/url?q=http%3A%2F%2Fichibrosan.com&sa=D&sntz=1&usg=AFQjCNEIjgky5kO16EWwlzXPjKcW5wK5_w>the right SVN domain currently ? All I get is:
svn co svn://ichibrosan.com/RomWBW
svn: E730060: Unable to connect to a repository at URL
'svn://ichibrosan.com/Rom
WBW'
svn: E730060: Can't connect to host 'ichibrosan.com': A connection attempt
faile
d because the connected party did not properly respond after a period of
time, o
r established connection failed because connected host has failed to
respond.

[Wayne Warthen]

Hi Roman,

Douglas has turned off that repository. I have moved the RomWBW repository
over to Google Code.

You can access it as a regular web page at https://code.google.com/p/romwbw/

You will also find instructions there for accessing it directly via SVN.

Thanks,

Wayne

Post by Douglas Goodall
svn co svn://ichibrosan.com/RomWBW
svn: E730060: Unable to connect to a repository at URL 'svn://
ichibrosan.com/Rom
WBW'
svn: E730060: Can't connect to host 'ichibrosan.com': A connection
attempt faile
d because the connected party did not properly respond after a period of
time, o
r established connection failed because connected host has failed to
respond.

[roman fulek]

Thanks Wayne!
Roman

Post by Wayne Warthen
Hi Roman,
Douglas has turned off that repository. I have moved the RomWBW
repository over to Google Code.
You can access it as a regular web page at
https://code.google.com/p/romwbw/
You will also find instructions there for accessing it directly via SVN.
Thanks,
Wayne

Post by Douglas Goodall
svn co svn://ichibrosan.com/RomWBW
svn: E730060: Unable to connect to a repository at URL 'svn://
ichibrosan.com/Rom
WBW'
svn: E730060: Can't connect to host 'ichibrosan.com': A connection
attempt faile
d because the connected party did not properly respond after a period of
time, o
r established connection failed because connected host has failed to
respond.