CODEWITHSUNDEEP
svntortoisesvnsmartsvn
ephraim
ephraim

Reputation: 436

SVN- pristine text missing

Already frustrated...Trying to update/commit/cleanup Tortoise SVN but always getting the notification about pristine text missing.

found some posts/questions on SO and on the web, nothing helped:

pristine svn-base file missing - suggests to clean pristine file, In my case it's the "pristine text" not found.

pristine svn-base file missing - suggests using smartSVN- clicking "Modify"->validate Admin Area - which doesn't exist anymore in smart SVN I've just downloaded...

And Error in Netbeans & Svn: Pristine text not found doesn't have an answer...

Anybody- some help please?

Upvotes: 1

Views: 19596

Answers (4)

dj_tony
dj_tony

Reputation: 11

i've done fresh chekout in new folder and copied the missing pristine file from there into not working copy pristine directory. seems work fine.

Upvotes: 1

Milan Parmar
Milan Parmar

Reputation: 130

There is an easy way for this. Take new SVN checkout for the same database/trunk. After that go to corrupted_database/ find the .svn folder. rename this folder to .svn_old (use command inside "corrupted_database" directory mv corrupted_database/.svn corrupted_database/.svn_old)

Now go to the "fresh_checkout" and find .svn folder. copy this folder to corrupted_database using command cp -r fresh_checkout/.svn corrupted_database/

Now do cd corrupted_database; svn up and check its working.

Upvotes: 3

LSerni
LSerni

Reputation: 57428

I have just had the same problem. The pristine text was actually there in 

.svn/pristine/09/09verylongnamereportedbysvncleanup.svn-base

and by inspecting its contents I could track it down to

./local/foobar/somefile

One other way is to access directly the SVN database:

sqlite3 .svn/wc.db
sqlite> SELECT repos_path FROM nodes WHERE checksum LIKE '%7685df22%';
path/to/the/file/that/got/corrupted
sqlite> .quit

Remove the file (move it somewhere else, e.g. rename it to ".bak"), run a svn cleanup, a svn update on that file, and review apply any changes from the previously saved copy.

Upvotes: 4

Álvaro González
Álvaro González

Reputation: 146630

The Subversion working copy format is not particularly robust and it's not strange that it gets corrupted now and then. When that happens, it's normally not worth the effort of fixing it. If svn cleanup can't cope with it, it's better to:

  1. Check out a fresh working copy.
  2. Copy your pending changes from the damaged working copy using your favourite file comparison tool (Meld, WinMerge, KDiff3, whatever).

You should not lose important information beyond changelists because everything else is stored on the repository, given that Subversion is a centralised version control system.

Upvotes: 9

Related Questions