X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Tue, 27 Mar 2012 20:20:49 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: rebase-4.1.0-1
Message-ID: <20120327182049.GU30721@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <announce.20120327014025.GA3344@tishler.net> <4F712CFC.9050603@cs.utoronto.ca> <20120327083621.GA30721@calimero.vinschen.de> <4F71DA4F.1060105@cs.utoronto.ca> <20120327152918.GL30721@calimero.vinschen.de> <COL102-W1924465DFDE1AB02D110FCB54A0@phx.gbl> <20120327161443.GO30721@calimero.vinschen.de> <COL102-W33387E9AF689AC8FA036AEB54A0@phx.gbl> <20120327171646.GR30721@calimero.vinschen.de> <4F72008F.8020403@cornell.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4F72008F.8020403@cornell.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
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 Mar 27 14:01, Ken Brown wrote:
> On 3/27/2012 1:16 PM, Corinna Vinschen wrote:
> >On Mar 27 09:35, Karl M wrote:
> >>
> >>
> >>
> >>>Can it at least complain about in-use files?
> >>
> >>It does in the setup.log output. Other than that, it can't since it
> >>has no window to do output to.
> >>
> >>
> >>But setup will still alert the user about running cygwin processes, true?
> >
> >I wasn't aware that setup alerts the user about running cygwin processes.
> 
> I think there are two different things being discussed in this
> thread. On the one hand, setup alerts the user that certain DLLs are
> in use and can't be replaced.  This, of course, hasn't changed.
> 
> On the other hand, the new _autorebase postinstall script
> (/etc/postinstall/autorebase.bat) will run rebaseall and will deal
> gracefully with DLLs that can't be rebased because they're in use.
> 
> I just tried it, and the list of DLLs that couldn't be rebased does
> indeed appear in setup.log.full.  I also get a warning from
> setup.exe about the exit code of autorebase.bat, which some users
> might interpret as meaning that autorebase.bat failed.  I wonder if
> you'd be better off suppressing this warning somehow.

That's unexpected.  The fact that rebase prints the warnings doesn't
mean it returns with a non-0 exit code.
In fact, as far as I can see, the only reason to fail with a non-0 exit
code after printing the "The following DLLs couldn't be rebased"
messages would be if saving the database failed, which also means
you should see a message "failed to create temporary rebase database"
or "failed to write rebase database" in the log.  If such a message
is not printed, I don't understand where the non-0 exit code is
coming from.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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

