X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 6 Apr 2009 16:06:01 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Reverting from 1.7.0-45 [was Re: [1.7]: For the love of god, don't update!] Message-ID: <20090406140601.GD4134@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <49D97797 DOT 9080902 AT gmail DOT com> <49D9913B DOT 7030708 AT cwilson DOT fastmail DOT fm> <49D99981 DOT 4030503 AT gmail DOT com> <49D99A02 DOT 7070407 AT gmail DOT com> <49D99D65 DOT 8040304 AT cwilson DOT fastmail DOT fm> <49D9C684 DOT 8030201 AT gmail DOT com> <49D9FDA4 DOT 7050005 AT cwilson DOT fastmail DOT fm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49D9FDA4.7050005@cwilson.fastmail.fm> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Apr 6 09:03, Charles Wilson wrote: > Dave Korn wrote: > > LOLWUT? It turns out something has gone horribly wrong in the alternatives > > department now: > > [...] > > Actually, from Corinna's reply, it appears that, in addition to > reverting *alternatives* because of the dependence that the new -10 > package has on the the cygwin-1.7.0-45 ctype export, you may also need > to revert any package that USES alternatives (or, at least, run > /usr/sbin/alternatives to recreate the symlinks using the "old" method) Actually, what I was trying to imply is that reverting to a pre-45 test release is not a good idea at all. Try to find the reason for your problem while -45 is running. Let's go forward, not backward, please. I have successfully built and run vim 7.2.148-1 as well as OpenSSL-1.0.0-beta1 under 1.7.0-45, and I have built and run several test applications in the meantime. We all know there are still bugs in the code, right? But reverting to an old release doesn't help us at all. If you really find a bug in -45 which is the culprit for not being able to build gcc, you'll get a bugfixed -46 ASAP. However, what I'd need in this case is some sort of reproducible testcase... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/