subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nico Kadel-Garcia <nka...@gmail.com>
Subject Re: Upgrading from 1.6.5 (Fedora) to 1.6.16 (built from source)
Date Wed, 09 Mar 2011 04:08:39 GMT
On Tue, Mar 8, 2011 at 6:12 PM, Marco Maccaferri <macca@maccasoft.com> wrote:
> On 07/03/2011 22:11 Jim Garrison ha scritto:
>
>> The last version available on the Fedora update site
>> for my system (Fedora 10) is 1.6.5, and I need the fixes
>> for Tree Conflict resolution that shipped in 1.6.6 and
>> later versions.
>>
>> Is there anything special to upgrading other than building
>> 1.6.16 from source, uninstalling the Fedora svn RPM and
>> hooking up Apache and the repository to the new version?
>
> Just install the Fedora 10 source RPM and replace the source package with
> the one downloaded from the subversion site (and change the version numbers
> in the specs file accordingly), rebuild all and you'll have a complete set
> of RPMs ready to update with yum localupdate.

You *wish*. Unless you've tested it, there may have been slight but
significant build structure changes. This is precisely what I've
encountered in the 1.6.15 to 1.6.16 upgrades for RPMforge building,
and it's quite frustrating. The "rpath" patch, for example, is now
rejected.

Please don't tell unsuspecting developers that such a complex project
is "plug and play" compatible. While it's often true, Subversion is
one of the projects where it is most likely not to be true due to its
extensive integration of separate components such as swig, neon, SSL,
WebDAV, Apache, Python, and SSH. Don't *start* me on the Python
dependencies.

Mime
View raw message