The Linux client RPM that CollabNet provides ought to run OK on SuSE.
It comes with its own copies of dependencies and installs everything
into /opt/CollabNet_Subversion so it does not mess with any of the
RPM's you already have installed on your system.
Mark
On Sun, Nov 30, 2008 at 11:35 AM, David Weintraub <qazwart_at_gmail.com> wrote:
> Thanks for the quick response.
>
> I tried some testing just now on a backup of our repository, and
> everything seemed fine. I just want to make absolutely sure that I
> wouldn't be breaking our build system with an upgrade.
>
> I wish I could upgrade our build system to use Subversion 1.5, but too
> many things are running on that box to take it down and take it apart.
>
> I'll setup a Hudson build with a backup repository and make sure that
> Hudson doesn't complain about anything. I had to "upgrade" Hudson, so
> it would work with a Subversion 1.3 client. I want to make sure Hudson
> doesn't throw a fit if I do an upgrade.
>
> Otherwise, the "svnadmin upgrade" command worked well.
>
> --
> David Weintraub
> qazwart_at_gmail.com
>
>
>
> On Sun, Nov 30, 2008 at 11:27 AM, Mark Phippard <markphip_at_gmail.com> wrote:
>> There should not be anything to be concerned about. It will work fine
>> with a 1.3 client.
>>
>> Mark
>>
>>
>> On Sun, Nov 30, 2008 at 11:17 AM, David Weintraub <qazwart_at_gmail.com> wrote:
>>> I thought I had everything setup nice and clean. I have Subversion 1.5
>>> installed as my server, and finally got the last project converted
>>> over to Subversion.
>>> However, our build machine is using Subversion 1.3. It's an old SUSE
>>> Linux installation, and we simply couldn't get a more recent revision
>>> of Subversion to work on it. Not without updating Apache, APR, Neon,
>>> and who knows what else. Heck, it took us a week just to get
>>> Subversion 1.3 running, so upgrading isn't an option right now.
>>> Now, here's the problem: Everything seemed to work our nicely. Our
>>> build machine (running 1.3) is able via Hudson to checkout the code
>>> and do a build. It can do labeling via Hudson. It looks good.
>>> However, one of our developers noticed that our Server (running
>>> Subversion 1.5) has only DB format 2 on it. He tried a "svn log -g"
>>> and got the following error message:
>>>
>>> svn: Querying mergeinfo requires version 3 of the FSFS filesystem
>>> schema; filesystem '/solbright/svn_repositories/dev/db' uses only
>>> version 2.
>>>
>>> I can run svnadmin upgrade on the Subversion repository, and in
>>> seconds, get it to be upgraded to db format version 3. I've tried this
>>> on a back of our server with no problems.
>>>
>>> The question I have are possible side effects on our build server
>>> running Subversion 1.3. I know that this build server can't do merge
>>> tracking, but I don't really need to worry about that. I simply want
>>> to know if there would be any side effect upgrading our repository to
>>> DB format version 3. All this subversion client has to do is checkout
>>> the code, work with Hudson, and do labeling. There's no real
>>> development that takes place on it.
>>>
>>> From what limited testing I'm doing, it all looks okay. I just want
>>> some confirmation that I won't be blowing everything up if I do the
>>> upgrade.
>>>
>>> --
>>> David Weintraub
>>> qazwart_at_gmail.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
>>> For additional commands, e-mail: users-help_at_subversion.tigris.org
>>>
>>>
>>
>>
>>
>> --
>> Thanks
>>
>> Mark Phippard
>> http://markphip.blogspot.com/
>>
>
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-30 17:52:44 CET