[cvsnt] Changelogs availability and updating from 2.0.58->2.5.x

Ben bda20 at cam.ac.uk
Thu Jun 26 10:51:08 BST 2008

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

On Thu, 26 Jun 2008, Peter Crowther wrote:

> From: Ben
>> Hi there,
> Heh.  Hi Ben!

Peter!  What a place to run into you!

>> I note that there's a cvsnt- RPM available.  Is there a 
>> changelog for what's gone on since the version we currently have 
>> installed, and does it contain any gotchas which would preclude me simply 
>> doing an "rpm -Uvh" with the new version?
> A lot has changed, including a number of security fixes.  I don't have a 
> pointer to the change log handy... anyone else?!

Security fixes I can deal with.  Major changes in functionality leading to 
current repositories becoming corrupted and clients being no longer able to 
connect or losing history/state/anything else woe-inducing I can't.

> No major gotchas to my knowledge, but I'd wait for someone with more UNIX 
> knowledge than me to reply.  The general advice is to uninstall the old 
> version, then install the new one - not sure whether that's any different 
> with the DeadRat package manager.

Theoretically the 'U' in 'rpm -Uvh' should take care of that.

> Watch for the administrative files under CVSROOT.  It wouldn't entirely 
> surprise me if an RPM upgrade blasted them.

Hmm, the rpm shouldn't replace _anything_ in the CVSROOTs.  Or do we mean 
something different?  I see a CVSROOT under each repository I have.  Are you 
refering to something else within the OS's filesystem to do with where 
CVSNT itself is installed?

I note there are two new lines in the PServer xinetd configuration file 
according to http://www.cvsnt.org/wiki/InstallationLinux:

        log_type       = FILE /var/log/cvspserver
        env            = 'HOME=/cvs'

The first seems obvious.  The second I've altered to the base directory 
where all of my repositories are based.  I'm wondering if that's right. 
Obviously this isn't live yet because I haven't upgraded.

> Generally, those files are ones to watch.  Different versions have 
> different admin files, and it's sometimes most appropriate to let the 
> installer install fresh ones, then merge the content from the old files by 
> hand.  Not sure how much yours are customised - is CVSNT grabbing user 
> accounts from pam, or do you have accounts in the CVSNT passwd file?

CVSNT is authenticating using user account from a 'passwd' file in each 
repository's CVSROOT directory.  Connection is done using PServer.  What do 
you think it's going to change in the admin files?  I've done zero 
customisation of anything.  Which files would I customise anyway?

>> I assume a restart of xinetd would be in order given it appears we're 
>> running it in PServer mode with most users using the Eclipse plugin or 
>> WinCVS to connect.
> I suspect so, not least to restart the CVSNT lock server daemon.

That was _actually_ what I meant to type.  Honest.

>> Thanks for any information you can give me.
> As always, treat this with a pinch of salt!  It's a rapid response, but 
> not as thorough as you'd get from someone running the UNIX version.

We're in no real rush.  I was hoping to get it sorted today as I'm on 
vacation from the end of play today for a week (-:

Unix Support, MISD, University of Cambridge, England
Plugger of wire, typer of keyboard, imparter of Clue
         Life Is Short.          It's All Good.

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook