Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: error (athena.apache.org: local policy)
From: John Maher <JohnM@rotair.com>
To: Andrew Reedick <Andrew.Reedick@cbeyond.net>, "users@subversion.apache.org"
	<users@subversion.apache.org>
Subject: RE: Strange behavior
Thread-Topic: Strange behavior
Thread-Index: 
 Ac6VJbiN2Ng5W3l4S6Gs0v8kwm1TGwAL0ckAAAeXBvD//9cagP/7/knggAhvdICAABDsgIAAP6sA//8pNHD//koy8P/8gz3A
Date: Tue, 13 Aug 2013 18:03:02 +0000
Message-ID: <910250F21FAA2A4E8F72DD21EA780766090608CA@VMJudi.corp.rotair.com>
References: <910250F21FAA2A4E8F72DD21EA7807660905D39A@VMJudi.corp.rotair.com>
 <293BE2C1-563D-4167-BA09-51619A34F794@ryandesign.com>
 <910250F21FAA2A4E8F72DD21EA7807660905D3D7@VMJudi.corp.rotair.com>
 <8FF220C7-1456-41B7-8FE9-36EDBE626423@ryandesign.com>
 <910250F21FAA2A4E8F72DD21EA7807660905D6F9@VMJudi.corp.rotair.com>
 <5209053F.8070305@gmx.us>
 <910250F21FAA2A4E8F72DD21EA7807660905D76A@VMJudi.corp.rotair.com>
 <205554392.20130812224306@am-soft.de>
 <910250F21FAA2A4E8F72DD21EA78076609060768@VMJudi.corp.rotair.com>
 <1B05D8F50421E24799AE93B03CC284BE01CA563B76@CRPMBX01.corp.cbeyond.net>
In-Reply-To: 
 <1B05D8F50421E24799AE93B03CC284BE01CA563B76@CRPMBX01.corp.cbeyond.net>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Thanks Andrew, I started going through your steps and discovered something.

My repository is called either iERP85_v2 or iERP85_V2.  Visual SVN reports =
the latter but the former works with the client.  Don't know which nor why =
one product chooses one over the other.  My mistake was assuming I make a m=
istake with the repository.  The mistake I actually made was trusting visua=
l svn server.  Although svn did report the smaller v it can be difficult to=
 notice.

So I created two branches for two new features I am working on. I'll see ho=
w they go.

Thanks again
JM

-----Original Message-----
From: Andrew Reedick [mailto:Andrew.Reedick@cbeyond.net]=20
Sent: Tuesday, August 13, 2013 10:27 AM
To: John Maher; users@subversion.apache.org
Subject: RE: Strange behavior


> -----Original Message-----
> From: John Maher [mailto:JohnM@rotair.com]
> Sent: Tuesday, August 13, 2013 9:40 AM
> To: Thorsten Sch=F6ning; users@subversion.apache.org
> Subject: RE: Strange behavior
>=20
> Hi Thorsten
>=20
> A good response to a less than good post.  People could take lessons=20
> from you.
>=20
> Actually, its been a frustrating week.  Sometimes subversion accepts=20
> the wrong slash in a path, other times it does not.  Sometimes it=20
> enforces case sensitivity in a url other times it does not.

Sounds like normal windows-unix interaction issues.  They're not that bad i=
f you have experience with UNIX systems.  In the Windows CMD shell, if you =
wrap your pathnames in double quotes, you can use forward slashes instead o=
f backslashes for directory separators, e.g. dir /s "c:/program files/subve=
rsion", which helps when feeding paths between CMD commands and svn command=
s.


>  Follow the
> book on how it instructs to import a project then it becomes=20
> impossible to merge and branch.

That's odd.  Very odd.  It's much more likely that you're not grokking some=
 paradigm or missed a step when creating the branch.  You might want to pos=
t your branch/merge test process (especially the commands) and have the lis=
t vet it.


> And now for the second time I must discard my repository along with=20
> all the history I've accumulated.  Yes you can say frustrating,=20
> bordering on maddening.

Why?  If you have a good initial import checked in, then create a new test =
branch, or even roll trunk back to the initial import.  Example:
Revision 10 of /trunk is your "200 commands" to import the initial baseline=
.
1. Create a new test branch from rev 10:  svn copy svn://server/trunk svn:/=
/server/branches/new_test_branch@10
Or if you want to roll trunk back to rev 10:
1. svn rm svn://server/trunk
2. svn copy svn://server/trunk@10 svn://server/trunk 3. create new test bra=
nch:  svn copy svn://server/trunk svn://server/branches/new_test_branch

The original trunk branch (with revisions 11+) is still available via peg r=
evisions, but peg revisions are a topic for later.

Or if you really want a fresh repo, then you can use 'svn export -r' to exp=
ort the initial working baseline and then import those files into your new =
test repository.  Meaning, if revision 10 represents your initial "200 comm=
ands" of importing files, then export revision 10 using 'svn export -r 10 .=
..'.  This lets you start a new repo without having to re-do the import fro=
m scratch.  I would tell you about 'svnadmin dump', but given your current =
mental state, that's probably not a good idea.

>=20
> I got a good laugh from:
> "Of course it can, just copy your 200 commands line by line one after=20
> another into a batch file."

I know it was a humorous comment, but...


Anyway, dealing with new software with new paradigms/assumptions can be ver=
y frustrating (e.g. going from ClearCase to 1.3 SVN, *grrrr*) but you need =
to take a step back and relax.  Importing and branching and merging in svn =
1.8 really isn't (shouldn't be) that difficult.  Plus, svn 1.8 is pretty ro=
bust and a mature product, so you shouldn't be fighting with it that much.
=20
Good luck, and keep up the perseverance.  "That which doesn't kill you, pro=
bably leaves you crippled and weak" (or something to that effect.)