Right - this error has nothing to do with the version of the server. You
must have accessed this working copy with a newer version of Subversion.

Justin

On Sat, Mar 20, 2010 at 8:33 PM, Moloney, Tim M <[email protected]>wrote:

>
> I believe that Justin is correct, but I've seen that error message also.
>
> I think that any version svn client can create a *new* working copy from
> any version svn server.
>
> However, if you check out a working copy with a newer svn client, then
> try to access that same working copy with an older svn client, you may
> see that error message, depending on what new features have been added.
>
> I ran into this problem when I had a newer svn client (via Eclipse
> Subversive) that created working copies that my system svn client (Red
> Hat 5) didn't understand.
>
>
> Tim Moloney                              I brought down the sky for you
> MRSL                                     but all you did was shrug.
> 2015 Cattlemen Road                            Audience Of One
> Sarasota, FL  34232                                  Appeal To Reason
> (941) 377-6775 x208                                        Rise Against
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of
> Sahoo
> Sent: Saturday, March 20, 2010 20:05
> To: [email protected]
> Subject: Felix workspace requires svn to be upgraded...
>
> [I have changed the subject]
>
> Justin,
>
> That used to be my understanding as well until I started encountering
> the following error while trying to update my Felix workspace using svn
> 1.5.4:
>
> ss141...@sahoo:/space/ss141213/WS/felix/trunk$ svn info
> svn: This client is too old to work with working copy '.'.  You need
> to get a newer Subversion client, or to downgrade this working copy.
> See http://subversion.tigris.org/faq.html#working-copy-format-change
> for details.
>
> Thanks,
> Sahoo
>
> Justin Edelson wrote:
> > Sahoo-
> > That's not how Subversion works. Every (released) version of the
> subversion
> > client will work with any (released) version of a subversion server.
> See
> > http://tortoisesvn.tigris.org/compatibility.html
> >
> > <http://tortoisesvn.tigris.org/compatibility.html>Justin
> >
> > On Sat, Mar 20, 2010 at 6:56 PM, Sahoo <[email protected]> wrote:
> >
> >
> >> Hi Felix,
> >>
> >> Because I have an older version of svn on my ubuntu 9.0.4 box, I am
> not
> >> able to check out Felix sources at this point of time. Ubuntu repo
> contains
> >> svn 1.5.4, but that's too old for svn workspace used by Felix. While
> I am
> >> trying to resolve that issue, I would like to try out the latest
> SNAPSHOT of
> >> web console. Would you mind making it available along with the
> sources in
> >> the SNAPSHOT repo?
> >>
> >> Thanks,
> >> Sahoo
> >>
> >>
> >>
> >> Felix Meschberger wrote:
> >>
> >>
> >>> Hi all
> >>>
> >>> Now that the major part of the JQuery UI rewrite has been done, we
> only
> >>> have a single issue left targeted for the Web Console 3.0.0 release
> [1].
> >>> There a number of other issues open for the Web Console [2] which
> are
> >>> not targeted yet.
> >>>
> >>> I propose to cut a release of the following bundles early this
> weekend
> >>> or early next week:
> >>>
> >>>   Web Console 3.0.0
> >>>   Event Plugin 1.0.2        (adapted for JQuery UI)
> >>>   Memory Usage Plugin 1.0.0 (new plugin)
> >>>   UPNP Plugin 1.0.0         (new plugin)
> >>>
> >>> So if you think that one of the open issues [2] should make it into
> the
> >>> 3.0.0 release, please tell us (and a patch makes things easier).
> >>>
> >>> Thanks and Regards
> >>> Felix
> >>>
> >>> [1] https://issues.apache.org/jira/browse/FELIX-2149
> >>> [2]
> >>>
> >>>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mod
> e=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=1231010
> 0&fixfor=-1&component=12312330<https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mod%0Ae=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=1231010%0A0&fixfor=-1&component=12312330>
> >>>
> >>>
> >>>
> >
> >
>

Reply via email to