DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=WeQcXcmx0NbGrxfNSsLsiL7KzN+LDCd/ggaFrc9prs/
	4AIe9vvm379lO0ddDC/w4JJZsocYxsm7izpXFBCFTbEyF816QvaCWS08MLiGV5B8
	3xG6fuE6ZFVVFA5ahF6/8MPLEbJg4ZND/ClcgikN0qwwy22NTh7ZqPcLaZz/Sjh8
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Stan Moore" <smoore1956@comcast.net>
To: <cygwin@cygwin.com>
References: <525BD8F3.4090603@cornell.edu>
In-Reply-To: <525BD8F3.4090603@cornell.edu>
Subject: RE: Did October "Patch Tuesday" break something?
Date: Mon, 14 Oct 2013 16:27:29 -0400
Message-ID: <002c01cec91b$cdf1f810$69d5e830$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain;	charset="Windows-1252"
Content-Transfer-Encoding: 7bit


<snip>
>> To close the loop for the record, my situation had nothing to do with
> > the windows patches.
> > For reasons I haven't tracked down yet the emacs package system seems
> > to have had a bad day.
> > Emacs has a package system and some repositories for many of the modes
> > and extensions available.
> > After M-x list-packages you select packages of interest for
> > installation or update and life is good. It seems one of the packages
> > is damaged in the repo or it became corrupted during/after update.
> > Oddly, it worked great for a day after package update but then the
> > package system started adding some download package directories to the
> > Info-directory-list which caused the emacs info mode to find the
> > French versions before anything else.  I still don't know what
> > triggered the madness but it's definitely happening during the package
> > load/init phase and has nothing to do with MS or the recent patches.
> 
> This was probably caused by the problem reported here:
> 
>    https://lists.gnu.org/archive/html/emacs-devel/2013-10/msg00360.html

Thanks, it's almost certainly related. I'd already sorted things out here
but never actually
got down to the what or how and the workaround was trivial. I figured out
basically what was 
going on but the timing did and still does puzzle me. Since I can't go back
to when it happened
it will just have to remain one of life's many little mysteries. 


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple