[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: We could find some revision in SVN repository

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Wed, 19 Aug 2009 12:00:20 +0100

2009/8/19 Petr Fejfar <petr.fejfar_at_gmail.com>:
> On Wed, Aug 19, 2009 at 10:16 AM, Simon
> Large<simon.tortoisesvn_at_googlemail.com> wrote:
>>> Maybe it is related to problem described in my another post and process,
>>> when I was trying to resynchronize TortoiseSVN:
>>> 1. I had 10 non-versioned folders, each containing 4 non-versioned files.
>>> 2. TortoiseSVN behaved like folders & files has been commited,
>>>    but they were not.
>> What do you mean by this? What is TortoiseSVN's behaviour? Why do you
>> say they are not committed?
> Hi Simon,
> have you read the (probably) related thread "TortoiseSVN falls out of
> step with repository"? (maybe my bad I've created two separated
> topics). It seems that the primary problem is client fallen out of
> steps with repository described in the second post. Once again:
> 1. I've committed non-versioned folders with files by checking on
> checkboxes in commit summary dialog
> 2. TortoiseSVN client then showed that everything has been commited
> and there are no modifications or non-versioned files to be committed
> 3. If my collegue updated his WC, those folders and files were missing
> in repository
> 4. If I checked source out by command line client into temporary
> location, the folders and files were really missing
> 5. I had to manually remove non-existing folders from repository and
> add them explicitelly by add command as described above

How do you remove folders that do not exist?

> 6. Revisions between commitment of those folders shown by TortoiseSVN
> as committed and adding those folders manually by add command again
> are two levels up,
>   but no action was recorderd and no data are missplaced
> 7. Nobody of us has changed URL.
>> You keep describing these revisions as missing, but we have already
>> established that they are not; they are just not where you expected
>> them to be.
> Sorry for that: I don't keep describing them as missing, but as
> "missing" for brevity.
>> Use repo browser to show the log for the repository root. Then LOOK AT
>> IT. That will tell you where the 'missing' files have been
>> copied/moved from and who did it.
> IT SHOWS ME NOTHING. The bottom panel with action is empty for those
> "missing" revisions...

That conflicts with your earlier description where you said the files
are present in the repository but two levels up. Are the files there
or not?

>> nested WCs or something else strange. Use Check for Modifications in
>> the working copy to see this. Use the Subversion tab on the Windows
>> folder properties to check whether the WC URL is what you think it
>> should be.
> Nothing special can be seen there. URL is correct and nobody of us has
> changed it.
>> On the WC that caused the problem try looking in
>> TortoiseSVN->Settings->Saved Data->Action Log and see what actions
>> were recorded.
> There are logged modifications and content sending of files being
> inside non-versioned folders which does not exists in repository and
> which TortoiseSVN finally marked as commited. The commit is reported
> as completed with no errors.

This really does sound like a server problem unless there is something
we are missing. Have you followed Stefan's suggestion to verify the
repository integrity?

You might do better asking on the users @ subversion list as this
problem seems to be unrelated to TortoiseSVN.


:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-19 13:00:31 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.