>
> Can you actually use a new repository created by svnadmin 1.5 with your
> 1.6.12 server install? Or is it just previous repositories that are working?
>
>
Yes. With my 1.6.12 server install, if I create a new repository like this:
#svnadmin create --pre-1.6-compatible myproject
then it works
NFS
shares.
BOb
From: Tech Geek [mailto:techgeek12...@gmail.com]
Sent: Wednesday, September 29, 2010 8:21 PM
To: users@subversion.apache.org
Subject: Re: Wrong value in db/format when creating from TortoiseSVN
I also experimented with http:// protocol and the same error message. I have
spent
On Thu, Sep 30, 2010 at 09:10:36AM -0700, Tech Geek wrote:
> Neil,
>
>
> > Not that I can help, but I wanted to clarify: you have a repo on a
> > CIFS-mounted shared drive, and are then using a Linux SVN server?
> >
> Yes that is correct.
>
> Although I admit that may not always be practical, e
Neil,
> Not that I can help, but I wanted to clarify: you have a repo on a
> CIFS-mounted shared drive, and are then using a Linux SVN server?
>
Yes that is correct.
Although I admit that may not always be practical, esp. in an enterprise (we
> plan to move to using NFS-mapped repos. when our S
Around about 30/09/10 01:21, Tech Geek typed ...
1. Repositories created on shared network drive with 1.6.12 subversion
engine (svnadmin) or 1.6.10 TSVN, will not commit through TSVN or even
through a Linux svn client.
Not that I can help, but I wanted to clarify: you have a repo on a
CIFS-
I also experimented with http:// protocol and the same error message. I have
spent last 2 days just working on these issues and here is what I would like
to summarize:
1. Repositories created on shared network drive with 1.6.12 subversion
engine (svnadmin) or 1.6.10 TSVN, will not commit through T
OK guys so I ended up upgrading the subversion server to 1.6.12 the same as
TortoiseSVN is built against.
Now I am able to checkout the repositories through TSVN but whenever I try
to commit I get the following error message:
$Commit failed (details follow):
$Couldn't perform atomic initialization
On 9/28/2010 6:20 PM, Tech Geek wrote:
Les,
The point remains that if they have write access through mapped
files, they have the capability of destroying everything there.
You could probably whip up a cgi script to create new
repositories from a web request form
>> Do not put your repository on a shared drive. Do not use file:
>> protocol to access it. It is not designed to work in such way. Read
>> the documentation (aka svnbook) and configure a proper server.
>
> This should be emphasized more. Although the OP said he wanted the
> users to be able to c
On Sep 28, 2010, at 18:20, Tech Geek wrote:
> My only other option now is to try upgrading the SVN server on the Linux
> machine...
That would be a good idea in any case. But if that can't be done, the previous
suggestions were good ones too:
* write a CGI script users can access over the we
Les,
> The point remains that if they have write access through mapped files,
>> they have the capability of destroying everything there.
>>
>> You could probably whip up a cgi script to create new repositories from a
>> web request form if something like that doesn't already exist. Or you coul
On 9/28/2010 2:23 PM, Tech Geek wrote:
Do not put your repository on a shared drive. Do not use file:
protocol to access it. It is not designed to work in such way. Read
the documentation (aka svnbook) and configure a proper server.
This should be emphasized more. Al
>
> Do not put your repository on a shared drive. Do not use file:
>> protocol to access it. It is not designed to work in such way. Read
>> the documentation (aka svnbook) and configure a proper server.
>
>
> This should be emphasized more. Although the OP said he wanted the users
> to be able
On 9/28/2010 12:57 PM, Konstantin Kolinko wrote:
Anyway, you must learn how to use and administer svn properly, and a
proper way to create a repository is to use "svnadmin create".
Do not put your repository on a shared drive. Do not use file:
protocol to access it. It is not designed to work
What Ryan said. Thanks, Ryan.
Ryan Schmidt wrote on Tue, Sep 28, 2010 at 12:47:51 -0500:
> On Sep 28, 2010, at 12:40, Tech Geek wrote:
> > Daniel,
> >> Or do (the Tortoise equivalent of) 'svnadmin create --pre-1.6-compatible'
> > Actually I would prefer to do the other way around. Can we tell TSV
2010/9/28 Tech Geek :
> Daniel,
>>
>> Or do (the Tortoise equivalent of) 'svnadmin create --pre-1.6-compatible'
>
> Actually I would prefer to do the other way around. Can we tell TSVN to
> create repositories which are compatible with Subversion Engine 1.5 because
> we would be usually creating re
On Sep 28, 2010, at 12:40, Tech Geek wrote:
> Daniel,
>> Or do (the Tortoise equivalent of) 'svnadmin create --pre-1.6-compatible'
> Actually I would prefer to do the other way around. Can we tell TSVN to
> create repositories which are compatible with Subversion Engine 1.5 because
> we would be
Daniel,
> Or do (the Tortoise equivalent of) 'svnadmin create --pre-1.6-compatible'
>
Actually I would prefer to do the other way around. Can we tell TSVN to
create repositories which are compatible with Subversion Engine 1.5 because
we would be usually creating repositories using the TSVN.
AFA
Daniel Becroft wrote on Tue, Sep 28, 2010 at 10:51:29 +1000:
> On Tue, Sep 28, 2010 at 10:49 AM, Tech Geek wrote:
>
> > >I don't know what the repository version numbers are that correspond to
> > each svn/TSVN version (and you didn't mention which >versions you have
> > installed).
> > Linux SVN
On Tue, Sep 28, 2010 at 10:49 AM, Tech Geek wrote:
> >I don't know what the repository version numbers are that correspond to
> each svn/TSVN version (and you didn't mention which >versions you have
> installed).
> Linux SVN Server version 1.5.1 (r32289)
> TSVN - 1.6.10 (32-bit)
>
That looks lik
>I don't know what the repository version numbers are that correspond to
each svn/TSVN version (and you didn't mention which >versions you have
installed).
Linux SVN Server version 1.5.1 (r32289)
TSVN - 1.6.10 (32-bit)
On Tue, Sep 28, 2010 at 5:23 AM, Tech Geek wrote:
> I have the subversion server running on a Debian Linux machine. The
> repositories are residing on a Windows domain shared network drive on the
> network which is mapped on the Linux machine as:
> mount -t cifs //software/svn_repositories /var/
22 matches
Mail list logo
