* Hung setup-x86_64.exe after parsing setup.ini
@ 2019-08-12 9:44 Веснин Юрий Александрович
2019-08-13 11:40 ` Jon Turney
2019-08-14 17:33 ` Achim Gratz
0 siblings, 2 replies; 6+ messages in thread
From: Веснин Юрий Александрович @ 2019-08-12 9:44 UTC (permalink / raw)
To: cygwin
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.
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?
Addition:
@ rdc-deps
sdesc: "RDC's devel dependencies"
ldesc: "RDC's devel dependencies"
category: Base
requires: ca-certificates gcc-core gcc-g++ git gnupg libftdi1 lynx make openssh python python27 python27-pip python38 python38-pip subversion vim wget
version: 0.1-1
install: x86_64/release/rdc-deps/rdc-deps-0.1-1.tar.xz 10240 2aaf7929c7d5299e2613f5a9eb18d7a644c81d0da7a6fba93069c83a490ec798941043a8ed8bb95b28ce21179e987e1f04f372a891a5918b40db6f612276f6e4
source: x86_64/release/rdc-deps/rdc-deps-0.1-1-src.tar.xz 108 da016ecd9ac6dd3ecd1a65b80c2728db59bccd9ca5e6b54888f02398e3f97a90d1bae3bef85f0eb0950c07734bf3e191fb679fc39527205ba0520009ca4769d2
depends2: ca-certificates, gcc-core, gcc-g++, git, gnupg, libftdi1, lynx, make, openssh, python, python27, python27-pip, python38, python38-pip, subversion, vim, wget
@ rdc-tools
sdesc: "RDC's toolchain"
ldesc: "RDC's toolchain"
category: Base
requires: rdc-deps
version: 1.1.1-1
install: x86_64/release/rdc-tools/rdc-tools-1.1.1-1.tar.xz 1378576256 5b15397950db4f95e3e0560a5c9183b3811e821cfb183db1bf93a411e01e5bb4b86825a28f8121389422ffd7e9f12eef88b22560f8c30b2beb5fae230c738332
source: x86_64/release/rdc-tools/rdc-tools-1.1.1-1-src.tar.xz 108 da016ecd9ac6dd3ecd1a65b80c2728db59bccd9ca5e6b54888f02398e3f97a90d1bae3bef85f0eb0950c07734bf3e191fb679fc39527205ba0520009ca4769d2
depends2: rdc-deps
---
Thank you in advice,
Yuriy Vesnin
--
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] 6+ messages in thread
* Re: Hung setup-x86_64.exe after parsing setup.ini
2019-08-12 9:44 Hung setup-x86_64.exe after parsing setup.ini Веснин Юрий Александрович
@ 2019-08-13 11:40 ` Jon Turney
2019-08-13 16:57 ` Веснин Юрий Александрович
2019-08-14 17:33 ` Achim Gratz
1 sibling, 1 reply; 6+ messages in thread
From: Jon Turney @ 2019-08-13 11:40 UTC (permalink / raw)
To: The Cygwin Mailing List
Cc: Веснин
Юрий
Александрович
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Hung setup-x86_64.exe after parsing setup.ini
2019-08-13 11:40 ` Jon Turney
@ 2019-08-13 16:57 ` Веснин Юрий Александрович
2019-08-13 17:27 ` Jon Turney
0 siblings, 1 reply; 6+ messages in thread
From: Веснин Юрий Александрович @ 2019-08-13 16:57 UTC (permalink / raw)
To: Jon Turney, The Cygwin Mailing List
> If you provide more details on that problem, I can probably give some
> advice.
I suppose that bug comes from parsing setup.ini because of cygwin hangs on such stage.
You can find more details by following previously described steps.
>> 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 the 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])
Definitely not. Setup utility does not reach the downloading stage.
> [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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Hung setup-x86_64.exe after parsing setup.ini
2019-08-13 16:57 ` Веснин Юрий Александрович
@ 2019-08-13 17:27 ` Jon Turney
2019-08-14 10:05 ` Веснин Юрий Александрович
0 siblings, 1 reply; 6+ messages in thread
From: Jon Turney @ 2019-08-13 17:27 UTC (permalink / raw)
To: The Cygwin Mailing List
Cc: Веснин
Юрий
Александрович
On 13/08/2019 17:56, ÐеÑнин ЮÑий ÐлекÑандÑÐ¾Ð²Ð¸Ñ wrote:
>> If you provide more details on that problem, I can probably give some
>> advice.
>
> I suppose that bug comes from parsing setup.ini because of cygwin hangs on such stage.
> You can find more details by following previously described steps.
You wrote: "We started to investigate setup.exe sources but we stuck in
bison sources."
I have no idea what kind of problem you encountered trying to
investigate the problem. Unless you provide more details about what you
got stuck on, I can't help you very much.
--
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] 6+ messages in thread
* Re: Hung setup-x86_64.exe after parsing setup.ini
2019-08-13 17:27 ` Jon Turney
@ 2019-08-14 10:05 ` Веснин Юрий Александрович
0 siblings, 0 replies; 6+ messages in thread
From: Веснин Юрий Александрович @ 2019-08-14 10:05 UTC (permalink / raw)
To: Jon Turney, The Cygwin Mailing List
>>> If you provide more details on that problem, I can probably give some
>>> advice.
>>
>> I suppose that bug comes from parsing setup.ini because of cygwin hangs on such stage.
>> You can find more details by following previously described steps.
> You wrote: "We started to investigate setup.exe sources but we stuck in
> bison sources."
> I have no idea what kind of problem you encountered trying to
> investigate the problem. Unless you provide more details about what you
> got stuck on, I can't help you very much.
Okay. The problem happens when we trying to add the large package with size around
1378576256 bytes parsing setup.ini. This freeze at the installation process.
--
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] 6+ messages in thread
* Re: Hung setup-x86_64.exe after parsing setup.ini
2019-08-12 9:44 Hung setup-x86_64.exe after parsing setup.ini Веснин Юрий Александрович
2019-08-13 11:40 ` Jon Turney
@ 2019-08-14 17:33 ` Achim Gratz
1 sibling, 0 replies; 6+ messages in thread
From: Achim Gratz @ 2019-08-14 17:33 UTC (permalink / raw)
To: cygwin
Веснин Юрий Александрович writes:
> It's definitely a bug. What's the proper way to fix it?
It's not a fix, but for starters you could create a bunch of smaller packages.
> Addition:
> @ rdc-deps
> sdesc: "RDC's devel dependencies"
> ldesc: "RDC's devel dependencies"
> category: Base
> requires: ca-certificates gcc-core gcc-g++ git gnupg libftdi1 lynx make openssh python python27 python27-pip python38 python38-pip subversion vim wget
> version: 0.1-1
> install: x86_64/release/rdc-deps/rdc-deps-0.1-1.tar.xz 10240 2aaf7929c7d5299e2613f5a9eb18d7a644c81d0da7a6fba93069c83a490ec798941043a8ed8bb95b28ce21179e987e1f04f372a891a5918b40db6f612276f6e4
> source: x86_64/release/rdc-deps/rdc-deps-0.1-1-src.tar.xz 108 da016ecd9ac6dd3ecd1a65b80c2728db59bccd9ca5e6b54888f02398e3f97a90d1bae3bef85f0eb0950c07734bf3e191fb679fc39527205ba0520009ca4769d2
> depends2: ca-certificates, gcc-core, gcc-g++, git, gnupg, libftdi1, lynx, make, openssh, python, python27, python27-pip, python38, python38-pip, subversion, vim, wget
>
> @ rdc-tools
> sdesc: "RDC's toolchain"
> ldesc: "RDC's toolchain"
> category: Base
> requires: rdc-deps
> version: 1.1.1-1
> install: x86_64/release/rdc-tools/rdc-tools-1.1.1-1.tar.xz 1378576256 5b15397950db4f95e3e0560a5c9183b3811e821cfb183db1bf93a411e01e5bb4b86825a28f8121389422ffd7e9f12eef88b22560f8c30b2beb5fae230c738332
> source: x86_64/release/rdc-tools/rdc-tools-1.1.1-1-src.tar.xz 108 da016ecd9ac6dd3ecd1a65b80c2728db59bccd9ca5e6b54888f02398e3f97a90d1bae3bef85f0eb0950c07734bf3e191fb679fc39527205ba0520009ca4769d2
> depends2: rdc-deps
None of this should have category Base. Use your own category and
install by category in setup.exe.
I hope it's obvious that the empty rdc-deps package is currently useless
and you could just list the deps right here. But you could depend on
non-empty pakcages of your own and therefore split this hguhe thing into
a number of packages that have more manageable sizes.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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] 6+ messages in thread
end of thread, other threads:[~2019-08-14 17:33 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-12 9:44 Hung setup-x86_64.exe after parsing setup.ini Веснин Юрий Александрович
2019-08-13 11:40 ` Jon Turney
2019-08-13 16:57 ` Веснин Юрий Александрович
2019-08-13 17:27 ` Jon Turney
2019-08-14 10:05 ` Веснин Юрий Александрович
2019-08-14 17:33 ` Achim Gratz
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).