/init.d/serias script (from baselayout package) does not show any change in the CVS header between the versions. I suspect that it was added with "-kb" flag.
I meant /init.d/serial, sorry.
Which was, in turn /etc/init.d/serial. Doh!
azarah@nosferatu init.d $ grep Header serial # $Header: /home/cvsroot/gentoo-src/rc-scripts/init.d/serial,v 1.4 2002/03/10 22:57:28 azarah Exp $ azarah@nosferatu init.d $ cvs log serial RCS file: /home/cvsroot/gentoo-src/rc-scripts/init.d/serial,v Working file: serial head: 1.4 branch: locks: strict access list: symbolic names: keyword substitution: kv total revisions: 4; selected revisions: 4 description: ---------------------------- revision 1.4 date: 2002/03/10 22:57:28; author: azarah; state: Exp; lines: +12 -9 lost of fixes ---------------------------- Looks fine to me.
Hi: If you unpack the file rc-scripts-1.3.0.tar.bz2 and look at the file init.d/serial, you'll notice that the Header string is: # $Header: /home/cvsroot/gentoo-src/rc-scripts/init.d/serial,v 1.3 2001/12/22 06 :51:18 azarah Exp $ which is obviously not consistent with what you have. I don't know how this is possible. ;^)
Actually, it is consistent, since you only changed the stuff on March 10, when it became 1.4 from 1.3. Here's the problem: when merging the changes to the files under /etc after I upgraded the baselayout package, I had to merge 26 files or so. So, I was looking at the CVS id strings of the old version and of the new version; if the strings were the same, I deleted the "new" version of the file, otherwise I looked at it closer. What caught my attention with "serial" was that the CVS header was the same as the old file on my system, but the new file contained differences. I concluded that since the file has changed in the new release of rc-scripts, but the CVS header hasn't, there must be a problem at the CVS level. The only other explanation, AFAICS, could be that rc-scripts were packaged from someone's working directory, and included uncommitted changes. Was this the case?
It just means it was packaged before commit. I usually try to get a tested working .tbz2 out for my systems and whatever test cases I can think of before commit. Ill do it the other way around next time ;)
