Curunir Wolf | 1 Mar 01:18 2008
Picon

Expected format '3' of repository; found format '5'

I can't believe nobody else is having this problem, but I can't seem
to find a solution.  I'm running Tortoise SVN version 1.4.8, build
12137 on Windows XP.  My repository is on a Gentoo Linux box, running
version 1.4.6 (r28521) of subversion.

I created a new repository, and tried to import a new set of files
into it, but I get this error:

     Error Expected format '3' of repository; found format '5'

Sure enough, the "format" file in the repository subdirectory is, in
fact "5".

How do I fix this?  The only option in 'svnadmin create' is --pre-1.4-
compatible, which seems wrong because I've been running 1.4 forever.

Any help?

Thx... HH
Milen A. Radev | 1 Mar 04:02 2008
Picon

Re: Expected format '3' of repository; found format '5'

On 01/03/2008, Curunir Wolf <harryholt@...> wrote:
> I can't believe nobody else is having this problem, but I can't seem
>  to find a solution.  I'm running Tortoise SVN version 1.4.8, build
>  12137 on Windows XP.  My repository is on a Gentoo Linux box, running
>  version 1.4.6 (r28521) of subversion.
>
>  I created a new repository, and tried to import a new set of files
>  into it, but I get this error:
>
>      Error Expected format '3' of repository; found format '5'
>
>  Sure enough, the "format" file in the repository subdirectory is, in
>  fact "5".
>
>  How do I fix this?  The only option in 'svnadmin create' is --pre-1.4-
>  compatible, which seems wrong because I've been running 1.4 forever.
>
>  Any help?

Most probably you've created the repository with version 1.4.x and now
you're trying to use it (import files etc) with version 1.3.x (more
info hre - http://svn.collab.net/repos/svn/trunk/notes/repos_upgrade_HOWTO).

--

-- 
Milen A. Radev
Stefan Küng | 1 Mar 17:17 2008
Picon

TortoiseSVN 1.5.0-alpha1 released

We've released TortoiseSVN 1.5.0-alpha1.

Since there are a lot of changes and new features in the upcoming 1.5.0 
release, we first release an alpha version for adventurous people to 
test. Even though this release is pretty stable, you most likely will 
encounter bugs in it. Please report them back to our mailing list so we 
can get the final release as stable as possible.

You can download the alpha1 release from here:
http://tortoisesvn.net/node/310

Please make sure you read the compatibility concerns on that page before 
you install the alpha1 release!

Stefan

--

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net

Joe Contreras | 1 Mar 18:04 2008
Picon
Picon

Help for checking out files on a network drive

Hi,

I'm not sure if this is where you post help for TortoiseSVN 1.4.2.

I'm having issues setting up the checkout - checkin process for TortoiseSVN.
My scenario.

I have a code base in classic ASP that requires version control.  I have SF
Subversion as the repository and I'm using TortoiseSVN 1.4.2 as the client.

The issue; we have a team that requires these files to be on a shared
network drive everyone can check them out from the same drive and lock the
necessary files and unlock them and commit them from this network drive.
How do we do that using TortoiseSVN?  My understanding is that everyone can
checkout the entire repository and only if you are using that file do you
need to lock it to avoid conflicts with other team members.  Once I get this
figured out we'll be up and running.  I think this is a cool product and
want to utilize it accordingly.  I've used VSS in the past for version
control however I've never used TortoiseSVN.

All help will be appreciated greatly.

Thank You
Ron Wilson | 1 Mar 21:13 2008
Picon

Re: Help for checking out files on a network drive

From my own experience, if you already have a repository being managed
by a SVN server (svnserve or mod_svn), you must have all SVN clients
access that repository via the server.

This is the recomended way, anyway.

If you absolutely must allow some SVN clients to directly access the
repository via a file share, then all of the SVN clients must access
it via the file share.

Also, the repositiory must be in FSFS format.

On 3/1/08, Joe Contreras <jscontreras@...> wrote:
> Hi,
>
> I'm not sure if this is where you post help for TortoiseSVN 1.4.2.
>
> I'm having issues setting up the checkout - checkin process for TortoiseSVN.
> My scenario.
>
> I have a code base in classic ASP that requires version control.  I have SF
> Subversion as the repository and I'm using TortoiseSVN 1.4.2 as the client.
>
> The issue; we have a team that requires these files to be on a shared
> network drive everyone can check them out from the same drive and lock the
> necessary files and unlock them and commit them from this network drive.
> How do we do that using TortoiseSVN?  My understanding is that everyone can
> checkout the entire repository and only if you are using that file do you
> need to lock it to avoid conflicts with other team members.  Once I get this
> figured out we'll be up and running.  I think this is a cool product and
(Continue reading)

Simon Large | 2 Mar 00:18 2008

Re: Help for checking out files on a network drive

On 01/03/2008, Joe Contreras <jscontreras@...> wrote:
>  I'm not sure if this is where you post help for TortoiseSVN 1.4.2.

Yes it is, although we are now on 1.4.8

>  I'm having issues setting up the checkout - checkin process for TortoiseSVN.
>  My scenario.
>
>  I have a code base in classic ASP that requires version control.  I have SF
>  Subversion as the repository and I'm using TortoiseSVN 1.4.2 as the client.

You mean the repository is on SourceForge, or you are using a
subversion downloaded from SF and installed on a local machine?

>  The issue; we have a team that requires these files to be on a shared
>  network drive everyone can check them out from the same drive and lock the
>  necessary files and unlock them and commit them from this network drive.

Now you're really getting confused. You must distinguish between the
repository (the master database that stores all revision information)
and the working copy, otherwise known as a sandbox or developer
checkout.

Each developer should checkout their own working copy on their local
hard drive. Having a shared working copy is not a good idea at all and
*will* cause problems. You will find people overwriting each others
changes and you will lose all the protection benefits that version
control gives you.

>  How do we do that using TortoiseSVN?  My understanding is that everyone can
(Continue reading)

wazz | 2 Mar 05:08 2008
Picon

is this possible ?


I would like to know if it is possible to generate automatically a versioning
number such as 1.0.12, 1.0.13,.... and to store it inside a file ? If so,
can it be incremented automatically ?

I don't know anything about TortoiseSVN, but I need to find a way to create
a number, like above, automatically when I commit files on the server.

Thank you
--

-- 
View this message in context: http://www.nabble.com/is-this-possible---tp15784110p15784110.html
Sent from the tortoisesvn - users mailing list archive at Nabble.com.
Tom Blough | 2 Mar 13:47 2008

Bug - TortoiseSVN 1.5.0-alpha1

Stefan,

Standard install of 1.5.0-alpha1 on XPSP2.  Open the repo browser and click
help.  Result is dialog "failed to launch help/OK".

Tom

> -----Original Message-----
> From: Stefan Küng [mailto:tortoisesvn@...] 
> Sent: Sunday, March 02, 2008 12:18 AM
> To: TortoiseSVN Dev; users@...
> Subject: TortoiseSVN 1.5.0-alpha1 released
> 
> 
> We've released TortoiseSVN 1.5.0-alpha1.
> 
> Since there are a lot of changes and new features in the 
> upcoming 1.5.0 
> release, we first release an alpha version for adventurous people to 
> test. Even though this release is pretty stable, you most likely will 
> encounter bugs in it. Please report them back to our mailing 
> list so we 
> can get the final release as stable as possible.
> 
> You can download the alpha1 release from here: 
> http://tortoisesvn.net/node/310
> 
> Please make sure you read the compatibility concerns on that 
> page before 
> you install the alpha1 release!
(Continue reading)

VirGin | 2 Mar 14:51 2008
Picon

Single Server, Multiple Repositories, Multiple Locations

Hola Folks,

Currently I have one repository that has several different projects. I
access the repository via svn:. SVN is running on one machine and the
repository is stored on another.

I would like to create multiple repositories on multiple machines but
access all of them via one server.

The -r command doesn't seem like it is going to work. At least I
haven't seen how it  will without other modifications.

How can I configure the server to serve repositories that are stored
on different machines, different drives and directories?

Thanx.

More Info:

Current Layout:
     - Server
          - Running SVN server.
          - Has a mapped drive to a location on another machine
          - Serves the repository stored on the other machine via the
mapped drive.
     - File Server 1
          - Has a single repository containing the projects.
          - Shares the directory so 'Server' can access it.

I'd like to create another repository on a different drive on 'File
(Continue reading)

Milen A. Radev | 2 Mar 16:02 2008
Picon

Re: Single Server, Multiple Repositories, Multiple Locations

On 02/03/2008, VirGin <virgin69@...> wrote:
> Hola Folks,
[...]

Wrong list - general and (especially) server-related SVN questions
should be posted to users at subversion.tigris.org.

--

-- 
Milen A. Radev

Gmane