I tried what you suggested with 'svn delete' (did it via the
TortoiseSVN 'repo-browser') but it's still not fixed. The error message
(for an update via the TortoiseSVN client) has now changed to:
> Error: In directory
> Error: Unsupported special file type '#!'
Trying the 'svn co' command under FC4, I now get:
> A trunk/pygtk/interface/simulation.h
> svn: In directory 'trunk/pygtk/interface'
> svn: Unsupported special file type '#!'
> [john@cruncher2 ascend-broken]$
The file that is now causing the error is one that I haven't changed
since a few days before the error showed up.
You asked me to describe what I was doing. I'm not in a position to want
to reproduce this error yet (I don't even know how to fix it) but... I
was pretty much just using Subversion as usual. It was TortoiseSVN,
vesion 1.3.2 Build 5840 - 32 bit on a Win2k Pentium 4.
Using the MSYS commandline, was working on a checked-out version of the
repository. I ran 'libtoolize' and 'automake -m' then added the new
files to the repository. One of the new files, 'install-sh', was in fact
a symlink to /usr/share/install-sh or something like that. Because I had
my $PATH set up wrong in MSYS, the symlink actually points to
Come to think of it, it's possible that the working directory had been
checked out with cygwin svn, and then I was trying to commit using
I guess the question then is: how does TortoiseSVN handle symlinks, and
how does standard cygwin svn handle symlinks, and is it possible that
these are incompatible? And what aobut the path-mangling that happens
between cygwin, msys, and windows?
Clearly this 'install-sh' file shouldn't have been added to the
repository -- it's still bad that I managed to break the repository though.
Any other ideas?
Garrett Rooney wrote:
>On 3/2/06, John Pye <email@example.com> wrote:
>>Yesterday I managed to break our subversion repository, and I'm
>>wondering if anyone can give me some suggestions on how to fix it.
>>Around the time it broken, I checked in a MSYS-generated 'install-sh'
>>symlink file using TortoiseSVN on Win2k. This broke my local working
>>copy, which I don't mind, but it's now impossible for me to checkout a
>>new working copy from the repository, which is obviously bad. Here is
>>the error message, which as you can see corresponds to this 'install-sh'
>>>svn: In directory 'trunk/pygtk/interface'
>>>svn: Unsupported special file type '#!'
>>The repository details are here:
>>I tried using the 'svn cleanup' on my old working copy. It complains
>>about missing files in 'text-base'.
>>What can I do to get our repository working again? Is there any way I
>>can fix it without backend access?
>>If I *do* have backend access, what should I do then?
>You could probably delete the symlink via 'svn delete
>$URL_OF_REPOS/path-to-symlink', and then you'll be able to update
>again, although I'm quite curious exactly how you managed to make this
>happen. If you could provide a list of steps to get into this state
>that would be much appreciated.
School of Mechanical and Manufacturing Engineering
The University of New South Wales
Sydney NSW 2052 Australia
t +61 2 9385 5127
f +61 2 9663 1222
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Mar 3 02:10:19 2006