Labels

Android (1) bash (2) boost (2) C (34) C++ (2) cheatsheet (2) CLion (6) css (3) Debian (33) DL (17) Docker (1) Dreamweaver (2) Eclipse (3) fail2ban (4) git (5) GitHub (4) Hacking (3) html (8) http (1) iOS (1) iPad (1) IRC (1) Java (30) javascript (3) Linux (164) Mac (19) Machine Learning (1) mySQL (47) Netbeans (4) Networking (1) Nexus (1) OpenVMS (6) Oracle (1) Pandas (3) php (16) Postgresql (8) Python (9) raid (1) RedHat (14) Samba (2) Slackware (45) SQL (14) svn (1) tar (1) ThinkPad (1) Virtualbox (3) Visual Basic (1) Visual Studio (1) Windows (2)

Friday 26 March 2021

SVN Error E200030 and others mentioning sqlite3 corrupt or malformed

I got this error while using PhpStorm and I believe this was down to me having my source files on a synced directory pCloud

I've had similar issues before whereby I've modified a file in an editor, say a bash script and then saved and when run the file, the previous version was in actual fact being run. I contacted pCloud and they advices that some development applications may cause this, hmmm.


anyway, on this occasion, I was able to fix my svn issue by checking our the repository to another location;

svn checkout http://192.168.8.5/svn/fec/www --username=myUsername

I then copied the .svn file from the new location to the old location, replacing all and all was well, but of course the larger problem is that I need to move my code files out of the synched directories as I fear this is just the tit of a very big icebearg.


 

 

No comments:

Post a Comment

Note: only a member of this blog may post a comment.