Joe Schaefer writes: > Theo Van Dinter <[EMAIL PROTECTED]> writes: > > So it appears someone has messed up the SVN install on the zone. This is > > breaking the SpamAssassin zone's nightly cronjobs since "svn" upgraded the > > working copies to 1.4, and then the 1.1.4 binaries can't use them. :(
Is this why the buildbots all started failing? I assumed that was another certificate change, based on the logs. (This is better news, since svn 1.4 means we get some good new SVN features I was looking for. ;) > Can you change you PATH to use /opt/subversion-1.4.3/bin instead > of /opt/subversion-1.1.4/bin ? This should be possible, but will take some work... there are a lot of independent scripts/cron jobs that use SVN. :( A common old Solaris pattern was to maintain e.g. /opt/subversion as a link to /opt/subversion-1.X.Y , and update *that* on upgrades to avoid this problem. It might be worth doing that on /opt. (update:) ah, I see it: /opt/subversion-current. Is it safe to use that? In the meantime, SpamAssassin devs: I'll institute a global "envs" file that sets the PATH appropriately for all our scripts and user logins on our zone. (I'll put it in /etc/profile if we have write perms on that.) Also, it may be worth reverting the change to /opt/subversion-1.1.4/bin/svn : lrwxrwxrwx 1 1327 other 29 Feb 25 08:16 /opt/subversion-1.1.4/bin/svn -> /opt/subversion-1.4.3/bin/svn* that still seems odd, as Theo noted. --j.
