On Wed, 2007-01-17 at 02:53 +0100, Michael Biebl wrote:
> Ross Boylan wrote:
....
> > I was able to reproduce this using the following steps.
> > [EMAIL PROTECTED]:~$ mkdir test1
> > [EMAIL PROTECTED]:~$ date; svn mkdir http://localhost/svn/scratch -m "play 
> > area"
> > Tue Jan 16 17:14:15 PST 2007
> > 
> > Committed revision 708.
> > [EMAIL PROTECTED]:~$ date; svn mkdir http://localhost/svn/scratch/test1 -m
> > "scratch project"
> > Tue Jan 16 17:14:39 PST 2007
> > 
> > Committed revision 709.
> > [EMAIL PROTECTED]:~$ svn co http://localhost/svn/scratch/test1
> > Checked out revision 709.
> > [EMAIL PROTECTED]:~$ kdesvn &
> > 
> > I opened test1 (the work area in kdesvn) and then created a file silly.c
> > in that directory using an editor (i.e., not in kdesvn).  kdesvn does
> > not show it.
> > 
> > I open another copy of kdesvn; it does show silly.c.  Using that copy, I
> > add the file and commit it.  It still doesn't show up in the first
> > window.  I did an update in the first window; the file still doesn't
> > show.
> 
> I can't reproduce this behaviour.
> When I open a workspace in kdesvn and add a file in there from outside
> (e.g. "touch test.c" on the console), kdesvn immediately shows this file
> as unversioned.
> No need to hit refresh or something else.
> So, theres definitely something wrong with your setup.
> Do you perhaps have installed your own kernel (not the stock Debian one)
> without dnotify/inotify support?

No, it's a stock kernel: 
# uname -a
Linux iron 2.6.17-2-k7 #1 SMP Wed Sep 13 17:18:46 UTC 2006 i686
GNU/Linux
ii  linux-image-2.6.17-2-k7     2.6.17-9       Linux 2.6.17 image on AMD
K7

Hmm, 2.6.18 is installed, but either I haven't rebooted or I need to
update something.

Could the problem be further up the stack, e.g. fam?  I vaguely remember
having some applications with slightly oddball fam requirements.
# dpkg -l '*fam*' | grep ii
ii  libfam0                                      2.7.0-12
The fam package is not installed.

> 
> > 
> > BTW I was also a bit surprised that when I File | open and entered
> > "test1" in the dialog that came up I got "could not open url test1".  I
> > was able to open it by clicking on the folder icon and selecting the
> > directory.  Entering file:://test1 (or various variations of that) also
> > didn't work.
> 
> This also works. You can either open local repositories or workspaces.
> The correct syntax is:
> file:///path/to/workspace/or/repository (note the *three* slashes)
> 
> Michael
> 
> 
-- 
Ross Boylan                                      wk:  (415) 514-8146
185 Berry St #5700                               [EMAIL PROTECTED]
Dept of Epidemiology and Biostatistics           fax: (415) 514-8150
University of California, San Francisco
San Francisco, CA 94107-1739                     hm:  (415) 550-1062



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to