Hi John,
Thanks for your reply.
I am sorry for my lack of clarity in my first email. Hopefully I can
address this.
OS: Linux (RHEL 3) (for clients, webserver and svnserve).
After I noticed this issue, I did try go to the webserver's workspace
and do the manual update. Typing svn update does not produce any error,
it just returns 'At revision <latest>'. So it appears, as far as it's
concerned, everything is updated. I ran an svn cleanup, and then tried
again, but it made no difference. The only way I could get it to
populate this new directory was to do the svn update <dir_name>.
RE: Recommendation #1
I do take the point that updating to the latest version is the way to
go, and I certainly will do this, post-project, but we're a little wary
of doing this now. I hope you understand.
My intention for posting here was to see if anyone recognized the issue
from before, or it at least sparks some recognition in the svn user
community.
RE: Recommendation #2
I have not ever played with post-commit scripts. They sound like a very
interesting idea - but for the simplicity of this mirror operation, I
thought they should be unnecessary.
Either way, the behavior of svn seems strange in this case.
This problem could affect users also if they were doing an svn update in
their workspace (I have seen this reported also, in 1 instance, and the
workaround was to remove the workspace directory, and update it again).
One thing I did try - I tried using a newer version of svn on the client
side (but did not upgrade the svn serve server), and it still did not
work.
I checked out your CPAN docs on SVN::Notify::Mirror. Thanks for the
link, it looks like something I could use.
Cheers,
John
-----Original Message-----
From: John Peacock [mailto:john.peacock_at_havurah-software.org]
Sent: Tuesday, February 12, 2008 8:07 AM
To: John Mcgrath
Cc: users_at_subversion.tigris.org
Subject: Re: svnupdate - some directories not being updated
> I am seeing a strange issue with svn - version 1.3.2, specifically
with
> the svn update command.
Recommendation #1 - upgrade to something more current (e.g. 1.4.6) on
both the client and server. There aren't going to be any fixes applied
to the 1.3.x branch (barring extremely serious security fixes). There
are few (if any) developers who still run such an old version, so you
are automatically limiting the number of people who can assist you.
> As these docs are web-based, we have a simple 'update script', which
> does nothing more than run an
>
> 'svn update' once every 5 mins in a particular directory on the
> webserver (i.e. a read-only workspace that the webserver points to ).
Recommendation #2 - use a real post-commit script, rather than some
time-based updates. Since you didn't tell us anything about your
environment (SVN server O/S, web server O/S, client O/S, etc), it's hard
for me to recommend anything specific. I did write SVN::Notify::Mirror*
specifically to make it very easy to create sophisticated post-commit
hooks.
> A user recently created a new sub-directory and checked it in:
>
> In the path docs/trunk/new_dir
>
What path do you have checked out on the web server?
>
> This sub-directory, and its contents were NOT however updated to the
> webservers workspace by the auto svn update.
>
> I cannot figure out why. All other subdirectories and files are auto
> populated, so why did this one not work?
What happened when you tried to manually run the `svn up` command in the
website's working copy (before you explicitly updated the new_dir)?
Basically, the narrative you have described has very little detail of
the kind needed for anyone to help to resolve this for you. What would
be best is a reproduction recipe: what you typed, what the software
responded, etc, so someone can try and recreate your issue. And of
course, you need to tell us a lot more than just the [outdated] version
of the Subversion software...
HTH
John
*) http://search.cpan.org/search?query=SVN-Notify-Mirror
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-12 17:50:30 CET