X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0	tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_SV,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
Message-ID: <4D823FEF.3050709@gmx.de>
Date: Thu, 17 Mar 2011 18:07:59 +0100
From: Matthias Andree <matthias DOT andree AT gmx DOT de>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; de-DE; rv:1.9.2.15) Gecko/20110306 Mnenhy/0.8.3 Thunderbird/3.1.9
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [SOLVED] cygwin1.dll upgrade problem
References: <19842 DOT 11745 DOT 643936 DOT 955718 AT wylie DOT me DOT uk>
In-Reply-To: <19842.11745.643936.955718@wylie.me.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

Am 17.03.2011 16:50, schrieb Alan J. Wylie:
>
> Hi, Corinna et al.
>
> I'm not subscribed to the mailing list: I read it via gmane, but I've
> just solved a problem that might be run into by other users.
>
> Initial symptom:
>
> svn exits immediately without any output
>
> I traced this to a recent upgrade of base/cygwin which left behind
> /bin/cygwin1.dll.new and didn't copy it over.
>
> I tried closing all cygwin programs and re-installing, but still it
> didn't upgrade and left the .new file behind.
>
> Illumination dawned - I run cron as a service, and this was holding
> the old copy of the library open. Shut down cron, re-install, and all
> is now fine.
>
> If you feel this is useful, please feel free to forward it on to the
> mailing list.

setup.exe will have made mention about in-use files that should have 
gotten replaced but were only scheduled for replacement across the next 
reboot, and that you need to reboot in order to finish the upgrade.

Of course you can retry to shut down all processes and re-do the upgrade 
without a reboot, but nonetheless the reboot should happen soon, not 
after days or weeks with other intermitting setup.exe runs, else you 
might inadvertently be switched back to older installations on a reboot.

Be sure to carefully read the pop-up requesters and infobubbles from 
setup.exe.

-- 
Matthias Andree

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