Message-ID: <5054EB57.2000502@comcast.net>
Date: Sat, 15 Sep 2012 16:55:51 -0400
From: Ken <kstmp001@comcast.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120909 Firefox/15.0.1 SeaMonkey/2.12.1
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Cygwin 1.7.16-1 setup v2.774 problem for un-installable packages
References: <5054975E.2020104@comcast.net>
In-Reply-To: <5054975E.2020104@comcast.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Ken wrote:
> - ran setup to "Install from Local Directory"
> - toggle the "Default" to "Install" for all the
> previously downloaded packages
> - Now, examine the X11 section and observe that the
> end of this listing includes many items listed as
> "Skip". For example, x2x, Xaw3d, mkcfm, and proxymngr
> to name a few.
> - Attempt to toggle the "Skip" to determine what the
> package size is and whether or not it is a binary or
> source, then setup.exe crashes.
>

Sorry for the garbage in the last post, resubmitting 
using standard ascii characters for the tree view ...

Upon further testing, I found that this issue only 
occurs when there are multiple local repository folders 
within the same local source tree 
("--local-package-dir" to setup). That is, even to the 
point where only one is populated with package files 
and the same version of setup.ini exists in all of 
them. For example, the following structure will produce 
the problem.

==================================
CYGWIN\1.7.16-1
|    setup.exe
|
|---http%3a%2f%2fcygwin.mirrors.pair.com%2f
| |    setup.ini
| |
| +---release
|     +---aalib
| |       +---libaa1
| |              libaa1-1.4rc5-10.tar.bz2
v v
v v (snipped)
v v
| |
| +---_update-info-dir
|        _update-info-dir-01074-1.tar.bz2
|
+---_http%3a%2f%2fcygwin.mirrors.pair.com%2f
        setup.ini
==================================

However, if setup.ini is deleted from the secondary 
repositories, the problem does not manifest.

Is this is a bug? Or is setup only designed to allow 
only one local repository folder?

Kind regards,
Ken

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