> ----- Original Message ----- > From: backyard <[EMAIL PROTECTED]> > To: "Ahmad Arafat Abdullah" <[EMAIL PROTECTED]>, "[EMAIL PROTECTED]" <[EMAIL > PROTECTED]>, "Matthew Seaman" <[EMAIL PROTECTED]> > Subject: Re: how to apply a patch set > Date: Sun, 17 Sep 2006 19:00:24 -0700 (PDT) > > > > > --- Ahmad Arafat Abdullah <[EMAIL PROTECTED]> wrote: > > > > > > ----- Original Message ----- > > > From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > > > To: "Matthew Seaman" > > <[EMAIL PROTECTED]> > > > Subject: Re: how to apply a patch set > > > Date: Mon, 18 Sep 2006 00:48:32 +0200 > > > > > Matthew Seaman wrote: > > > > [EMAIL PROTECTED] wrote: > > > >> Hello, > > > >> > > > >> I am trying to apply a patch set to FreeBSD 5.5 > > (this letter 'p' > > > >> followed by a number, after the version in > > 'uname -a') - but somehow it > > > >> did not work. > > > >> > > > >> I cvsup-ed the src using the standard > > 'stable-supfile' with '*default > > > >> release=cvs tag=RELENG_5_5' - then I rebuild > > world. > > > >> > > > >> Now 'uname -a' reports 'FreeBSD 5.5 STABLE #0'. > > Before it was 'FreeBSD > > > >> 5.5 RELEASE #0'. So instead of applying patch > > set I have moved to 'STABLE'. > > > >> > > > >> Could somebody tell me what have I done wrong? > > Actually - what is the > > > >> difference between the 'pX' and the '#X' after > > the version? > > > > > > > > You've shifted your self onto the RELENG_5 code > > branch rather than the > > > > RELENG_5_5 branch. > > > > Yes... but how did it happen after I instructed > > the supfile to get > 'RELENG_5_5'? > > > > Actually in the examples/cvsup I did not find any > > example how to do 'release'. > > > > Thank you for the other answers! > > > Iv. > > > > > > > > > > > > i think I've read abt this long time ago.. but not > > pretty sure ( someone correct me if I'm wrong ).. > > > > u can try: > > > > *default release=cvs tag=RELENG_5_5_RELEASE > > > > > > anyway i never tried this! and i never encounter the > > prob u'va said since 4.x ---> 6.1 > > ( and I'm normally/mostly using -pX than STABLE for > > my prod server ). Seems your method/tag > > > > tag=RELENG_5_5 is correct way to patch to -pX, i > > can't find any reason why your system "patched" > > into STABLE... > > > > could u please copy+paste here your stable-supfile > > config? > > > > TQ > > > > STABLE is the latest set of "patches" to the system. > It will change the tag from RELEASE from the install > to the STABLE set of patches versus the CURRENT set. > STABLE is the major ones you want. CURRENT is all of > them to date. > > If you cvsup to RELEASE you will downgrade and end up > with what you started with when you installed from CD > or whatever was available when the RELEASE cd was > created for whatever system your getting. > > -brian
ermm.. for me ( and as far as i know ) STABLE is a development patch and it will end up with the next RELEASE version.. such as 5.4-STABLE will be patch gradually until it became 5.5-RELEASE. Anyway 5.4-RELEASE-pX is a security fixes ( and possibly bugfix ) but it still remains as RELEASE and not "migrating_into_the_next_version/release". some of the people ( like me ) just prefer to -pX rather than -STABLE. So far i'm not needed -CURRENT yet even RELEASE -pX is powerful enough and suits my needs for my prod servers.. for this case ( back to the topics ), I think this guy do the right method for cvsup-ed to 5.5-RELEASE-pX but it end up with 5.5-STABLE. So i think we better help him and solve it since he maybe not need -STABLE like u said TQ p/s: Correct me if I'm wrong anyone! -- ___________________________________________________ Play 100s of games for FREE! http://games.mail.com _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
