Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!data.nas.nasa.gov!wilbur.nas.nasa.gov!tweten From: tweten@wilbur.nas.nasa.gov (Dave Tweten) Subject: Re: Error in patch 89 References: <1993Mar5.160055.17730@cm.cf.ac.uk> <CGD.93Mar5103643@eden.CS.Berkeley.EDU> Sender: news@nas.nasa.gov (News Administrator) Organization: NAS Systems Division, NASA Ames Date: Wed, 10 Mar 93 21:15:06 GMT Message-ID: <1993Mar10.211506.150@nas.nasa.gov> Lines: 46 In article <CGD.93Mar5103643@eden.CS.Berkeley.EDU> cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes: >that problem w/patch 89 was fixed in a later-but-named-the-same >release of the new patches... I don't think it is named the same. If the results of my effort to start again clean are any measure, the buggy patch 89 is still around, with a different name - a name which makes it look like a better patchset to use. When I picked up the patches yesterday, for my clean restart, agate.berkeley.edu had two similarly named files with the same dates on them: pub/386BSD/386bsd-0.1/unofficial/patch-kit/patchset84-110.tar and pub/386BSD/386bsd-0.1/unofficial/patch-kit/patchset84-110-LATEST.tar Being gullable, I presumed that "LATEST" meant what it said. I took it. I used it last night. I got the reject file for /usr/src/usr.bin/awk/config.h The reject resulted from trying to change #define HAVE_STRTOD 1 to #define HAVE_STRTOD 0 when it had that value already. Tonight, I'll try again with the file that isn't the "LATEST". >(so most people didn't see it... 8-) It's nice to know I'm not "just one of the crowd." Maybe a better name could be used for the "LATEST" file on agate, like patchset84-110-POISONOUS-DO-NOT-USE.tar Just a thought :-) -- --------------------------------------------------------------------------- Dave Tweten tweten@nas.nasa.gov NASA Ames Research Center, M/S 258-5 (415) 604-4416 Moffett Field, CA 94035-1000 FAX: (415) 604-4377