X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-0.7 required=5.0	tests=AWL,BAYES_00,RCVD_NUMERIC_HELO,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
To: cygwin@cygwin.com
From: =?UTF-8?B?UmVuw6kgQmVyYmVy?= <r.berber@computer.org>
Subject: Re: Installing new versions of vim doesn't uninstall old versions
Date: Thu, 11 Nov 2010 12:45:33 -0600
Lines: 29
Message-ID: <ibhdkk$hi0$1@dough.gmane.org>
References: <0C33B811BB93B3469F549ADBFA84414718BC77B4B2@NALASEXMB08.na.qualcomm.com> <4CDC342B.7010308@cygwin.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.0
In-Reply-To: <4CDC342B.7010308@cygwin.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On 11/11/2010 12:21 PM, Larry Hall (Cygwin) wrote:

> On 11/11/2010 1:07 PM, Harrington, John wrote:
>> I recently had a problem with vim that was the result of my unwittingly
>> having two previous versions of vim in my /usr/bin.  Is it normal for the
>> cygwin installer not to delete or clobber the previous versions?  I'm not
>> sure what I did wrong, if anything, in updating my cygwin installation.
>=20
> Probably just a local glitch.  We haven't seen other reports of this,
> though
> that could just mean that no one else has noticed.

Actually there are many reports, its not just vim, similar reports have
been made about ssh, and checking for un-installed updates showed other
cases.

setup.exe just leaves <you-name-it>.exe.new (or .dll.new) and the change
never happens.

It may have been one of the old versions of setup, I don't know, some
upgrades do happen correctly when an old one is still there, and left there.
--=20
Ren=C3=A9 Berber



--
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