On 4/9/07, Stefan Küng <firstname.lastname@example.org> wrote:
> Larry Martell wrote:
> >> * check the SAMBA permissions. If you don't have full access, fetching
> >> the status doesn't work.
> > I do have full access.
> Something still must be wrong. See below
> >> * what does the "check for modifications" dialog show? Does it show the
> >> correct status of the files/folders? If not, then it's definitely a
> >> SAMBA issue and I can't really help you there.
> > When I first bring up "check for modifications" it says "File list is
> > empty"
> > But if I click on "Check Repository" it then show the correct status for
> > everything. But even after that the icons and menus are still not correct.
> If the file list is initially empty, then that means that either you
> don't have any modified files in your working copy, or the status
> couldn't be fetched.
I'm sorry, perhaps I was not completely clear in my earlier messages. When
files are modified in a local working copy, then the icons and menus are
correct. It's only when a file has been changed in the repository that the
icons and menus are not correct.
> You get some information after clicking on "Check Repository", but that
> just indicates that the connection to the repository is ok. Because you
> only see the status of the repository at that point. If you look closer,
> you'll see that the 'status' columns still don't show you the correct
> status, only the 'remote status' columns.
> There must be something wrong with your SAMBA setup. Subversion can't
> fetch the status of your working copy. Or your working copy is corrupt.
> * do a fresh checkout and try again
> * use the SVN command line client, do an 'svn st -v' and check its
> output. You might get an error message which might give you more hints
> about what exactly is wrong with your working copy/setup.
svn st -v does not give any errors.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Apr 9 16:02:24 2007