Wade Hampton wrote:
> kfogel@collab.net wrote:
>
>> Is the data itself private? If not, you could send us a dumpfile, and
>> we could reproduce that way...
>>
>>
> Unfortunately, this data is. Any hints on inspecting the dump file?
> Should I dump then
> try to reimport as a new repo name and see if that works?
Solved.
I dumped the repo:
-- on server, as root:
cd /repohome/svn
svnadmin dump E >e.dmp
Next, I edited the dump file and removed 4 lines making
trunk/install_system/VERSION.sh
executable (see below).
Next created a test repo, imported it, then checked it out, all worked.
-- on server as root
svnadmin create etest
svnadmin load etest <e.dmp
chown -R apache2:apache2 etest
-- on test machine:
cd ~/work
svn checkout http://gandalf:8080/svn/etest etest
To fix, all I had to do was to remove the four lines starting at K 14
which made the symlink executable. Symlinks are mode 777
by default hence making it executable is not required (may fail?).
I think the problem was that VERSION.sh had been a file
reference (made executable), but was removed (svn rm)
and replaced with a symlink (svn add). The make executable
must be an artifact. However, it should not kill my checkouts
of the repo (at most should cause a warning). This seems to be
a bug in svn.
An excerpt of my dump file:
Node-path: trunk/install_system/VERSION.sh
Node-kind: file
Node-action: add
Prop-content-length: 59
Text-content-length: 18
Text-content-md5: e82b705f0e89ad0996f1d8345a272c30
Content-length: 77
K 11
svn:special
V 1
*
K 14
svn:executable
V 1
*
PROPS-END
link ../VERSION.sh
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 2 15:23:15 2004