public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: "Веснин Юрий Александрович" <yavesnin@spb.rpkb.ru>
Subject: Re: Hung setup-x86_64.exe after parsing setup.ini
Date: Tue, 13 Aug 2019 11:40:00 -0000	[thread overview]
Message-ID: <a00c2dad-660f-5810-eb03-b7f40ee24aaf@dronecode.org.uk> (raw)
In-Reply-To: <003aa1a12e604bcca88f42a3a8aa41c9@spb.rpkb.ru>

On 12/08/2019 10:44, Веснин Юрий Александрович wrote:
> 
> After creating a huge custom package, we meet inaccessibility of using setup.exe. It hangs on parsing setup.ini. By doing a little research we've found that this behavior appears when package size is greater than 1GiB (not accurate 1GiB but 1.4GB is enough). We started to investigate setup.exe sources but we stuck in bison sources.

If you provide more details on that problem, I can probably give some 
advice.

> How to reproduce the problem:
> 1. Make own FTP-repo of Cygwin (I think it could be done without packages at all)
> 2. Append the addition to setup.ini (from bottom of letter; in my setup.ini it holds from 173244 line)
> 3. Compress one with setup
> 4. Start latest (2.897 | 64 bit) setup-x86_64.exe, try to use this repo with default other settings.
> 5. The freeze happens during parsing setup.xz
> 
> "Workaround" is
> 1. Replace actual size with 1000000000 (at 173260th line of my setup.ini)
> 2. Recompress one
> 3. Start same setup utility
> 4. Parsing setup.xz passed but it breaks by downloading, of course. It's OK.
> 
> It's definitely a bug. What's the proper way to fix it?

Odd.

I suspect that there might be additional problems later on, if the 
uncompressed size of the package exceeds 2GB (as briefly mentioned in [1])

[1] https://cygwin.com/ml/cygwin-apps/2013-01/msg00045.html

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

  reply	other threads:[~2019-08-13 11:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12  9:44 Веснин Юрий Александрович
2019-08-13 11:40 ` Jon Turney [this message]
2019-08-13 16:57   ` Веснин Юрий Александрович
2019-08-13 17:27     ` Jon Turney
2019-08-14 10:05       ` Веснин Юрий Александрович
2019-08-14 17:33 ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a00c2dad-660f-5810-eb03-b7f40ee24aaf@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=yavesnin@spb.rpkb.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).