[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Updating from 1.11.17 to 1.11.22
From: |
Mark D. Baushke |
Subject: |
Re: Updating from 1.11.17 to 1.11.22 |
Date: |
Wed, 01 Nov 2006 16:00:20 -0800 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Simon Renshaw <address@hidden> writes:
> The server where CVS is installed is running CentOS 4.4 (clone of Red
> Hat Enterprise 4) and it came with 1.11.17 installed (RPM called
> cvs-1.11.17-9.RHEL4).
The RHEL4 sources
ftp://rpmfind.net/linux/redhat/updates/enterprise/4AS/en/os/SRPMS/cvs-1.11.17-9.RHEL4.src.rpm
seem to have a lot of individual patches as well as the canonical
cvs-1.11.17.tar.bz2 sources:
cvs-1.11.17-CAN-2005-0753.patch
cvs-1.11.17-cvspass.patch
cvs-1.11.17-extzlib2.patch
cvs-1.11.17-repo.patch
cvs-1.11.17-sccs2rcs.patch
cvs-1.11.17.tar.bz2
cvs-1.11.17.tar.bz2.sig
cvs-1.11.19-tmp.patch
cvs-1.11.1p1-bs.patch
cvs-1.11.2-abortabort.patch
cvs-1.11.2-netbsd-tag.patch
cvs-1.11.5-extzlib.patch
You should take care that you do not depend on any of the patched
behaviors before going to the vanilla CVS source distribution.
> So if I want to update it to the latest stable version, I should remove
> the RPM and then build the source?
>
> Or can anybody suggest a place where I could download a RPM of the
> latest version?
rpmfind.net is a fairly good place to start looking for such things.
> I plan to move all my CVS data to another server before doing that.
>
> Thanks!
> Simon
Good luck,
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)
iD4DBQFFSTUTCg7APGsDnFERAoWuAJ9/0AGtAvvi78m6LsaTOZDLu7LWGwCXdPMN
kfWa6uP9i/PUjW0nIAMwag==
=78M6
-----END PGP SIGNATURE-----