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.
Hi all, We tested the same RPM package in another server, with Red Hat EL v4 and it worked as expected. Unfortunately we cannot update our development server from Red Hat EL v3 to v4 because there are other services that we cannot stop for a server upgrade. I'd like to receive some directions on how to build CVSNT 2.5.03.2151. We built it yesterday but the server gives this warning message when commiting a file: cvs commit -f -m "no message" -- Document01.doc (in directory E:\test) Checking in Document01.doc; /test_repository/test_module/Document01.doc,v <-- Document01.doc cvs commit: warning: unrecognized response `free(): invalid pointer 0x9f482f0!' from cvs server new revision: 1.3; previous revision: 1.2 done The problem seems to be related to differences between the library versions we have in our system and the ones expected by CVSNT 2.5.03.2151. Tony, can you point (or give) us to some directions on what are the library versions required to build CVSNT 2.5.03.2151? Thanks in advance, Daniel Daniel Lapolla wrote: > Just forgot to mention: the server operating system is Linux Red Hat > EL3, Kernel 2.4.21-20 SMP. > > CVSNT server was installed from the RPM available from cvsnt.com. > > I did the same tests with a 2.5.03.2151 CVSNT Windows server in my > workstation and there is no such problem. > > Any ideas? > > Thanks > > Daniel Lapolla wrote: >> Hi, >> >> We have several binary files that were added with -kB option (binary >> deltas). >> >> They were added/modified when the server was still build 1976. We did >> a test here and with a 2151 server running with a copy of the >> repository we got the following error: >> >> cvs -z9 commit -f -m "test message" -- SomeFile.doc (in directory >> E:\Mymodule\Documents) >> Checking in SomeFile.doc; >> cvs [commit aborted]: end of file from server (consult above messages >> if any) >> >> The problem occurs with 2.0.51d and 2.5.03.2151 clients. >> >> Does someone had a similar problem already? Is there a known fix or >> workaround? >> >> TIA >> >> Daniel