Old working copy format

Hi Christoph,

thank you for the answer.

On 6 Jan, pertzschc wrote:
> it depends from the subversion version of the used server:
>
> If server is at a version <1.4 then it uses the "old&quot; (xml)format.
> If server is at a version >=1.4.0 then it uses the "new&quot; (non-xml)format.
>;
> If you have working copies with the old format and the server
&gt; get an update to version >=1.4.0 SmartSVN will convert the working
&gt; copy to the new format, during the next synchronisation.

That can't be the whole truth. I used a server at a version <1.4 (by
protocol svn+ssh) and after I used SmartSVN 2.1.2 the working copy was
converted (so that an other older subversion client can't read the
working copy anymore).

I remember there was an option for SmartSVN to tell, that the working
copy should not be converted but I can't remember its name.

Dietmar

--
Dietmar Lippold, Institut VIS, Universität Stuttgart
Raum 1.461, Universitätsstraße 38, 70569 Stuttgart
Tel.: 0711 / 7816 - 435; Fax: 0711 / 7816 - 340
E-Mail: dietmar.lippold%40informatik.uni-stuttgart.de">dietmar.lippoldinformatik.uni-stuttgart.de

Messages in this topic (3) Reply (via web post) | Start a new topic

.

Hi Dietmar,

I think the option you're talking about is -Dsmartsvn.no-wc-upgrade=false.

--
Best regards,
Sebastien

2007/1/6, Dietmar Lippold < dietmar.lippold%40informatik.uni-stuttgart.de">dietmar.lippoldinformatik.uni-stuttgart.de&gt;:

>; I remember there was an option for SmartSVN to tell, that the working
&gt; copy should not be converted but I can't remember its name.
>;

[Non-text portions of this message have been removed]

Messages in this topic (4) Reply (via web post) | Start a new topic

.

Hi Sebastien,

On 6 Jan, Sebastien Daloz wrote:
&gt; I think the option you're talking about is -Dsmartsvn.no-wc-upgrade=false.

Yes, thanks, that was what I meant. The curious thing with the double
negation which stands for "no&quot;.

It works very well when I add that option in the script which starts
SmartSVN ("smartsvn.sh&quot; on Linux). As I read in the manual, that seems
to be the normal way for startup options. But that file is not
modifiable by a normal user. So I would like to suggest to the
developers to add a possibility to set that option (or an other startup
option) in an other way or to give it on the command line.

Dietmar

--
Dietmar Lippold, Institut VIS, Universität Stuttgart
Raum 1.461, Universitätsstraße 38, 70569 Stuttgart
Tel.: 0711 / 7816 - 435; Fax: 0711 / 7816 - 340
E-Mail: dietmar.lippold%40informatik.uni-stuttgart.de">dietmar.lippoldinformatik.uni-stuttgart.de

Messages in this topic (5) Reply (via web post) | Start a new topic

.

Hi Dietmar,

I had the same problem after upgrading to 2.1.2. There is a thread on
the mailing list with the subject that explains it a bit:

&quot;Re: [smartsvn] Is it possible to download a previous version?&quot;

<;quote>

Hi Lance,

You may still use version 2.1.x and set the VM option

-Dsmartsvn.no-wc-upgrade=false

to make SmartSVN not automatically upgrade working copies
(checking out
will produce still 1.4 working copies). Don't be confused by
"false",
previous property name was "smartsvn.wc-upgrade" ... However, we
give no
guarantee on how long this property will be supported.

Alternatively you may download version 2.0.7 from our website.

Windows installer:

http://www.syntevo.com/common/download-license.jsp?product=smartsvn&;file=smartsvn%2Fsmartsvn-win32-setup-jre-2_0_7.zip
<http://www.syntevo.com/common/download-license.jsp?product=smartsvn&;file=smartsvn%2Fsmartsvn-win32-setup-jre-2_0_7.zip>

Mac OS X:

http://www.syntevo.com/common/download-license.jsp?product=smartsvn&;file=smartsvn%2Fsmartsvn-macosx-2_0_7.tar.gz
<http://www.syntevo.com/common/download-license.jsp?product=smartsvn&;file=smartsvn%2Fsmartsvn-macosx-2_0_7.tar.gz>

Generic:

http://www.syntevo.com/common/download-license.jsp?product=smartsvn&;file=smartsvn%2Fsmartsvn-generic-2_0_7.tar.gz
<http://www.syntevo.com/common/download-license.jsp?product=smartsvn&;file=smartsvn%2Fsmartsvn-generic-2_0_7.tar.gz>

Please note, that we give no more maintenance/support for these
versions. So my suggestion is to upgrade your plug-in to version
1.4 as
soon as possible.

--
Best regards,
Marc Strapetz

</quote>

I added the property

-Dsmartsvn.no-wc-upgrade=false

to the VM arguments and it solved at least the one part of the problem:
upgrade of existing working copies.

Unfortunately I do not know of any way to make smartsvn use the old
client format on checkout while I still use a number of clients that do
not understand the new format.

Good Luck,
Henning

Dietmar Lippold wrote:
&gt;
> Hi Christoph,
>
>; thank you for the answer.
&gt;
> On 6 Jan, pertzschc wrote:
&gt; > it depends from the subversion version of the used server:
&gt; >
> > If server is at a version <1.4 then it uses the "old&quot; (xml)format.
> > If server is at a version >=1.4.0 then it uses the "new&quot;
> (non-xml)format.
>; >
> > If you have working copies with the old format and the server
&gt; > get an update to version >=1.4.0 SmartSVN will convert the working
&gt; > copy to the new format, during the next synchronisation.
>;
> That can't be the whole truth. I used a server at a version <1.4 (by
> protocol svn+ssh) and after I used SmartSVN 2.1.2 the working copy was
> converted (so that an other older subversion client can't read the
> working copy anymore).
>
> I remember there was an option for SmartSVN to tell, that the working
&gt; copy should not be converted but I can't remember its name.
>;
> Dietmar
&gt;
> --
> Dietmar Lippold, Institut VIS, Universität Stuttgart
> Raum 1.461, Universitätsstraße 38, 70569 Stuttgart
> Tel.: 0711 / 7816 - 435; Fax: 0711 / 7816 - 340
> E-Mail: dietmar.lippold%40informatik.uni-stuttgart.de">dietmar.lippoldinformatik.uni-stuttgart.de
> <mailto:dietmar.lippold%40informatik.uni-stuttgart.de>
>
>

[Non-text portions of this message have been removed]

Messages in this topic (6) Reply (via web post) | Start a new topic

.

Hi, is it maybe also possible to convert a new working copy format
back to the old one? thank you

Messages in this topic (7) Reply (via web post) | Start a new topic

.