Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
5. If you are using CTM to receive the "*,v" files and then using the "cvs" command to check out your source tree, then I don't know whether you need to delete your ",v" files and replace them or not. You do need to delete your ,v files in this case (only for the crypto dirs). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
In article [EMAIL PROTECTED], Sheldon Hearn [EMAIL PROTECTED] wrote: Warner, Mark says that this applies if you used CTM to get cvs's ,v files, not CTM. Also, he clarified the last sentence for me, by saying that it's the crypto ,v files that need to be removed and not the checked out crypto files. There has been a whole lot of confusing info floating around here. Let me try to straighten this out. 1. If you are using CVSup in checkout mode, you don't have a problem. Go away and don't read any more of this. :-) 2. If in the past you have been getting your crypto files from the US or Canada, you don't have a problem. Go away and don't read any more of this. 3. If you are running a CVSup mirror site, you don't have a problem. Go away and don't read any more of this. 4. If you use CVSup to fetch the "*,v" files and then use the "cvs" command to check out your source tree, then you need to delete the *checked out sources* in these trees: src/crypto src/eBones src/secure src/sys/crypto Then check out these sources again using the "cvs" command. Do NOT delete your "*,v" files -- they are perfectly fine. 5. If you are using CTM to receive the "*,v" files and then using the "cvs" command to check out your source tree, then I don't know whether you need to delete your ",v" files and replace them or not. Hopefully Mark will clarify this if he hasn't already done so. But you definitely DO need to delete your *checked out sources* in these trees: src/crypto src/eBones src/secure src/sys/crypto Then check out these sources again using the "cvs" command. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
In article [EMAIL PROTECTED], Udo Erdelhoff [EMAIL PROTECTED] wrote: What about the non-US cvsup mirrors? Mirror sites don't have a problem, and they shouldn't do anything special. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
On Thu, 13 Jul 2000 19:19:48 +0200, Mark Murray wrote: 2711: If you used to get your crypto files from internat, AND you used cvsup to get cvs' ,v files, then the latest changes to the source collections will impact you. You will need to remove all the crypto files and start over. Warner, Mark says that this applies if you used CTM to get cvs's ,v files, not CTM. Also, he clarified the last sentence for me, by saying that it's the crypto ,v files that need to be removed and not the checked out crypto files. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
On Fri, 14 Jul 2000, Sheldon Hearn wrote: : : :On Thu, 13 Jul 2000 19:19:48 +0200, Mark Murray wrote: : : 2711: : If you used to get your crypto files from internat, AND you : used cvsup to get cvs' ,v files, then the latest changes : to the source collections will impact you. You will need to : remove all the crypto files and start over. : :Warner, Mark says that this applies if you used CTM to get cvs's ,v :files, not CTM. Also, he clarified the last sentence for me, by saying Should this read "used CTM ... not CVS" or "used CVS ... not CTM"? DAvid To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
On Fri, 14 Jul 2000 07:36:38 EST, David Scheidt wrote: :Warner, Mark says that this applies if you used CTM to get cvs's ,v :files, not CTM. Also, he clarified the last sentence for me, by saying Should this read "used CTM ... not CVS" or "used CVS ... not CTM"? Argh, what is it about this one? :-) That should have read: Warner, Mark says that this applies if you used CTM and not CVSup to get cvs's ,v files. Sorry, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
How can I tell if I need to nuke my crypto files? Sounds like I should have this problem but it doen't look like I do. I looked through the commits for the past few days searching for crypto, and I have all of the files that were commited. (secure/lib/libcrypto/Makefile Makefile.inc from earlier today crypto/openssh/ readconf.c, servconf.c, ssh_config, sshd.8, /telnet/libtelnet/auth.c from 7/11/00) thanks, -Charlie On Wed, Jul 12, 2000 at 03:05:25PM +0100, Brian Somers wrote: I haven't looked into it too deeply yet because of other source tree problems, but if you used to get your crypto ,v files from internat, you will suffer some funny problems unless you nuke the old checked-out files. My apologies if this is old news, but I see nothing in UPDATING. The problem occurs when you cvsup the new crypto-in-src-all sources and replace RCS files with different contents and the same version number. cvs update/checkout compares the repo version number against the checked out version number and considers the file an ``M'' (modified source). The file isn't updated and your world gets corrupted. This is probably a candidate for UPDATING. -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Charles Anderson[EMAIL PROTECTED] No quote, no nothin' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
On Fri, Jul 14, 2000 at 01:56:31PM +0200, Sheldon Hearn wrote: Also, he clarified the last sentence for me, by saying that it's the crypto ,v files that need to be removed and not the checked out crypto files. What about the non-US cvsup mirrors? Most of them used cvsup to mirror the crypto distributions from internat. Does this mean that these mirrors have to nuke theier local copies (of the crypto files), too? That would be a major problem for all users of these mirrors. They would have to wait until "their" mirror fixed it's copy... Is it possible to check if a repository is affected? Something along the lines of "/home/ncvs/src/crypto/foo.c should have revision bar, last commit by ... on ..., the md5 should be ..." /s/Udo -- "People who claim Windows in superior to Unix are the same people who'd argue that you better use your hand instead of toilet paper to wipe your ass. I can hear them now - 'It's colourful and it's intuitive and easy to use and even a child could do it.'". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
On Thu, 13 Jul 2000 19:19:48 +0200, Mark Murray wrote: 2711: If you used to get your crypto files from internat, AND you used cvsup to get cvs' ,v files, then the latest changes to the source collections will impact you. You will need to remove all the crypto files and start over. Warner, Mark says that this applies if you used CTM to get cvs's ,v files, not CTM. Also, he clarified the last sentence for me, by saying that it's the crypto ,v files that need to be removed and not the checked out crypto files. It applies if you overwrite your ,v files with the src-all ones, whether by CTM or cvsup. ``cvs checkout'' will compare the checked out version with the repo version and think it has nothing to do, emitting M src/crypto/whatever Ciao, Sheldon. -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
cd /usr/src/whereever cvs diff or just check your ``cvs checkout'' output for lines beginning with M. How can I tell if I need to nuke my crypto files? Sounds like I should have this problem but it doen't look like I do. I looked through the commits for the past few days searching for crypto, and I have all of the files that were commited. (secure/lib/libcrypto/Makefile Makefile.inc from earlier today crypto/openssh/ readconf.c, servconf.c, ssh_config, sshd.8, /telnet/libtelnet/auth.c from 7/11/00) thanks, -Charlie On Wed, Jul 12, 2000 at 03:05:25PM +0100, Brian Somers wrote: I haven't looked into it too deeply yet because of other source tree problems, but if you used to get your crypto ,v files from internat, you will suffer some funny problems unless you nuke the old checked-out files. My apologies if this is old news, but I see nothing in UPDATING. The problem occurs when you cvsup the new crypto-in-src-all sources and replace RCS files with different contents and the same version number. cvs update/checkout compares the repo version number against the checked out version number and considers the file an ``M'' (modified source). The file isn't updated and your world gets corrupted. This is probably a candidate for UPDATING. [.] -- Charles Anderson [EMAIL PROTECTED] No quote, no nothin' -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
In message [EMAIL PROTECTED] John Polstra writes: : This is probably a candidate for UPDATING. : : That wouldn't hurt. But it actually affects _all_ branches, I : believe. So in a way, UPDATING doesn't cover enough ground. Does anybody have any text that is better than the following? 2711: If you used to get your crypto files from internat, AND you used cvsup to get cvs' ,v files, then the latest changes to the source collections will impact you. You will need to remove all the crypto files and start over. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
"Warner" == Warner Losh [EMAIL PROTECTED] writes: Warner In message [EMAIL PROTECTED] John Polstra writes: Warner : This is probably a candidate for UPDATING. Warner : Warner : That wouldn't hurt. But it actually affects _all_ branches, I Warner : believe. So in a way, UPDATING doesn't cover enough ground. Warner Does anybody have any text that is better than the following? Warner 2711: Warner If you used to get your crypto files from internat, AND you Warner used cvsup to get cvs' ,v files, then the latest changes Warner to the source collections will impact you. You will need to Warner remove all the crypto files and start over. My understanding was that the problem was cvsuping the crypto ,v files from internat and then using cvs to get a source tree, i.e I was under the impression that cvsup in checkout mode was ok. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
In message [EMAIL PROTECTED] Martin Hopkins writes: : "Warner" == Warner Losh [EMAIL PROTECTED] writes: : : Warner In message [EMAIL PROTECTED] John Polstra :writes: : Warner : This is probably a candidate for UPDATING. : Warner : : Warner : That wouldn't hurt. But it actually affects _all_ branches, I : Warner : believe. So in a way, UPDATING doesn't cover enough ground. : : Warner Does anybody have any text that is better than the following? : Warner 2711: : Warner If you used to get your crypto files from internat, AND you : Warner used cvsup to get cvs' ,v files, then the latest changes : Warner to the source collections will impact you. You will need to : Warner remove all the crypto files and start over. : : My understanding was that the problem was cvsuping the crypto ,v : files from internat and then using cvs to get a source tree, i.e I was : under the impression that cvsup in checkout mode was ok. Do you have a suggested better text? I thought I said that. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
In message [EMAIL PROTECTED] John Polstra writes: : This is probably a candidate for UPDATING. : : That wouldn't hurt. But it actually affects _all_ branches, I : believe. So in a way, UPDATING doesn't cover enough ground. Does anybody have any text that is better than the following? 2711: If you used to get your crypto files from internat, AND you used cvsup to get cvs' ,v files, then the latest changes to the source collections will impact you. You will need to remove all the crypto files and start over. Maybe add the directories it will impact; crc/crypto, src/sys/crypto, src/eBones, src/secure. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
Warner In message [EMAIL PROTECTED] Martin Hopkins writes: Warner : "Warner" == Warner Losh [EMAIL PROTECTED] writes: Warner : Warner : Warner In message [EMAIL PROTECTED] John Polstra writes: Warner : Warner : This is probably a candidate for UPDATING. Warner : Warner : Warner : Warner : That wouldn't hurt. But it actually affects _all_ branches, I Warner : Warner : believe. So in a way, UPDATING doesn't cover enough ground. Warner : Warner : Warner Does anybody have any text that is better than the following? Warner : Warner 2711: Warner : Warner If you used to get your crypto files from internat, AND you Warner : Warner used cvsup to get cvs' ,v files, then the latest changes Warner : Warner to the source collections will impact you. You will need to Warner : Warner remove all the crypto files and start over. Warner : Warner : My understanding was that the problem was cvsuping the crypto ,v Warner : files from internat and then using cvs to get a source tree, i.e I was Warner : under the impression that cvsup in checkout mode was ok. Warner Do you have a suggested better text? I thought I said that. How about... If you used to mirror the crypto portion of the repository from internat AND used cvs to check out crypto sources from your local repository then the recent changes to the source collections will impact you. You will need to remove all your crypto sources (e.g cvs release -d crypto) and start over. Comments Brian? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
"Mark" == Mark Murray [EMAIL PROTECTED] writes: In message [EMAIL PROTECTED] John Polstra writes: : This is probably a candidate for UPDATING. : : That wouldn't hurt. But it actually affects _all_ branches, I : believe. So in a way, UPDATING doesn't cover enough ground. Does anybody have any text that is better than the following? 2711: If you used to get your crypto files from internat, AND you used cvsup to get cvs' ,v files, then the latest changes to the source collections will impact you. You will need to remove all the crypto files and start over. Mark Maybe add the directories it will impact; crc/crypto, src/sys/crypto, src/eBones, src/secure. Agreed. Reading this I just realised I missed the src-sys-crypto collection in my proposed text. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
"Mark" == Mark Murray [EMAIL PROTECTED] writes: In message [EMAIL PROTECTED] John Polstra writes: : This is probably a candidate for UPDATING. : : That wouldn't hurt. But it actually affects _all_ branches, I : believe. So in a way, UPDATING doesn't cover enough ground. Does anybody have any text that is better than the following? 2711: If you used to get your crypto files from internat, AND you used cvsup to get cvs' ,v files, then the latest changes to the source collections will impact you. You will need to remove all the crypto files and start over. Mark Maybe add the directories it will impact; crc/crypto, src/sys/crypto, src/eBones, src/secure. Agreed. Reading this I just realised I missed the src-sys-crypto collection in my proposed text. And I forgot eBones secure ! I also never knew about ``cvs release''. I did a rm -fr and then removed the entry from CVS/Entries :-/ Martin -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
**HEADS UP** if you used to cvsup the crypto repo from internat !
I haven't looked into it too deeply yet because of other source tree problems, but if you used to get your crypto ,v files from internat, you will suffer some funny problems unless you nuke the old checked-out files. My apologies if this is old news, but I see nothing in UPDATING. The problem occurs when you cvsup the new crypto-in-src-all sources and replace RCS files with different contents and the same version number. cvs update/checkout compares the repo version number against the checked out version number and considers the file an ``M'' (modified source). The file isn't updated and your world gets corrupted. This is probably a candidate for UPDATING. -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
My apologies if this is old news, but I see nothing in UPDATING. I sent it to ctm-announce... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
In article [EMAIL PROTECTED], Brian Somers [EMAIL PROTECTED] wrote: I haven't looked into it too deeply yet because of other source tree problems, but if you used to get your crypto ,v files from internat, you will suffer some funny problems unless you nuke the old checked-out files. [...] The problem occurs when you cvsup the new crypto-in-src-all sources and replace RCS files with different contents and the same version number. cvs update/checkout compares the repo version number against the checked out version number and considers the file an ``M'' (modified source). The file isn't updated and your world gets corrupted. One thing I'd like to stress is that this only affects you if you're getting the CVS files (*,v) and then using the cvs command to check them out and/or update them. If you are using CVSup in checkout mode (*default tag=something) then you don't need to do anything special. This is probably a candidate for UPDATING. That wouldn't hurt. But it actually affects _all_ branches, I believe. So in a way, UPDATING doesn't cover enough ground. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
