public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Cygwin 1.7.16-1 setup v2.774 problem for un-installable packages
@ 2012-09-15 15:07 Ken
  2012-09-15 20:55 ` Ken
  2012-09-16  3:48 ` Ken
  0 siblings, 2 replies; 3+ messages in thread
From: Ken @ 2012-09-15 15:07 UTC (permalink / raw)
  To: cygwin

[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]

Hello,

I have come across an issue in setup where certain 
Cygwin components are listed and, if selected, cause 
setup to crash.  This is something that I do not recall 
experiencing with previous versions of setup.  However, 
I am unaware of when this actually first started.  A 
cursory search of the mailing list does not yield 
anything related to this particular issue.

Details:

- Host OS is Windows 7, 64bit
- setup.exe v2.774
- I had previously selected "Download Without 
Installing" and saved many packages locally (my usual 
method for years) without issue. This was done fresh on 
9/15/2012.
- 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.

Note that this is not isolated to the X11 category.  
There is a smattering of other packages throughout the 
listing which instigate the same result.

As an additional aid, I have included a bzipped PDF 
file which shows all of the above.

By the way, it appears that at least some of these are 
listed in setup.ini without any "Install" or "Source" 
line (perhaps all are listed in this way; I did not 
check for this).

While I could employ a work-around (e.g., modify the 
setup.ini file to remove the offending entries after 
each download), I much prefer a more permanent 
solution.  Is this enough detail where someone can 
reproduce the problem and incorporate a fix?

Please note, that setup.exe otherwise operates fine and 
installs the other selected packages (provided that 
none of these "Skip" packages are touched).

My thanks goes out to the entire Cygwin team for their 
tireless effort!

Kind regards,
Ken


[-- Attachment #2: Cygwin-setup-problem-for-un-installable-apps.pdf.bz2 --]
[-- Type: application/x-bzip2, Size: 389520 bytes --]

[-- Attachment #3: Type: text/plain, Size: 218 bytes --]

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Cygwin 1.7.16-1 setup v2.774 problem for un-installable packages
  2012-09-15 15:07 Cygwin 1.7.16-1 setup v2.774 problem for un-installable packages Ken
@ 2012-09-15 20:55 ` Ken
  2012-09-16  3:48 ` Ken
  1 sibling, 0 replies; 3+ messages in thread
From: Ken @ 2012-09-15 20:55 UTC (permalink / raw)
  To: cygwin

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Cygwin 1.7.16-1 setup v2.774 problem for un-installable packages
  2012-09-15 15:07 Cygwin 1.7.16-1 setup v2.774 problem for un-installable packages Ken
  2012-09-15 20:55 ` Ken
@ 2012-09-16  3:48 ` Ken
  1 sibling, 0 replies; 3+ messages in thread
From: Ken @ 2012-09-16  3:48 UTC (permalink / raw)
  To: cygwin

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-09-15 20:55 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-09-15 15:07 Cygwin 1.7.16-1 setup v2.774 problem for un-installable packages Ken
2012-09-15 20:55 ` Ken
2012-09-16  3:48 ` Ken

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).