On Jun 28, 10:04am, Anne Bennett wrote:
} On Mon, 12 Mar 2007, John Nemeth wrote:
} 
} > } /usr/src/share/zoneinfo/northamerica does not contain the new
} > } timezone changes for Canada, even after cvs update.  Result:
} > } the time is wrong.
} >
} >      Did you use 'cvs update -A'?
} 
} No, I hadn't; I have an extremely rudimentary knowledge of cvs.  I've just
} looked up "-A" for update: "Reset any sticky tags, dates, or -k options".
} I am not aware of having used any sticky tags, but okay...  Yup, it

     If you are starting with NetBSD 3.1 source tarballs, they will
come with a "netbsd-3" sticky tag by default so that updates will get
stuff from that branch.  Normally, you will want to stick with stuff on
the same branch.

} > Quebec didn't adopt the change until
} > December 2006, so the change won't be on the branch (yet).
} 
} Must make a point of learning more about branches and cvs...

     Have a look here, http://netbsd.org/Releases/release-map.html .

} This is a bit of an important problem for us Canadian NetBSD users,

     It's a bit of a problem for us Canadian NetBSD developers as
well.  Off the top of my head, there are five of us.  One of us should
have looked into it.  This was an oopsie.

} though.  I can't possibly be the only one who had not figured out how
} to fix it "properly" (within the NetBSD-designed system).  I'm not
} sure what to suggest as a way to tell us all what to do - a security
} advisory seems like overkill - but you must be being pelted with
} problem reports about this today, no?

     Actually, only two have shown up so far.  But yes, we need to get
this fixed up and say something about it.

} Next time I need a particularly recent file, I'll try "cvs update -A"
} before reporting a problem.

     Be careful with that.  It is generally okay with data files, but
can cause problems with code, since the code can depend on other
changes elsewhere.  This type of thing is best done by a developer
unless you know the code in question really well.  If something doesn't
work on a branch feel free to file a PR.  If you have an idea for the
fix, you can always include it.

}-- End of excerpt from Anne Bennett