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 Glen, They are *.dcu,v. We did have an older version before 2.0.51d possibly got corrupt then, because these particular modules were commited once and pretty much never used again. Yet in saying that I see that some .identcache,v files are also corrupt. I believe it is a BDS2006 file also binary, also missing CVSNT header and looking like garbage, don't know how it got corrupted. Luckily though (touch wood) all the files I have found so far shouldn't actually be in the CVS as they can get recreated by Delphi. Thank you very much for your help. I still love CVS for it's ease of use and fairly easy to understand. I have learnt new things today and I'm happy about that. Regards and thanks once again, Sean B Glen Starrett wrote: > Sean Bertinotti wrote: >> It appears that all the offending files I have found so far are *.dcu >> (Delphi Compiled Units) I am deleting them from the repository as they >> should not be in the CVS anyway. This is a binary file, so I am >> concerned that I will come across different binary files with the same >> problem. It will be a long night for me :P > > Are these files in your repository as *.dcu,v or just *.dcu? If they > don't have the ,v at the end then they shouldn't be in your repository > at all -- someone put them in there accidentally I bet. > >> I am now endeavoring to manually repair my modules using trace to >> identify the offending file, and deleting it from the repository. Do >> another checkout with trace and repeat steps :) Please let me know if >> this is alright to do. I have reverted to CVSNT 2.5.03 as it was >> running a lot faster than 2.4.03 on my machines. > > Just make sure you have a good backup of everything, and it's fine to > delete the bad ones. You can re-add good copies later if you find > anything that's corrupt that really should be there. > > If you're messing with a production repository then much more care will > be needed. > > Regards, >