[developers] Bug fix not merged with LKB code

[Stephan Oepen]

hi bernd,

> i just re-identified a bug in LKB that i already fixed two years
> ago. This time, it involved about three persons work for two days to
> pin it down.  We obviously used a frozen LKB most of the time,
> otherwise this would have reappeared earlier.
> 
> Maybe somebody can verify that this change is OK in the LKB environment
> too and can propagate it into the CVS. Thanks to anyone who'll do it.

i went through all intern()s in the (active portions of) MRS code today
and believe the problem above is now resolved.  i also checked in quite
a few changes that had accumulated on my end, mostly to [incr tsdb()].
i am still testing the results and will summarize a little later.

for people who wanted to try using the latest code (or compiling a new
PET) immediately, new builds are underway.  for Linux (32- and 64-bit),
you can already access these upcoming builds as follows:

  bash ./install --test

for those familiar with the layout of the download site, the switch is
requesting the installer to fetch the `test' build.  most likely, this
build will be propagated to `latest' within a few days; the installer,
by default, will install the `latest' version.

                                                      all best  -  oe

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++ Universitetet i Oslo (IFI); Boks 1080 Blindern; 0316 Oslo; (+47) 2285 7989
+++     CSLI Stanford; Ventura Hall; Stanford, CA 94305; (+1 650) 723 0515
+++       --- oe at csli.stanford.edu; oe at ifi.uio.no; stephan at oepen.net ---
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++