Mark W. Eichin writes ("Re: Bug#4329: Emacs has hardcoded path for jka-compr,
breaks at upgrade"):
> Did you upgrade from 19.29-3 to 19.31-2 as indicated in your message,
> or to 19.34-2, which is current?
19.34-2 hasn't reached my local mirror yet. Isn't it still in
Incoming ?
> (I ask, because I just got the bug
> report today, and it appears to be about a day old -- but if you
> actually reported it before 8/27, then there is a bug tracking problem
> that needs attention.)
Years only have 12 months, ITYSBT. Perhaps you meant the 27th of
August, aka 27.8.1996 aka 1996-8-27 ? [1]
If you look at the headers of the messages you'll see that I reported
it at 02:23 BST (= 01:23 GMT) on the 29th.
> I can see about making the emacs postinst smarter, but it's clear that
> the line you quoted from site-start was what was wrong in the first
> place. I don't know, however, what package included it (which is a
> part of the reason for the change in the way startup code is handled...)
Right ...
Ian.
[1] Yes, I know it was probably deliberate, but American middle-endian
date-formats are stupid and confusing and I want them stamped out.
