I use Easyeclipse for PHP with the Subclipse plugin for a long time without any problem.
This morning I committed my project without any problem. This afternoon I try to commit it again and it gives this error, which concerns only a subfolder.
Unsupported working copy format
svn: This client is too old to work with working copy
'My subfolder'; please get a newer Subversion client
I found several questions where the solution was an update of the client, like the error suggests. But in my case, I didn't change any configuration nor installed anything.
I fear that some files got corrupted.
It could have happened during a manual copy-paste process on my local copy, but I have no indication for this.
Is there a way to know for sure if the problem is with the server side or with the client side.
What are possible steps to restore the situation ?
The problem is with the client side, server is not contacted at this stage. Your local repository checkout might have been silently upgraded by another svn client you use. Or it might also be damaged and Subclipse errorneously reports it as an upgrade it doesn't understand.
If you don't want to upgrade Subclipse, your only way is to do a fresh checkout from server, and copy over your changes from this upgraded repository.
This probably means you used another SVN client that was a newer version and upgraded the working copy to a newer format. Subclipse has versions that support all versions of Subversion. Most likely you need to install Subclipse 1.10.x which contains support for the SVN 1.8 working copy format.
http://subclipse.tigris.org/servlets/ProjectProcess?pageID=p4wYuA
Once you upgrade Subclipse to the right version it will immediately work again. Your existing working copy ought to still be fine.
In my case I move eclipse workspace place to another then problem is occured. For solving problem I checkout project form the svn repo. Then in old project I clean all svn files. (simple search .svn and delete ) then I copy the content to the just checkedout one my changes become visible and my project is up to date. This method can be applied for other annoying errors. Hope help someone
Related
im very frustrated because i lost a lot of hours reading and testing, and could not find how to make it live.
I cloned and downloaded Zidisha git
Then i followed these instruction: image
At the stage 5. -vagrant up calls a file that doesn't have on the server.
I need to find a server with this saucy.box or exists a easier/another method?
Thank you
This project is using ubuntu-saucy which has been deprecated (see https://en.wikipedia.org/wiki/Ubuntu_version_history#Table_of_versions) so the link referenced on cloud-images is not available anymore, and the box itself (larryli/saucy64) is not available on vagrant atlas.
You are left with 2 options:
build your vagrant box yourself using the same ubuntu release (can be found https://cloud-images.ubuntu.com/releases/13.10/)
upgrade the ubuntu release to a more recent one and still supported (you can use trusty64 or xenial64)
Note: this project has not been updated for the last 3 years - there are many chances that you will find a lot of obsolete things in it.
I thought this had to be a common problem, but I was not able to find an easy solution. The problem is, we are working with multiple people on developing a website, without any version control involved. Which leads to obvious problems with conflicting edits and someone messing up the whole site with no simple way to recover. Currently some work with Filezila + Notepad++ directly downloading, additing and uploading the files.
Others work with Netbeans on their local copy and upload the files automatically when saving.
What I would like to do now is intruduce a version control system that still lets everyone work on the live system, but checks for conflicts and allows to rollback files to previous versions.
I tried to set up GIT with a post-receive hook that copies everything to the webroot, but failed in doing so. Besides I think SVN might be a better solution because everyone has just to checkout/commit instead of pull/commit/push.
Is it possible to set up GIT/SVN the way I like to?
Is there a better solution?
I have an SVN server setup and a cron job on the dev server to pull the latest revision out every 60 seconds. Then I have another script on the live server that isn't croned but I can manually run which updates the live server to the specified revision when I request it.
This allows the devs to commit and automatically test on the dev server pretty much real time and then when we've reviewed the code changes etc on the dev server and we're happy with it then I manually run the update on the live server.
The "common" problems come from you letting them work on live website ...
A developer on live will always find a way to ruin your day!
We are two in a team working on the same project. i am on MAC and the other one is on PC. i have never used SVN before. googling about the SVN gave me basic understanding about svn. and what i understood is there should be subversion installed in client machine (i do not know which client, i assume there are many like versions and cornerstone for mac, tortoise for windows etc. and i require a repository where i will host the centralized version of the application. the client will get the copy of codes or files where they can commit the changes to repository (main application). which can be undone if required. however what i don't understand is, as our PHP code uses database(mysql in my case) how is it managed by SVN client?
lastly i expect my development environment to be implemented the following way.
i want to set up my mac as development server for SVN at the same
time i would like to work in the same machine making use of SVN.
PC should access the repository from MAC and commit the changes.
all the setup should be done and implemented locally via LAN. please correct me if i am wrong on my understanding about the svn and also do guide me about the requirements and resources i need to install in both the machine for me to get going using SVN for my projects.
thank you..
You can use your Mac both for hosting your SVN repository and also use it as the client to checkout your working copy. Have a look at this link (its slightly old but you'll get the gist).
Once you have the SVN repository setup you can enable HTTP access on it so that your partner can checkout the copy and commit changes to it. Have a look here on how to enable HTTP access for your repository.
Most modern day PHP Frameworks use migrations scripts that help in building and maintaining your database schema, if possible use a framework. Have a look at the migrations script of one of the frameworks for inspiration (i.e if you can't use a framework). Migration scripts under the hood fire create table or alter table commands, and all you do is add the migration files to your SVN repository to version control your database schema.
One caveat with hosting the SVN repository on your Mac is that for some reason if its down, your partner gets stuck as code changes can't be committed and new changes can't be checked out. Have a look at this thread for free online private SVN repositories. In case you want to go the paid route GitHub.com is awesome.
I develop on my own and use a repository hosted on http://www.springloops.com. On here I just export the database to a text file and keep historic changes to the database on there. Clearly this is not suitable for a team working together on a project unless you're well coordinated in recording your database changes.
This question looks useful MySQL Version Control - Subversion though it's specific to mysql subversioning - not quite the answer to your broader question.
Each machine should have the relevant Client software, I recommend Tortoise SVN for Windows - it's pretty popular. There is bound to be a similar alternative SVN Client for OSX that you can get your hands on.
I noticed a strange sync problem. I have my project setup as a remote project and everything works fine. I have it set to upload on save. However, if someone on my server is working on a file and saves it. I don't see this change in netbeans and I end up opening a older version of the file and overwriting my colleague's changes when I press save.
Is there a way to have netbeans check the remote server for the latest file before saving?
thanks
No, NetBeans can not check the remote file automatically. It's just not set up to do that. Even if it were, you would still run into problems where you would clobber your colleague's changes, or he would clobber yours.
What you have is a basic version control problem, which is best solved by implementing one of the several version control systems out there (e.g., CVS, Subversion, Git, Mercurial, etc.) and then "building" your website out to the server from version control. Short of that, an imperfect solution would be to partition the files such that you are forbidden to edit files assigned to your colleague, and vice-versa.
NetBeans can download the file for you, but only when you tell it to by right-clicking on the file and choosing the Download command. This downloads the file whether it has been updated by someone else or not.
I am using Eclipse Version: 3.3.2
I have imported a project which is on already on SVN repository. I just checked out in wwwroot and then imported into eclipse. Done some changes. Then i was thinking to install subclipse.
opened eclipse plugin manager installed Subclipse 1.2.4.
Then right clicked on project ->Team -> Share Project -> selected SVN. It shows an error :
org.tigris.subversion.javahl.ClientException:
Unsupported working copy format svn:
This client is too old to work with
working copy
'C:\Inetpub\wwwroot\project'; please
get a newer Subversion client
Is there any problem with Subclipse? Is it effect SVN repository or my changes?
Should i proceed further?
There are several versions of svn, and therefore, several versions of subclipse (and of subversive). If you don't checkout your project with subclipse but with another svn client, you will possibly have problems if the versions differ. If you have made some changes, commit them with the client you svn coed your project with, and then
either you install the matching subclipse (or subversive) version
either you delete your project and check it out again, but with subclipse (using new Project> checkout from SVN)