Ryan Schmidt wrote:
> On Oct 21, 2008, at 02:52, Ruslan Sivak wrote:
>
>> Stefan Sperling wrote:
>>
>>> On Tue, Oct 21, 2008 at 03:09:51AM -0400, Ruslan Sivak wrote:
>>>
>>>> We've had these kind of issues on an off for about a month now.
>>>> They seem to just go away by themselves, but I wanted to see if
>>>> anyone here has an idea of what's going on. I can't seem to make
>>>> this one go away.
>>>> I switch to a certain directory and do an svn update. It updates
>>>> a bunch of files and then errors out with
>>>>
>>>> svn: In directory '.'
>>>> svn: Can't open file
>>>> '.svn\tmp\text-base\fc228205-7e93-ee10-e903ca61ec859384.jpg
>>>> .svn-base': The system cannot find the file specified.
>>>>
>>>> Any idea of what could be wrong here?
>>>
>>> Please provide more information.
>>>
>>> Have you checked whether the file really there?
>>>
>>> Are you using Windows or Linux with a FAT partition?
>>> Is the working copy on a filesystem which does not treat filenames
>>> as case-sensitive (i.e. it cannot tell apart lower case from upper
>>> case letters)? If so, was that file originally checked in under a
>>> name which only differs in case from what the error is printing?
>>
>> Thank you for your help. The file did indeed turn out to be in
>> repository twice - in two differenent cases.
>
> Ok. You can install a pre-commit hook to prevent this from happening
> in the future:
>
> http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/case-insensitive.py
>
>
Thank you, I will look into installing this.
>> I guess this goes back to my issue of committing the files. The
>> changes happen directly on the file system, and nightly I issue an
>> svn commit as part of a batch process. The problem, however, is that
>> it doesn't commit deletiions. Is there still no way to pass a
>> parameter to the svn executable to tell it to commit the deletions as
>> well?
>
> Run "svn rm" for each file you want to delete. Then "svn ci".
>
This will add a lot of complexity to my application. It will also add
extra revisions which we don't necessarily need. For example, someone
uploads a photo for the photo gallery. I would then resize the photo,
and all the original and all the new sizes into the repository. The
person then decides to replace that photo with a different one. I now
delete the old photos, commit, upload the new photo, resize, add the
files, commit again.
Not only is this a lot more complicated, but it wastes repository space.
> Sounds like you've already deleted the files without informing
> Subversion, and would like to now inform Subversion of this after the
> fact. To find out which files you need to "svn rm", you could run "svn
> st" -- those lines beginning with "!" are the files which were
> improperly removed.
>
> You generally don't want to detect things after the fact. Use the
> correct "svn" commands at the time the action occurs. See the FAQ:
>
> http://subversion.tigris.org/faq.html#wc-change-detection
>
Thank you, I've read this before. I understand that it says not to do
it, but in our case that's exactly what we want to do. Deletes and adds
are handles just fine, and we don't do renames. I think a while ago
smoeone posted a batch script that could be used to auto commit the
deleted files - does anyone still have it? I really wish this would be
part of subversion someday.
Russ
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-21 18:28:07 CEST