X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<ibhdkk$hi0$1@dough.gmane.org>
References:	<0C33B811BB93B3469F549ADBFA84414718BC77B4B2 AT NALASEXMB08 DOT na DOT qualcomm DOT com> <4CDC342B DOT 7010308 AT cygwin DOT com> <ibhdkk$hi0$1 AT dough DOT gmane DOT org>
Date:	Thu, 11 Nov 2010 21:38:03 +0000
Message-ID:	<AANLkTikB-TrDr+4qB1wsq6pDXeDBrC7wDfGy17v1BwQX@mail.gmail.com>
Subject:	Re: Installing new versions of vim doesn't uninstall old versions
From:	Andy Koppe <andy DOT koppe AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 11 November 2010 18:45, Ren=C3=A9 Berber wrote:
> 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. =C2=A0Is it normal =
for the
>>> cygwin installer not to delete or clobber the previous versions? =C2=A0=
I'm not
>>> sure what I did wrong, if anything, in updating my cygwin installation.
>>
>> Probably just a local glitch. =C2=A0We haven't seen other reports of thi=
s,
>> 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

Yep, bugs in this area were quashed in January and April, but
unfortunately setup.exe bugs can have quite an afterlife, e.g. due to
people ignoring the warnings about a newer setup.exe being available
or installing from a local mirror. And of course the .new files, once
they're there, aren't going to go away.

Andy

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

- Raw text -