Subversion is back up read only, no commit access yet, not sure when it will be back up fully.
Unfortunatley subversion does not have a nice way to recover from these types of situations, so for those of us who lost commits, here is what we must do.
1. Check out a fresh copy of your branch somewhere else
2. Do a diff between the old working copy and the new checkout
3. Apply the diff to your new checkout
4. Commit the fresh copy back into repository and kill the old working copy
Here is some more info for those interested.
http://thread.gmane.org/gmane.comp.version-control.subversion.user/48940/focus=48940
-Justin
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Justin Deoliveira wrote:
Subversion is back up read only, no commit access yet, not sure when it will be back up fully.
This is not good, can we set up a temporary home for the next week? You are teaching us the new framework - and if we cannot look at it we cannot learn or help you with it.
Options:
- Paul - can we grab a spike directory on geotools for a couple of weeks?
- Chris - do you have an svn server of your own we can actually move to?
- Justin can you talk to the tigris people to see if they can lend us svn space? (this is the shared framework we are talking about).
Justin if the above do not work out we will just have to take a fork based on your code locally - I prefer to keep things
public in case anyone wants to follow along with your new documentation.
Cheers,
Jody
Unfortunatley subversion does not have a nice way to recover from these types of situations, so for those of us who lost commits, here is what we must do.
1. Check out a fresh copy of your branch somewhere else
2. Do a diff between the old working copy and the new checkout
3. Apply the diff to your new checkout
4. Commit the fresh copy back into repository and kill the old working copy
Here is some more info for those interested.
http://thread.gmane.org/gmane.comp.version-control.subversion.user/48940/focus=48940
-Justin
Jody,
No matter what you do, if you want to re-host that archive you're going to have to get your hands on an svn dump or you'll lose all your revision history. Not sure if those are easy to come by right now?
P.
On 21-May-06, at 12:36 PM, Jody Garnett wrote:
Justin Deoliveira wrote:
Subversion is back up read only, no commit access yet, not sure when it will be back up fully.
This is not good, can we set up a temporary home for the next week? You are teaching us the new framework - and if we cannot look at it we cannot learn or help you with it.
Options:
- Paul - can we grab a spike directory on geotools for a couple of weeks?
- Chris - do you have an svn server of your own we can actually move to?
- Justin can you talk to the tigris people to see if they can lend us svn space? (this is the shared framework we are talking about).
Justin if the above do not work out we will just have to take a fork based on your code locally - I prefer to keep things
public in case anyone wants to follow along with your new documentation.
Cheers,
Jody
Unfortunatley subversion does not have a nice way to recover from these types of situations, so for those of us who lost commits, here is what we must do.
1. Check out a fresh copy of your branch somewhere else
2. Do a diff between the old working copy and the new checkout
3. Apply the diff to your new checkout
4. Commit the fresh copy back into repository and kill the old working copy
Here is some more info for those interested.
http://thread.gmane.org/gmane.comp.version-control.subversion.user/48940/focus=48940
-Justin
Well we have full read access so I could a checkout and dump if need be.
Paul Ramsey wrote:
Jody,
No matter what you do, if you want to re-host that archive you're going to have to get your hands on an svn dump or you'll lose all your revision history. Not sure if those are easy to come by right now?
P.
On 21-May-06, at 12:36 PM, Jody Garnett wrote:
Justin Deoliveira wrote:
Subversion is back up read only, no commit access yet, not sure when it will be back up fully.
This is not good, can we set up a temporary home for the next week? You are teaching us the new framework - and if we cannot look at it we cannot learn or help you with it.
Options:
- Paul - can we grab a spike directory on geotools for a couple of weeks?
- Chris - do you have an svn server of your own we can actually move to?
- Justin can you talk to the tigris people to see if they can lend us svn space? (this is the shared framework we are talking about).
Justin if the above do not work out we will just have to take a fork based on your code locally - I prefer to keep things
public in case anyone wants to follow along with your new documentation.
Cheers,
Jody
Unfortunatley subversion does not have a nice way to recover from these types of situations, so for those of us who lost commits, here is what we must do.
1. Check out a fresh copy of your branch somewhere else
2. Do a diff between the old working copy and the new checkout
3. Apply the diff to your new checkout
4. Commit the fresh copy back into repository and kill the old working copy
Here is some more info for those interested.
http://thread.gmane.org/gmane.comp.version-control.subversion.user/ 48940/focus=48940
-Justin
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
I am not sure if the temporary move is rash or not. All I know is that I am choked that we have a bunch of developers who are actually getting paid to be trained as GeoServer developers but are sitting bored because of this darn outage.
-Justin
Jody Garnett wrote:
Justin Deoliveira wrote:
Subversion is back up read only, no commit access yet, not sure when it will be back up fully.
This is not good, can we set up a temporary home for the next week? You are teaching us the new framework - and if we cannot look at it we cannot learn or help you with it.
Options:
- Paul - can we grab a spike directory on geotools for a couple of weeks?
- Chris - do you have an svn server of your own we can actually move to?
- Justin can you talk to the tigris people to see if they can lend us svn space? (this is the shared framework we are talking about).
Justin if the above do not work out we will just have to take a fork based on your code locally - I prefer to keep things
public in case anyone wants to follow along with your new documentation.
Cheers,
Jody
Unfortunatley subversion does not have a nice way to recover from these types of situations, so for those of us who lost commits, here is what we must do.
1. Check out a fresh copy of your branch somewhere else
2. Do a diff between the old working copy and the new checkout
3. Apply the diff to your new checkout
4. Commit the fresh copy back into repository and kill the old working copy
Here is some more info for those interested.
http://thread.gmane.org/gmane.comp.version-control.subversion.user/48940/focus=48940
-Justin
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Paul Ramsey wrote:
Jody,
No matter what you do, if you want to re-host that archive you're going to have to get your hands on an svn dump or you'll lose all your revision history. Not sure if those are easy to come by right now?
Agreed Paul, I understand that read only access is available as of Sunday. Perhaps I should just make a local fork rather then bother everyone (and just not preserve history when merging back with TOPP). It has been a couple of weeks and I have not seen a damage control plan out of TOPP yet so am needing to start thinking for myself.
I would set things up here, but bandwidth is very expensive so I cannot make a public repo. Suppose I could talk to that local research group that uses GeoServer.
Jody
P.
On 21-May-06, at 12:36 PM, Jody Garnett wrote:
Justin Deoliveira wrote:
Subversion is back up read only, no commit access yet, not sure when it will be back up fully.
This is not good, can we set up a temporary home for the next week? You are teaching us the new framework - and if we cannot look at it we cannot learn or help you with it.
Options:
- Paul - can we grab a spike directory on geotools for a couple of weeks?
- Chris - do you have an svn server of your own we can actually move to?
- Justin can you talk to the tigris people to see if they can lend us svn space? (this is the shared framework we are talking about).
Justin if the above do not work out we will just have to take a fork based on your code locally - I prefer to keep things
public in case anyone wants to follow along with your new documentation.
Cheers,
Jody
Unfortunatley subversion does not have a nice way to recover from these types of situations, so for those of us who lost commits, here is what we must do.
1. Check out a fresh copy of your branch somewhere else
2. Do a diff between the old working copy and the new checkout
3. Apply the diff to your new checkout
4. Commit the fresh copy back into repository and kill the old working copy
Here is some more info for those interested.
http://thread.gmane.org/gmane.comp.version-control.subversion.user/48940/focus=48940
-Justin
Looks like write access will be available tommorow. They will send out a notice sometime tommorow about how people can go about getting their LDAP account passwords.
-Justin
Justin Deoliveira wrote:
I am not sure if the temporary move is rash or not. All I know is that I am choked that we have a bunch of developers who are actually getting paid to be trained as GeoServer developers but are sitting bored because of this darn outage.
-Justin
Jody Garnett wrote:
Justin Deoliveira wrote:
Subversion is back up read only, no commit access yet, not sure when it will be back up fully.
This is not good, can we set up a temporary home for the next week? You are teaching us the new framework - and if we cannot look at it we cannot learn or help you with it.
Options:
- Paul - can we grab a spike directory on geotools for a couple of weeks?
- Chris - do you have an svn server of your own we can actually move to?
- Justin can you talk to the tigris people to see if they can lend us svn space? (this is the shared framework we are talking about).
Justin if the above do not work out we will just have to take a fork based on your code locally - I prefer to keep things
public in case anyone wants to follow along with your new documentation.
Cheers,
Jody
Unfortunatley subversion does not have a nice way to recover from these types of situations, so for those of us who lost commits, here is what we must do.
1. Check out a fresh copy of your branch somewhere else
2. Do a diff between the old working copy and the new checkout
3. Apply the diff to your new checkout
4. Commit the fresh copy back into repository and kill the old working copy
Here is some more info for those interested.
http://thread.gmane.org/gmane.comp.version-control.subversion.user/48940/focus=48940
-Justin
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com