X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Rcv55ON3D3xkW+v7
	S66Yn9NlklCyrroU/+AUqNN5LSdzOsvKT0mU6L0jjqL+aS7vNNPa57+CvwuyfMUw
	OM3Lzrt0+/enZrdQQlyqXYya8g+i+MRHveN/DhieytyNf/TKRLOHJc+p4fiSgUgc
	LhPEJNVY5F9RHB/xPZiLDg4lv7A=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=tX2QTo4YOAWrOyxivhqSFT
	youMw=; b=vQdUZ9EXUyXEGtws+OU82GevTibWSu28YvBh74AnNmDajrnyTye7sh
	5/JmmnfLZ0EmjgWOSYkE1BquMmxvm/fCydK6WhFGC9DLcuORzihZgnxLWec6Bqi6
	g7hdnUHnP3CY7yXY2M1GO2U2+WuNn+TnrIKvm8XVMyRY+SQnEhLao=
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
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	vms173001pub.verizon.net
Message-id:	<52545966.9000404@cygwin.com>
Date:	Tue, 08 Oct 2013 15:13:42 -0400
From:	"Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to:	cygwin AT cygwin DOT com
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: baffling cygwin setup.exe behavior
References:	<20131008185241 DOT GA21581 AT plunk DOT org>
In-reply-to:	<20131008185241.GA21581@plunk.org>

On 10/8/2013 2:52 PM, Don Hatch wrote:

<snip>

> So, as far as I can see,
> the only way to get rcs 5.8.2-1 is to globally select "Curr"
> and *don't click on rcs at all*.
> So, to upgrade rcs and nothing else,
> I'd have to globally select "Curr"
> and manually change every package *except* rcs
> to "Keep", leaving rcs alone.
> That seemed like a lot of work and error prone,
> and I knew I was going to be doing all this several times,
> and who knows whether I'd run into other problems on the way.
> So instead, I elected to upgrade
> my entire system to "Curr", even though
> that's not really what I wanted.
>
> If anyone can explain what's going on here
> (is this a bug? or something wrong with my thinking?)
> and how to do this simple operation,
> I'd really appreciate it.

I'm not sure why you cannot get back to 5.8.2-1.  I can but I
don't have 'rcs' installed so my cycle just goes from Skip->
5.8.2-1->5.8.1-1->Skip->....

I guess if all else fails, try uninstalling and reinstalling
'rcs'.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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