Re: SVN updating from Xcode. 3x the fail.
Re: SVN updating from Xcode. 3x the fail.
- Subject: Re: SVN updating from Xcode. 3x the fail.
- From: Joar Wingfors <email@hidden>
- Date: Mon, 02 Jun 2014 08:45:46 -0700
Hi Alex,
Your experience with SVN support in Xcode, as reported in your many emails to this list lately, is far worse than what I can remember hearing about from anyone else. There must be something in your environment that could explain that, but I'm not sure what. Please file bug reports so that we can figure that out. The first thing to do, and what we'd need in those bug reports, would be to compare with the output from the command line.
Files showing diffs / conflicts where nothing is seen in the editor sounds like whitespace / line endings. That should be easy enough to verify, and obvious enough that I'd imagine that you've ruled out / confirmed already? Another thing to check would be SVN properties ("metadata").
As far as performance goes, SVN support in Xcode should be just as fast as it is on the command line. If it is not, you should be filing bug reports. The time spent should be almost completely in IO.
Joar
On 2 jun 2014, at 07:28, Alex Zavatone <email@hidden> wrote:
> Xcode 5.1.1, Mac OS 10.8.5
>
> I just got in this morning with instructions to update our iOS project workspace.
>
> So, with the workspace open, I do that. I go to Source Control and select Update.
>
> Xcode first opens a comparison window with the message "No Editor".
>
> Finally getting used to this, I wait 30 seconds for something to appear.
>
> Finally in the left hand pane, a list of 20 files appear all with a U to the right of them.
>
> If I select any of the header, method or project files. Xcode shows the source of each file with the local on the left and the head as expected on the right. As expected, all the conflicts are marked in red in the scroll bar.
>
> Looking at each of the conflicts, I see that the lines marked as conflicts are exactly the same in my local copy and in the head on the SVN server.
>
> I tested this by copying each line and comparing each for equality and they are exactly the same.
>
> Why IS Xcode marking them as being in conflict then?
>
> This is the same for every one of the 20 files that are marked as needing an update.
>
> Now, of course, the Update button is grayed out. It's been grayed out for about 15 minutes now. I know this because I walked out to my car, came back, examined all of the lines that are supposed to be in conflict and typed this engrossing email
>
> Why does Xcode think that the entire project needs an update,
> why does Xcode mark files as needing updates when all the items that it sees as conflicts have no conflict at all,
> why does Xcode think the project needs an update and keeps the Update button grayed out?
>
> I've got two PhD's looking at the screen now (yeah, I have screenshots) with each one shaking their head.
>
> Everyone on our team has this exact same issue with Xcode's SVN support. (No, we can't change to Git, that's beyond our control.)
>
> 20 minutes now and Update is not yet enabled - for files that Xcode states need updates - for files that Xcode flags as having conflicts - for lines of code that are identical.
>
> Switching to the command line to see how long the update takes.
>
> Under a minute to switch directories and update all folders to version 61 from the command line.
>
> I can't believe that Apple lets Xcode ship with such horrible SVN support.
>
> Either fix SVN support it or pull it from Xcode. This is an utter disgrace and a massive waste of time for your developers.
>
>
>
>
>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden