Hello Ryan,
Many thanks for your response. I appreciate your comments
and suggestions. If you don't mind, can I kick things around
a bit more with you?
} It sounds like the files and/or directories in /usr/local/svn/tsakai
} are not owned by you, hence permission denied. Change their ownership
} to you, or if this repository is for more than just testing out
} Subversion's functionality, then set up svnserve or apache and change
} the ownership of the files to the user you run svnserve or apache as.
The ownership of /usr/local/svn/tsakai is:
drwxr-sr-x 6 root apache 4096 Aug 25 14:03 /usr/local/svn/tsakai
I asked myself: Is svnserve supposed to run as daemon? And issued:
$ ps axl | grep svnserve
and got nothing. I went to /etc/init.d and found a script named
collabnet_subversion. I typed:
$ ./collabnet_subversion status
And the response was:
Collabnet Subversion server not configured.
Please run 'Configure-CollabNet-Subversion' to configure.
Surprised and intrigued by those 2 lines, I looked for
Configure-CollabNet-Subversion and found the script in
/opt/CollabNet_Subversion/bin directory and ran it. There
was some dialog and it found the existing repositories
(including mine, /usr/local/svn/tsakai). I mostly chose
default and gave a dns name, as well as the port number
(8099), and eventually told me:
Starting CollabNet Subversion: [ OK ]
Congratulations! You have successfully configured the CollabNet
Subversion server.
You can access your repositories at the following URL:
http://vixen.egcrc.org:8099/svn/YOUR-REPOS-NAME
http://vixen.egcrc.org:8099/viewvc/YOUR-REPOS-NAME
Naturally, I told firefox to go to:
http://vixen.egcrc.org:8099/svn/tsakai
and bingo! It is working.
And to go to: http://vixen.egcrc.org:8099/viewvc/tsakai
This is fantastic. I can look at everything I have ever checked in
and look at this and that. Super!
At this point, I was curious about the ownership of my repository.
I thought it might have changed.
$ ll -d /usr/local/svn/tsakai
drwxr-sr-x 6 csvn csvn 4096 Aug 25 14:03 /usr/local/svn/tsakai
In fact, it did change. (Previously, it was root (owner) and apache
(group owner).) I proceeded with issuing two commands:
$ svnadmin lslocks /usr/local/svn/tsakai
and it returned nothing with exit status of 0
$ echo $?
0
The same with:
$ svnadmin lstxns /usr/local/svn/tsakai
$ echo $?
0
Encouraged, I went on to issue what I started with yesterday:
$ svn import ~/Projects/pivot file:///usr/local/svn/tsakai -m "initial import"
svn: Can't open file '/usr/local/svn/tsakai/db/txn-current-lock': Permission denied
$ echo $?
1
Rats! is what I felt... What's next?
I tried:
$ svn --version
svn: Could not initialize the SASL library
Here, too, the exit status was 1.
} Do you have SASL installed? What version? How was it installed?
I am not real clear on SASL. I looked at directories /usr/lib/sasl
and version numbers in this directory seem to be one of
[0.0.7, 1.0.16, 1.0.17, 1.0.19, 1.0.20]. In /usr/lib/sasl2, there is
only: 2.0.19. /usr/lib64/sasl is like /usr/lib/sasl: [0.0.7, 1.0.16,
1.0.17, 1.0.19, 0.0.20]. Finally, /usr/lib64/sasl2 has only 2.0.19.
I have no idea how any of them got installed. (Maybe it is time
for a bit of disclosure... We had a guy working as system administrator
and he was a good talker at the outset, but it turned out he had no
idea what he was doing and wound up wrecking many linux machines.
The machine I have been referring to is only one of them and some of
us were extremely upset. The guy is no longer with us and I am trying
to resurrect what's been broken.)
I wanted to try something else (reaching out for straw). Namely,
$ sudo chown csvn /usr/local/bin/svnadmin
$ sudo chown csvn /usr/local/bin/svn
Now the owner of /usr/local/svn/tsakai and that of svnadmin and
svn are all the same, I tried the same thing as before:
$ svn import ~/Projects/pivot file:///usr/local/svn/tsakai -m "initial import"
and it told me the same thing as before:
svn: Can't open file '/usr/local/svn/tsakai/db/txn-current-lock': Permission denied
So... Where do I stand? Maybe it amounts to:
1) How do I fix/reinstall SASL?
2) Should I reinstall subversion (1.6.2) from scratch?
Can you please comment and give me some suggestion for path forward?
Thank you.
Regards,
Tena Sakai
tsakai_at_gallo.ucsf.edu
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2009b_at_ryandesign.com]
Sent: Wed 10/14/2009 1:44 AM
To: Tena Sakai
Cc: users_at_subversion.tigris.org
Subject: Re: svnadmin: Expected repository format '3' or '5'; found format '4'
On Oct 13, 2009, at 22:54, Tena Sakai wrote:
> I have a subversion repository on a linux machine.
> The path to the repository is /usr/local/svn/tsakai.
> I have a project which is under ~/Projects/pivot and
> I want to check in everything in this directory.
> I issued:
>
> $ svn import ~/Projects/pivot file:///usr/local/svn/tsakai -m
> "initial import"
>
> The machine's response was:
> svn: Can't open file '/usr/local/svn/tsakai/db/txn-current-lock':
> Permission denied
It sounds like the files and/or directories in /usr/local/svn/tsakai
are not owned by you, hence permission denied. Change their ownership
to you, or if this repository is for more than just testing out
Subversion's functionality, then set up svnserve or apache and change
the ownership of the files to the user you run svnserve or apache as.
> I asked:
> $ svnadmin lslocks /usr/local/svn/tsakai/db
>
> And the response was:
> svnadmin: Expected repository format '3' or '5'; found format '4'
>
> I asked a slightly different question:
> $ svnadmin lstxns /usr/local/svn/tsakai/db
>
> and I got the same response:
> svnadmin: Expected repository format '3' or '5'; found format '4'
svnadmin needs to be pointed at the repository directory, not its db
subdirectory, so if you want to list the locks and transactions, you
need
svnadmin lslocks /usr/local/svn/tsakai
and
svnadmin lstxns /usr/local/svn/tsakai
> I don't want anything fancy. I don't want to use apache
> portable library; I don't want to use berkeley db. I want
> to use something really basic (for now anyway).
You are already using the Apache Portable Runtime library. It is not
possible to use Subversion without it. It has nothing to do with using
the Apache Web Server, which is of course optional.
> Oh, one more thing. When I issue:
> $ svn --version
>
> It says:
> svn: could not initialize the SASL library
Do you have SASL installed? What version? How was it installed?
> And when I type:
> $ svn
>
> It melts down:
> Segmentation fault
>
> Does this mean I don't have command line client?
It means you have the command line client, and it crashes when you try
to use it. That should not happen, of course. My first suggestion
would be to investigate the SASL problem you already found.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2407760
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-15 04:30:47 CEST