* Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) @ 2012-08-23 11:35 Martin.Fitzpatrick 2012-08-23 13:29 ` Earnie Boyd ` (5 more replies) 0 siblings, 6 replies; 54+ messages in thread From: Martin.Fitzpatrick @ 2012-08-23 11:35 UTC (permalink / raw) To: cygwin; +Cc: david Hi, I have just completed a cygwin install, which seemed to take an extraordinary length of time, so I started googling and found the article "Setup 1.7.11 texlive postinstall takes 6+ hours". Ken Brown's response to that post was hopeful, but may have underestimated the scope of the problem, putting it down to "something else going on with your system, maybe having to do with your VM." My installation was on a laptop, not a VM, and while I wouldn't claim that it's a powerful machine, I'm still very surprised at the install time. I also think it remarkable that most (something like 90%) of the install time was spent in the texlive postinstall phase; so in other words, most of the install ran at an acceptable speed (~16 mins to get to the start of the postinstall phase- not too bad for a slow laptop) but the first texlive task ("/etc/postinstall/texlive-collection-basic.sh") then took 25 mins- more than the rest of the install up to that point. So, I would say to Ken Brown- "Keep up the good work"- but please consider raising its priority! At the time of writing you had fixed 29 postinstall scripts and there were 45 remaining. Some users are being hit very hard by this and in fact I aborted the install several times before I realized that it wasn't hanging completely and that the postfix to the "/etc/postinstall/texlive-..." message in the install window was actually changing from time to time- it was that slow! I can send the setup.log.full if you want to see the timestamps for yourself. Regards, Martin. This document is strictly confidential and intended only for use by the addressee unless otherwise stated. If you are not the intended recipient, please notify the sender immediately and delete it from your system. -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2012-08-23 11:35 Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) Martin.Fitzpatrick @ 2012-08-23 13:29 ` Earnie Boyd 2012-08-23 14:35 ` Adam Dinwoodie ` (4 subsequent siblings) 5 siblings, 0 replies; 54+ messages in thread From: Earnie Boyd @ 2012-08-23 13:29 UTC (permalink / raw) To: cygwin On Thu, Aug 23, 2012 at 6:03 AM, Martin.Fitzpatrick wrote: > Hi, > > I have just completed a cygwin install, which seemed to take an > extraordinary length of time, so I started googling and found the article If you do the same with the anti-virus disabled does it change the length of time? -- Earnie -- https://sites.google.com/site/earnieboyd -- 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] 54+ messages in thread
* RE: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2012-08-23 11:35 Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) Martin.Fitzpatrick 2012-08-23 13:29 ` Earnie Boyd @ 2012-08-23 14:35 ` Adam Dinwoodie 2012-08-23 15:27 ` Ken Brown ` (3 subsequent siblings) 5 siblings, 0 replies; 54+ messages in thread From: Adam Dinwoodie @ 2012-08-23 14:35 UTC (permalink / raw) To: cygwin, overseers Martin.Fitzpatrick@... wrote: > This document is strictly confidential and intended only for use by the addressee unless otherwise stated. If you are not the intended recipient, please notify the sender immediately and delete it from your system. Martin, per <http://sourceware.org/lists.html#disclaimer-bounce>, disclaimers like this aren't appropriate for a public mailing list. Emails to this list are seen by a very wide number of people and are publicly archived online indefinitely. Overseers, as requested, have a disclaimer that seems to have slipped through the filter. -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2012-08-23 11:35 Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) Martin.Fitzpatrick 2012-08-23 13:29 ` Earnie Boyd 2012-08-23 14:35 ` Adam Dinwoodie @ 2012-08-23 15:27 ` Ken Brown 2012-08-25 6:47 ` Ken Brown 2013-01-28 16:42 ` toddcs ` (2 subsequent siblings) 5 siblings, 1 reply; 54+ messages in thread From: Ken Brown @ 2012-08-23 15:27 UTC (permalink / raw) To: cygwin On 8/23/2012 6:03 AM, Martin.Fitzpatrick@sita.aero wrote: > Hi, > > I have just completed a cygwin install, which seemed to take an > extraordinary length of time, so I started googling and found the article > "Setup 1.7.11 texlive postinstall takes 6+ hours". Ken Brown's response to > that post was hopeful, but may have underestimated the scope of the > problem, putting it down to "something else going on with your system, > maybe having to do with your VM." My installation was on a laptop, not a > VM, and while I wouldn't claim that it's a powerful machine, I'm still > very surprised at the install time. I also think it remarkable that most > (something like 90%) of the install time was spent in the texlive > postinstall phase; so in other words, most of the install ran at an > acceptable speed (~16 mins to get to the start of the postinstall phase- > not too bad for a slow laptop) but the first texlive task > ("/etc/postinstall/texlive-collection-basic.sh") then took 25 mins- more > than the rest of the install up to that point. > > So, I would say to Ken Brown- "Keep up the good work"- but please consider > raising its priority! At the time of writing you had fixed 29 postinstall There is definitely some inefficiency in the postinstall scripts when many texlive-collection-* packages are installed at once. I'm working on finding a better way of doing it. See the thread starting at http://cygwin.com/ml/cygwin-apps/2012-08/msg00001.html > scripts and there were 45 remaining. Some users are being hit very hard by > this and in fact I aborted the install several times before I realized > that it wasn't hanging completely and that the postfix to the > "/etc/postinstall/texlive-..." message in the install window was actually > changing from time to time- it was that slow! I can send the > setup.log.full if you want to see the timestamps for yourself. Yes, I would like to see setup.log.full. If it's huge, you can send it off list, or just post it somewhere for me to download. 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2012-08-23 15:27 ` Ken Brown @ 2012-08-25 6:47 ` Ken Brown 2012-08-25 7:26 ` Achim Gratz 0 siblings, 1 reply; 54+ messages in thread From: Ken Brown @ 2012-08-25 6:47 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 2796 bytes --] On 8/23/2012 7:35 AM, Ken Brown wrote: > On 8/23/2012 6:03 AM, Martin.Fitzpatrick@sita.aero wrote: >> Hi, >> >> I have just completed a cygwin install, which seemed to take an >> extraordinary length of time, so I started googling and found the article >> "Setup 1.7.11 texlive postinstall takes 6+ hours". Ken Brown's >> response to >> that post was hopeful, but may have underestimated the scope of the >> problem, putting it down to "something else going on with your system, >> maybe having to do with your VM." My installation was on a laptop, not a >> VM, and while I wouldn't claim that it's a powerful machine, I'm still >> very surprised at the install time. I also think it remarkable that most >> (something like 90%) of the install time was spent in the texlive >> postinstall phase; so in other words, most of the install ran at an >> acceptable speed (~16 mins to get to the start of the postinstall phase- >> not too bad for a slow laptop) but the first texlive task >> ("/etc/postinstall/texlive-collection-basic.sh") then took 25 mins- more >> than the rest of the install up to that point. >> >> So, I would say to Ken Brown- "Keep up the good work"- but please >> consider >> raising its priority! At the time of writing you had fixed 29 postinstall > > There is definitely some inefficiency in the postinstall scripts when > many texlive-collection-* packages are installed at once. I'm working > on finding a better way of doing it. See the thread starting at > > http://cygwin.com/ml/cygwin-apps/2012-08/msg00001.html > >> scripts and there were 45 remaining. Some users are being hit very >> hard by >> this and in fact I aborted the install several times before I realized >> that it wasn't hanging completely and that the postfix to the >> "/etc/postinstall/texlive-..." message in the install window was actually >> changing from time to time- it was that slow! I can send the >> setup.log.full if you want to see the timestamps for yourself. > > Yes, I would like to see setup.log.full. If it's huge, you can send it > off list, or just post it somewhere for me to download. Thanks for sending me your setup.log.full. I've extracted the timing information for the texlive-collection-* postinstall scripts (see the attached). I saw 5 postinstall scripts that took inordinately long (marked with ***): texlive-collection-fontsextra.sh texlive-collection-fontsrecommended.sh texlive-collection-formatsextra.sh texlive-collection-htmlxml.sh texlive-collection-langcjk.sh I don't see anything in those scripts that would explain this. I just ran them manually on my system, and the times (in minutes) were 14, 3, 2.5, 2.5, and 7. So I can't think of any explanation except that something on your system (anti-virus or other BLODA?) was interfering. Ken [-- Attachment #2: setup.log.full --] [-- Type: text/plain, Size: 12234 bytes --] 2012/08/22 21:59:02 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-basic.sh" 2012/08/22 22:24:04 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/brltty.sh" 2012/08/22 22:27:32 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-bibtexextra-doc.sh" 2012/08/22 22:27:37 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-bibtexextra.sh" 2012/08/22 22:27:43 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-binextra-doc.sh" 2012/08/22 22:27:48 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-binextra.sh" 2012/08/22 22:27:53 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-context-doc.sh" 2012/08/22 22:27:58 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-context.sh" 2012/08/22 22:42:32 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-arabic.sh" 2012/08/22 22:42:51 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-bulgarian.sh" 2012/08/22 22:43:02 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-chinese.sh" 2012/08/22 22:43:22 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-czechslovak.sh" 2012/08/22 22:43:34 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-dutch.sh" 2012/08/22 22:44:02 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-english.sh" 2012/08/22 22:44:31 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-finnish.sh" 2012/08/22 22:45:04 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-french.sh" 2012/08/22 22:45:41 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-german.sh" 2012/08/22 22:46:13 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-italian.sh" 2012/08/22 22:47:02 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-japanese.sh" 2012/08/22 22:48:13 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-korean.sh" 2012/08/22 22:48:54 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-mongolian.sh" 2012/08/22 22:49:00 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-polish.sh" 2012/08/22 22:49:13 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-portuguese.sh" 2012/08/22 22:49:26 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-russian.sh" 2012/08/22 22:49:46 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-serbian.sh" 2012/08/22 22:49:51 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-slovenian.sh" 2012/08/22 22:50:19 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-spanish.sh" 2012/08/22 22:51:05 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-thai.sh" 2012/08/22 22:51:59 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-turkish.sh" 2012/08/22 22:52:38 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-ukrainian.sh" 2012/08/22 22:53:01 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-documentation-vietnamese.sh" 2012/08/22 22:53:18 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-fontsextra-doc.sh" ***2012/08/22 22:53:24 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-fontsextra.sh" 2012/08/23 02:40:30 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-fontsrecommended-doc.sh" ***2012/08/23 02:41:36 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-fontsrecommended.sh" 2012/08/23 03:42:53 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-fontutils-doc.sh" 2012/08/23 03:44:01 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-fontutils.sh" ***2012/08/23 03:45:07 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-formatsextra.sh" 2012/08/23 04:44:14 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-games.sh" 2012/08/23 04:45:34 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-genericextra-doc.sh" 2012/08/23 04:45:39 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-genericextra.sh" 2012/08/23 04:45:45 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-genericrecommended-doc.sh" 2012/08/23 04:45:50 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-genericrecommended.sh" ***2012/08/23 04:45:55 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-htmlxml.sh" 2012/08/23 05:41:03 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-humanities-doc.sh" 2012/08/23 05:41:56 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-humanities.sh" 2012/08/23 05:43:04 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langafrican.sh" 2012/08/23 05:56:56 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langarabic.sh" ***2012/08/23 05:58:24 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langcjk.sh" 2012/08/23 07:19:52 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langcroatian.sh" 2012/08/23 07:19:57 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langcyrillic.sh" 2012/08/23 07:43:51 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langczechslovak.sh" 2012/08/23 07:52:30 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langfinnish.sh" 2012/08/23 07:52:35 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langfrench.sh" 2012/08/23 07:53:48 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langgerman.sh" 2012/08/23 07:53:53 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langgreek.sh" 2012/08/23 07:56:09 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langhebrew.sh" 2012/08/23 07:57:21 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langhungarian.sh" 2012/08/23 07:57:26 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langindic.sh" 2012/08/23 07:58:59 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langitalian.sh" 2012/08/23 07:59:04 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langlithuanian.sh" 2012/08/23 07:59:50 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langmongolian.sh" 2012/08/23 08:01:02 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langpolish.sh" 2012/08/23 08:07:52 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langportuguese.sh" 2012/08/23 08:07:57 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langspanish.sh" 2012/08/23 08:08:02 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langswedish.sh" 2012/08/23 08:08:07 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langtibetan.sh" 2012/08/23 08:08:13 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langturkmen.sh" 2012/08/23 08:08:18 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-langvietnamese.sh" 2012/08/23 08:11:02 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-latex-doc.sh" 2012/08/23 08:11:07 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-latex.sh" 2012/08/23 08:21:30 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-latexextra-doc.sh" 2012/08/23 08:21:35 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-latexextra.sh" 2012/08/23 08:23:14 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-latexrecommended-doc.sh" 2012/08/23 08:23:20 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-latexrecommended.sh" 2012/08/23 08:23:25 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-luatex-doc.sh" 2012/08/23 08:23:30 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-luatex.sh" 2012/08/23 08:23:35 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-mathextra-doc.sh" 2012/08/23 08:23:40 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-mathextra.sh" 2012/08/23 08:26:55 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-metapost-doc.sh" 2012/08/23 08:27:00 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-metapost.sh" 2012/08/23 08:28:15 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-music-doc.sh" 2012/08/23 08:28:20 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-music.sh" 2012/08/23 08:29:32 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-omega.sh" 2012/08/23 08:34:21 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-pictures-doc.sh" 2012/08/23 08:34:26 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-pictures.sh" 2012/08/23 08:35:52 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-plainextra.sh" 2012/08/23 08:35:57 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-pstricks-doc.sh" 2012/08/23 08:36:03 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-pstricks.sh" 2012/08/23 08:36:09 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-publishers-doc.sh" 2012/08/23 08:36:14 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-publishers.sh" 2012/08/23 08:36:20 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-science-doc.sh" 2012/08/23 08:36:25 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-science.sh" 2012/08/23 08:37:38 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-texinfo.sh" 2012/08/23 08:37:43 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-xetex-doc.sh" 2012/08/23 08:37:49 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/texlive-collection-xetex.sh" 2012/08/23 08:42:34 running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/TeXmacs.sh" [-- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2012-08-25 6:47 ` Ken Brown @ 2012-08-25 7:26 ` Achim Gratz 0 siblings, 0 replies; 54+ messages in thread From: Achim Gratz @ 2012-08-25 7:26 UTC (permalink / raw) To: cygwin Ken Brown writes: > I don't see anything in those scripts that would explain this. I just > ran them manually on my system, and the times (in minutes) were 14, > 3, 2.5, 2.5, and 7. So I can't think of any explanation except that > something on your system (anti-virus or other BLODA?) was interfering. IIRC, most of the time (wallclock, it really doesn't use much CPU) in these scripts is taken up by kpsewhich (there is a short phase of disk activity at the beginning that corresponds to building of the ls-lR database). I've never observed it taking _this_ long however, so I suspect that kpsewhich had/has forking problems on the OPs' system. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2012-08-23 11:35 Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) Martin.Fitzpatrick ` (2 preceding siblings ...) 2012-08-23 15:27 ` Ken Brown @ 2013-01-28 16:42 ` toddcs 2013-01-29 3:41 ` Ken Brown 2014-07-20 14:01 ` leftwing 2014-10-21 3:23 ` Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) Don MacDougall 5 siblings, 1 reply; 54+ messages in thread From: toddcs @ 2013-01-28 16:42 UTC (permalink / raw) To: cygwin I, too, am now experiencing this texlive problem during Cygwin update, in which I am trying to install Asymptote for the first time. I am on a late-model laptop with up-to-date anti-virus software. I do not experience such extreme bottlenecks at all in other contexts. -- View this message in context: http://cygwin.1069669.n5.nabble.com/Setup-2-774-texlive-postinstall-takes-10-hours-resending-due-to-cygwin-bounce-tp92260p95720.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2013-01-28 16:42 ` toddcs @ 2013-01-29 3:41 ` Ken Brown 2013-02-05 15:48 ` jeremycraven 0 siblings, 1 reply; 54+ messages in thread From: Ken Brown @ 2013-01-29 3:41 UTC (permalink / raw) To: cygwin On 1/28/2013 11:41 AM, toddcs wrote: > I, too, am now experiencing this texlive problem during Cygwin update, in > which I am trying to install Asymptote for the first time. I am on a > late-model laptop with up-to-date anti-virus software. I do not experience > such extreme bottlenecks at all in other contexts. How about supplying some details? There should be information in /var/log/setup.log and /var/log/setup.log.full that would tell you where the delays were and, perhaps, why. 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2013-01-29 3:41 ` Ken Brown @ 2013-02-05 15:48 ` jeremycraven 2013-02-05 16:37 ` marco atzeri 2013-02-05 16:43 ` Ken Brown 0 siblings, 2 replies; 54+ messages in thread From: jeremycraven @ 2013-02-05 15:48 UTC (permalink / raw) To: cygwin I am just reinstalling cygwin on a fresh install of XP on a rather old laptop with Avast as virus software. It is absolutely crawling at the texlive postinstallation stage - stuck showing 24-25% for at least half an hour now. I was about to give up but googled "cygwin install hangs texlive-collection" and was surprised to actually hit something so will leave it to run over night. Previous installs went a lot lot quicker. There is no /var/log/setup.log etc that I can see yet ( only an empty file setup.log.postinstallXa03208 in C:\cygwin\var\log). I can confirm kpsewhich.exe is taking most of the CPU. Jeremy -- View this message in context: http://cygwin.1069669.n5.nabble.com/Setup-2-774-texlive-postinstall-takes-10-hours-resending-due-to-cygwin-bounce-tp92260p95900.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2013-02-05 15:48 ` jeremycraven @ 2013-02-05 16:37 ` marco atzeri 2013-02-05 16:43 ` Ken Brown 1 sibling, 0 replies; 54+ messages in thread From: marco atzeri @ 2013-02-05 16:37 UTC (permalink / raw) To: cygwin On 2/5/2013 4:48 PM, jeremycraven wrote: > I am just reinstalling cygwin on a fresh install of XP on a rather old laptop > with Avast as virus software. > > It is absolutely crawling at the texlive postinstallation stage - stuck > showing 24-25% for at least half an hour now. I was about to give up but > googled "cygwin install hangs texlive-collection" and was surprised to > actually hit something so will leave it to run over night. > > Previous installs went a lot lot quicker. > > There is no /var/log/setup.log etc that I can see yet ( only an empty file > setup.log.postinstallXa03208 in C:\cygwin\var\log). > > I can confirm kpsewhich.exe is taking most of the CPU. > > Jeremy > > Hi Jeremy, just for curiosity, how many texlive-collections did you select for installation ? Regards Marco -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2013-02-05 15:48 ` jeremycraven 2013-02-05 16:37 ` marco atzeri @ 2013-02-05 16:43 ` Ken Brown 2013-02-06 9:52 ` jeremycraven 1 sibling, 1 reply; 54+ messages in thread From: Ken Brown @ 2013-02-05 16:43 UTC (permalink / raw) To: cygwin On 2/5/2013 10:48 AM, jeremycraven wrote: > I am just reinstalling cygwin on a fresh install of XP on a rather old laptop > with Avast as virus software. > > It is absolutely crawling at the texlive postinstallation stage - stuck > showing 24-25% for at least half an hour now. I was about to give up but > googled "cygwin install hangs texlive-collection" and was surprised to > actually hit something so will leave it to run over night. The texlive-collection-* postinstall scripts have to do a lot of work, and it takes time. You didn't say which of these packages you've installed. There are almost 100 of them, and most TeX users only need a few. See the announcement at http://cygwin.com/ml/cygwin-announce/2012-07/msg00013.html for some advice. > Previous installs went a lot lot quicker. > > There is no /var/log/setup.log etc that I can see yet ( only an empty file > setup.log.postinstallXa03208 in C:\cygwin\var\log). The log files will be available when setup.exe finishes. Please look at them and see if there's anything interesting to report. > I can confirm kpsewhich.exe is taking most of the CPU. Not surprising. 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2013-02-05 16:43 ` Ken Brown @ 2013-02-06 9:52 ` jeremycraven 2013-02-06 14:11 ` Ken Brown 0 siblings, 1 reply; 54+ messages in thread From: jeremycraven @ 2013-02-06 9:52 UTC (permalink / raw) To: cygwin I did not change anything in the "Publishing" section, so all were at default, unless one of my other choices chnaged them due to dependencies (see end of this post as well). Elsewhere as far as I remember I added all of X11, python, and editors, rxvt , tcsh shell, and Imagemagick. Of those the only mildly suspicious one is the tex wysiwyg editor. I seem to have ended up with your "standard" install (according to the texlive advice that you pointed me to) when I look at the things in publishing marked "KEEP" and referring to "texlive" (e.g. have the ...latexrecommended one). (Is there any other way to know what non standard items one chose in the future?). The key timings in the full log file are: 13:23 started whole process 15:00 postinstall started 15:12-15:56 texlive things 16:08-16:56 more texlive things 17:00 finished so I make it 90 mins out of 210 mins were texlive. Maybe that is as it should be, but is this what would happen if I had not touched the "default" install settings? I think like others, I nearly lost faith that my computer was still working - it was only because I knew cygwin was so valuable to me that I persevered. In a first time try I might well have given up. (The upside of this is I can try and see if this latex install copes on a file someone sent me where my ubuntu one failed!) I notice the following lines near the top of the log files: 2013/02/05 13:27:23 Adding required dependency texlive: Selecting version 20120628-1 for installation. 2013/02/05 13:27:23 Adding required dependency texlive-collection-basic: Selecting version 20120628-2 for installation. 2013/02/05 13:27:23 Adding required dependency texlive-collection-documentation-base: Selecting version 20120628-1 for installation. 2013/02/05 13:27:23 Adding required dependency texlive-collection-fontsextra: Selecting version 20120628-1 for installation. 2013/02/05 13:27:23 Adding required dependency texlive-collection-fontsrecommended: Selecting version 20120628-1 for installation. 2013/02/05 13:27:23 Adding required dependency texlive-collection-fontutils: Selecting version 20120628-1 for installation. 2013/02/05 13:27:23 Adding required dependency texlive-collection-genericrecommended: Selecting version 20120628-1 for installation. 2013/02/05 13:27:23 Adding required dependency texlive-collection-htmlxml: Selecting version 20120628-1 for installation. 2013/02/05 13:27:23 Adding required dependency texlive-collection-latex: Selecting version 20120628-1 for installation. 2013/02/05 13:27:23 Adding required dependency texlive-collection-latexextra: Selecting version 20120628-1 for installation. 2013/02/05 13:27:23 Adding required dependency texlive-collection-latexrecommended: Selecting version 20120628-1 for installation. 2013/02/05 13:27:23 Adding required dependency texlive-collection-pictures: Selecting version 20120628-1 for installation. 2013/02/05 13:27:23 Adding required dependency texlive-collection-science: Selecting version 20120628-1 for installation. 2013/02/05 13:27:23 Adding required dependency texlive-collection-texinfo: Selecting version 20120628-1 for installation. I don't know if that indicates extra dependencies beyond the default, and if so I wonder what triggered them. I can send you the log files if you suggest where best to send them. Cheers Jeremy -- 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 -- View this message in context: http://cygwin.1069669.n5.nabble.com/Setup-2-774-texlive-postinstall-takes-10-hours-resending-due-to-cygwin-bounce-tp92260p95923.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2013-02-06 9:52 ` jeremycraven @ 2013-02-06 14:11 ` Ken Brown 0 siblings, 0 replies; 54+ messages in thread From: Ken Brown @ 2013-02-06 14:11 UTC (permalink / raw) To: cygwin On 2/6/2013 4:52 AM, jeremycraven wrote: > > I did not change anything in the "Publishing" section, so all were at > default, unless one of my other choices chnaged them due to dependencies Nothing from TeX Live is installed by default. So everything you installed came from dependencies. > (see end of this post as well). Elsewhere as far as I remember I added all > of X11, python, and editors, rxvt , tcsh shell, and Imagemagick. Of those > the only mildly suspicious one is the tex wysiwyg editor. I assume you're talking about lyx. Take a look at the setup.ini file in your Cygwin download directory, and you'll see that lyx requires quite a few texlive-collection-* packages. It probably shouldn't require so many, but this was a decision made by the lyx maintainer (who just resigned as maintainer). > I seem to have ended up with your "standard" install (according to the > texlive advice that you pointed me to) when I look at the things in > publishing marked "KEEP" and referring to "texlive" (e.g. have the > ...latexrecommended one). (Is there any other way to know what non standard > items one chose in the future?). After you select packages and click "Next", setup.exe will pop up a dialogue box warning you if there are dependencies that you need to install. For each one, it will tell you which package(s) it depends on. > The key timings in the full log file are: > 13:23 started whole process > 15:00 postinstall started > 15:12-15:56 texlive things > 16:08-16:56 more texlive things > 17:00 finished > > so I make it 90 mins out of 210 mins were texlive. > > Maybe that is as it should be, but is this what would happen if I had not > touched the "default" install settings? No, it would have been much faster. For one thing, you wouldn't have installed anything from TeX Live. > I think like others, I nearly lost faith that my computer was still working > - it was only because I knew cygwin was so valuable to me that I persevered. > In a first time try I might well have given up. A user installing Cygwin for the first time would be well advised to start by accepting all the defaults. > (The upside of this is I can try and see if this latex install copes on a > file someone sent me where my ubuntu one failed!) > > I notice the following lines near the top of the log files: > > 2013/02/05 13:27:23 Adding required dependency texlive: Selecting version > 20120628-1 for installation. > 2013/02/05 13:27:23 Adding required dependency texlive-collection-basic: > Selecting version 20120628-2 for installation. > 2013/02/05 13:27:23 Adding required dependency > texlive-collection-documentation-base: Selecting version 20120628-1 for > installation. > 2013/02/05 13:27:23 Adding required dependency > texlive-collection-fontsextra: Selecting version 20120628-1 for > installation. > 2013/02/05 13:27:23 Adding required dependency > texlive-collection-fontsrecommended: Selecting version 20120628-1 for > installation. > 2013/02/05 13:27:23 Adding required dependency texlive-collection-fontutils: > Selecting version 20120628-1 for installation. > 2013/02/05 13:27:23 Adding required dependency > texlive-collection-genericrecommended: Selecting version 20120628-1 for > installation. > 2013/02/05 13:27:23 Adding required dependency texlive-collection-htmlxml: > Selecting version 20120628-1 for installation. > 2013/02/05 13:27:23 Adding required dependency texlive-collection-latex: > Selecting version 20120628-1 for installation. > 2013/02/05 13:27:23 Adding required dependency > texlive-collection-latexextra: Selecting version 20120628-1 for > installation. > 2013/02/05 13:27:23 Adding required dependency > texlive-collection-latexrecommended: Selecting version 20120628-1 for > installation. > 2013/02/05 13:27:23 Adding required dependency texlive-collection-pictures: > Selecting version 20120628-1 for installation. > 2013/02/05 13:27:23 Adding required dependency texlive-collection-science: > Selecting version 20120628-1 for installation. > 2013/02/05 13:27:23 Adding required dependency texlive-collection-texinfo: > Selecting version 20120628-1 for installation. > > I don't know if that indicates extra dependencies beyond the default, and if > so I wonder what triggered them. Most or all of these were triggered by lyx. > I can send you the log files if you suggest where best to send them. I don't need to see them unless there are error messages involving texlive postinstall scripts. 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2012-08-23 11:35 Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) Martin.Fitzpatrick ` (3 preceding siblings ...) 2013-01-28 16:42 ` toddcs @ 2014-07-20 14:01 ` leftwing 2014-07-20 17:44 ` Ken Brown 2014-10-21 3:23 ` Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) Don MacDougall 5 siblings, 1 reply; 54+ messages in thread From: leftwing @ 2014-07-20 14:01 UTC (permalink / raw) To: cygwin I'm experiencing this problem right now, about 2 years after earlier discussion. I didn't choose this package - it was installed as a dependency for curl development. The post install processes have been running for hours and hours ... -- View this message in context: http://cygwin.1069669.n5.nabble.com/Setup-2-774-texlive-postinstall-takes-10-hours-resending-due-to-cygwin-bounce-tp92260p109904.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2014-07-20 14:01 ` leftwing @ 2014-07-20 17:44 ` Ken Brown 2014-10-20 22:39 ` Setup 2.774 texlive postinstall takes 10+ hours Don MacDougall 0 siblings, 1 reply; 54+ messages in thread From: Ken Brown @ 2014-07-20 17:44 UTC (permalink / raw) To: cygwin On 7/20/2014 10:00 AM, leftwing wrote: > I'm experiencing this problem right now, about 2 years after earlier > discussion. I didn't choose this package - it was installed as a dependency > for curl development. The post install processes have been running for > hours and hours ... Please make a self-contained report, with complete details. And please check more carefully to see what's pulling in texlive. I don't think it's curl. Maybe you have some obsolete packages installed that are causing this. (Uncheck the "Hide obsolete packages" box when you run setup.) 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-07-20 17:44 ` Ken Brown @ 2014-10-20 22:39 ` Don MacDougall 2014-10-21 2:09 ` Ken Brown 0 siblings, 1 reply; 54+ messages in thread From: Don MacDougall @ 2014-10-20 22:39 UTC (permalink / raw) To: cygwin I downloaded Setup.exe version 2.850 (32 bit) on Oct 18, 2014 and used it to install cygwin from scratch on an Asus Eee notebook with Atom N455 cpu. I tried to install only the default packages but it seems like that took about 8 hours to download overnight. The install went okay until it came to the /etc/postinstall/texlive-collection-basic.sh which seemed to hang for at least 12 hours. Thinking it was hung I canceled the install, but then I found this longish thread going back several years, so I restarted the install and let it run for at least 24 hours and see no more happening. It sits the whole time on this script. The "Total:" line shows 99% done and the "Package:" line shows zero progress the whole time. Is there a way to install Cygwin without installing this package, which seems to have been included in the default selection? Now that I seem to have it included can I take it out without breaking something that is too important to do without? When I restarted the install everything said "default" and I didn't change anything. Since it doesn't ever finish I don't see any log file, or indeed, ever a log directory. Thank you, Don MacDougall -- View this message in context: http://cygwin.1069669.n5.nabble.com/Setup-2-774-texlive-postinstall-takes-10-hours-resending-due-to-cygwin-bounce-tp92260p112040.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-10-20 22:39 ` Setup 2.774 texlive postinstall takes 10+ hours Don MacDougall @ 2014-10-21 2:09 ` Ken Brown 2014-10-21 2:26 ` Ken Brown 2014-10-21 4:06 ` Don MacDougall 0 siblings, 2 replies; 54+ messages in thread From: Ken Brown @ 2014-10-21 2:09 UTC (permalink / raw) To: cygwin On 10/20/2014 6:38 PM, Don MacDougall wrote: > I downloaded Setup.exe version 2.850 (32 bit) on Oct 18, 2014 and used it to > install cygwin from scratch on an Asus Eee notebook with Atom N455 cpu. I > tried to install only the default packages but it seems like that took about > 8 hours to download overnight. The install went okay until it came to the > /etc/postinstall/texlive-collection-basic.sh which seemed to hang for at > least 12 hours. Thinking it was hung I canceled the install, but then I > found this longish thread going back several years, so I restarted the > install and let it run for at least 24 hours and see no more happening. It > sits the whole time on this script. The "Total:" line shows 99% done and > the "Package:" line shows zero progress the whole time. > > Is there a way to install Cygwin without installing this package, which > seems to have been included in the default selection? I don't know what happened, but you must have inadvertently selected some packages to install that you didn't intend to choose. There are no texlive packages in a default installation. 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-10-21 2:09 ` Ken Brown @ 2014-10-21 2:26 ` Ken Brown 2014-10-21 4:06 ` Don MacDougall 1 sibling, 0 replies; 54+ messages in thread From: Ken Brown @ 2014-10-21 2:26 UTC (permalink / raw) To: cygwin On 10/20/2014 10:09 PM, Ken Brown wrote: > On 10/20/2014 6:38 PM, Don MacDougall wrote: >> I downloaded Setup.exe version 2.850 (32 bit) on Oct 18, 2014 and used >> it to >> install cygwin from scratch on an Asus Eee notebook with Atom N455 >> cpu. I >> tried to install only the default packages but it seems like that took >> about >> 8 hours to download overnight. The install went okay until it came to >> the >> /etc/postinstall/texlive-collection-basic.sh which seemed to hang for at >> least 12 hours. Thinking it was hung I canceled the install, but then I >> found this longish thread going back several years, so I restarted the >> install and let it run for at least 24 hours and see no more >> happening. It >> sits the whole time on this script. The "Total:" line shows 99% done and >> the "Package:" line shows zero progress the whole time. >> >> Is there a way to install Cygwin without installing this package, which >> seems to have been included in the default selection? > > I don't know what happened, but you must have inadvertently selected > some packages to install that you didn't intend to choose. There are no > texlive packages in a default installation. Did you by any chance click on the word "Default" near the top of the screen? If so, it would have changed to "Install", which means you've chosen to install everything. 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-10-21 2:09 ` Ken Brown 2014-10-21 2:26 ` Ken Brown @ 2014-10-21 4:06 ` Don MacDougall 2014-10-21 12:58 ` Ken Brown 1 sibling, 1 reply; 54+ messages in thread From: Don MacDougall @ 2014-10-21 4:06 UTC (permalink / raw) To: cygwin > I don't know what happened, but you must have inadvertently selected > some packages to install that you didn't intend to choose. There are no > texlive packages in a default installation. If I somehow did something like this, is there an easy way to undo it other than to delete everything and start over? Since I've already downloaded everything I've no objection to having it install, especially since the install says it's 99% complete, but this one package seems to hold everything up and when I try to install everything else while uninstalling this one package, the installer still stalls at the same postinstall script. Might I presume that it can't uninstall till it first completes the install? If that's the case, then I suppose I'll just leave it set to install and let it run for 3 or 4 days in the hope it'll eventually complete. Most of the other postinstall scripts and the whole rest of the install process ran in no more than a few hours. Don -- View this message in context: http://cygwin.1069669.n5.nabble.com/Setup-2-774-texlive-postinstall-takes-10-hours-resending-due-to-cygwin-bounce-tp92260p112047.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-10-21 4:06 ` Don MacDougall @ 2014-10-21 12:58 ` Ken Brown 2014-10-24 7:11 ` Don MacDougall 0 siblings, 1 reply; 54+ messages in thread From: Ken Brown @ 2014-10-21 12:58 UTC (permalink / raw) To: cygwin On 10/21/2014 12:06 AM, Don MacDougall wrote: >> I don't know what happened, but you must have inadvertently selected >> some packages to install that you didn't intend to choose. There are no >> texlive packages in a default installation. > > If I somehow did something like this, is there an easy way to undo it other > than to delete everything and start over? Since I've already downloaded > everything I've no objection to having it install, especially since the > install says it's 99% complete, but this one package seems to hold > everything up and when I try to install everything else while uninstalling > this one package, the installer still stalls at the same postinstall script. > Might I presume that it can't uninstall till it first completes the install? > If that's the case, then I suppose I'll just leave it set to install and let > it run for 3 or 4 days in the hope it'll eventually complete. Most of the > other postinstall scripts and the whole rest of the install process ran in > no more than a few hours. I wouldn't try to restart the install without figuring out why /etc/postinstall/texlive-collection-basic.sh didn't complete. Is there anything at all in /var/log/ that might provide a clue? Usually setup writes temporary files while it's executing postinstall scripts. 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-10-21 12:58 ` Ken Brown @ 2014-10-24 7:11 ` Don MacDougall 2014-10-24 11:35 ` Andrey Repin 0 siblings, 1 reply; 54+ messages in thread From: Don MacDougall @ 2014-10-24 7:11 UTC (permalink / raw) To: cygwin > I wouldn't try to restart the install without figuring out why > /etc/postinstall/texlive-collection-basic.sh didn't complete. Is there > anything > at all in /var/log/ that might provide a clue? Usually setup writes > temporary > files while it's executing postinstall scripts. There wasn't even a /var/log directory until the install was finished. What I finally did to get it to finish was to move all the texlive-collection files out of the postinstall directory and the install process finished all the rest quite rapidly. Then I put them back, except for the language packages, and reran the install program and one by one moved the files back out again if they stalled. In the end there were 8 that wouldn't run. In the temporary logs are a lot of error messages similar to the following three: Can't fork, trying again in 5 seconds at /usr/bin/updmap line 59. 7 [main] perl 8088 child_info_fork::abort: unable to remap Fcntl.dll to same address as parent (0x2E0000) - try running rebaseall Can't fork, trying again in 5 seconds at /usr/bin/updmap line 59. 6 [main] perl 8056 child_info_fork::abort: address space needed by 'MD5.dll' (0x2D0000) is already occupied Can't fork, trying again in 5 seconds at /usr/bin/updmap line 59. 5 [main] perl 8076 child_info_fork::abort: address space needed by 'IO.dll' (0x2F0000) is already occupied I looked for updmap but there doesn't appear to be even a /usr/bin directory, so I must be looking in the wrong place. In any case, I did get the install to complete by this rather ugly method except for those 8 packages and all the language files. I don't know if this method will have fouled up anything else or not. If the log files would be of any value to you, I've put them here: http://www.macdougalls.net/cygwinlogs/ Thanks for your help, Don -- View this message in context: http://cygwin.1069669.n5.nabble.com/Setup-2-774-texlive-postinstall-takes-10-hours-resending-due-to-cygwin-bounce-tp92260p112141.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-10-24 7:11 ` Don MacDougall @ 2014-10-24 11:35 ` Andrey Repin 2014-10-29 5:06 ` Don MacDougall 0 siblings, 1 reply; 54+ messages in thread From: Andrey Repin @ 2014-10-24 11:35 UTC (permalink / raw) To: Don MacDougall, cygwin Greetings, Don MacDougall! >> I wouldn't try to restart the install without figuring out why >> /etc/postinstall/texlive-collection-basic.sh didn't complete. Is there >> anything >> at all in /var/log/ that might provide a clue? Usually setup writes >> temporary >> files while it's executing postinstall scripts. > There wasn't even a /var/log directory until the install was finished. What > I finally did to get it to finish was to move all the texlive-collection > files out of the postinstall directory and the install process finished all > the rest quite rapidly. Then I put them back, except for the language > packages, and reran the install program and one by one moved the files back > out again if they stalled. In the end there were 8 that wouldn't run. In > the temporary logs are a lot of error messages similar to the following > three: > Can't fork, trying again in 5 seconds at /usr/bin/updmap line 59. > 7 [main] perl 8088 child_info_fork::abort: unable to remap Fcntl.dll > to same address as parent (0x2E0000) - try running rebaseall > Can't fork, trying again in 5 seconds at /usr/bin/updmap line 59. > 6 [main] perl 8056 child_info_fork::abort: address space needed by > 'MD5.dll' (0x2D0000) is already occupied > Can't fork, trying again in 5 seconds at /usr/bin/updmap line 59. > 5 [main] perl 8076 child_info_fork::abort: address space needed by > 'IO.dll' (0x2F0000) is already occupied This could happen, if you install too many packages on a 32-bit Cygwin, or there's an interference in your system that break memory layout of applications. (I.e. BLODA) > I looked for updmap but there doesn't appear to be even a /usr/bin > directory, so I must be looking in the wrong place. You're looking in the wrong place. Whole Cygwin is installed in that directory. > In any case, I did get the install to complete by this rather ugly method > except for those 8 packages and all the language files. I don't know if this > method will have fouled up anything else or not. > If the log files would be of any value to you, I've put them here: > http://www.macdougalls.net/cygwinlogs/ -- WBR, Andrey Repin (anrdaemon@yandex.ru) 24.10.2014, <15:26> Sorry for my terrible english... -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-10-24 11:35 ` Andrey Repin @ 2014-10-29 5:06 ` Don MacDougall 2014-10-29 12:20 ` Andrey Repin 0 siblings, 1 reply; 54+ messages in thread From: Don MacDougall @ 2014-10-29 5:06 UTC (permalink / raw) To: cygwin > This could happen, if you install too many packages on a 32-bit Cygwin, or > there's an interference in your system that break memory layout of > applications. (I.e. BLODA) I think you might be right and getting to the bottom of it looks looks like it'll take a lot longer than I was counting on spending right now, so I think I'll have to suspend this till I have more time to spend on it. I didn't intend to install so many packages, and now that I have done so accidentally, I haven't found an easy way to go back to the default installation, but if there is a way without starting over from scratch I'd be interested in a pointer to any documentation on it. And your English seems near perfect to me. I wouldn't have known your weren't a native speaker if you hadn't let on. Thanks for your help and others who have helped also. Don MacDougall -- View this message in context: http://cygwin.1069669.n5.nabble.com/Setup-2-774-texlive-postinstall-takes-10-hours-resending-due-to-cygwin-bounce-tp92260p112282.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-10-29 5:06 ` Don MacDougall @ 2014-10-29 12:20 ` Andrey Repin 2014-10-30 22:27 ` Don MacDougall 0 siblings, 1 reply; 54+ messages in thread From: Andrey Repin @ 2014-10-29 12:20 UTC (permalink / raw) To: Don MacDougall, cygwin Greetings, Don MacDougall! >> This could happen, if you install too many packages on a 32-bit Cygwin, or >> there's an interference in your system that break memory layout of >> applications. (I.e. BLODA) > I think you might be right and getting to the bottom of it looks looks like > it'll > take a lot longer than I was counting on spending right now, so I think I'll > have to suspend this till I have more time to spend on it. > I didn't intend to install so many packages, and now that I have done so > accidentally, I haven't found an easy way to go back to the default > installation, > but if there is a way without starting over from scratch I'd be interested > in a > pointer to any documentation on it. Since you've already downloaded the packages, you can just remove the installed directory (don't remove setupXXX.exe or mirror copies! Only the directory where you've it installed) and restart setup in "install from local directory" mode. That'd be the fastest way. You'll just have to re-run setup afterward to update installed components from internet. -- WBR, Andrey Repin (anrdaemon@yandex.ru) 29.10.2014, <15:10> Sorry for my terrible english... -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-10-29 12:20 ` Andrey Repin @ 2014-10-30 22:27 ` Don MacDougall 2014-11-02 18:02 ` Ken Brown 0 siblings, 1 reply; 54+ messages in thread From: Don MacDougall @ 2014-10-30 22:27 UTC (permalink / raw) To: cygwin >> ...if there is a way (to begin again to install default packages) without >> starting over >> from scratch I'd be interested in a pointer to any documentation on it. > > Since you've already downloaded the packages, you can just remove the > installed directory (don't remove setupXXX.exe or mirror copies! Only the > directory where you've it installed) and restart setup in "install from > local directory" mode. > That'd be the fastest way. You'll just have to re-run setup afterward to > update installed components from internet. Thank you for the advice. I moved the installed directory (29 GB) aside and restarted the install, carefully avoiding changing any of the default settings, and this time it finished in a couple of minutes and the install directory is only 158 MB and I find a cygwin terminal and am able to do routine bash commands, so I presume that all is working. So, why the postinst scripts failed to run before, now becomes an academic matter for me. Thanks again for the help. Don MacDougall -- View this message in context: http://cygwin.1069669.n5.nabble.com/Setup-2-774-texlive-postinstall-takes-10-hours-resending-due-to-cygwin-bounce-tp92260p112334.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-10-30 22:27 ` Don MacDougall @ 2014-11-02 18:02 ` Ken Brown 2014-11-03 10:25 ` Corinna Vinschen 0 siblings, 1 reply; 54+ messages in thread From: Ken Brown @ 2014-11-02 18:02 UTC (permalink / raw) To: cygwin On 10/30/2014 6:27 PM, Don MacDougall wrote: > So, why the > postinst scripts failed to run before, now becomes an academic matter for > me. Nevertheless, let me point out for the sake of the archives that the answer was contained in one of your earlier messages: On 10/24/2014 3:11 AM, Don MacDougall wrote: > Can't fork, trying again in 5 seconds at /usr/bin/updmap line 59. > 7 [main] perl 8088 child_info_fork::abort: unable to remap Fcntl.dll > to same address as parent (0x2E0000) - try running rebaseall The problem is that many of the texlive postinstall scripts run perl scripts, and these failed as above because rebaseall needed to be run. I guess this problem will occur whenever perl and texlive are installed simultaneously. I'm not sure what the solution is. Would it be hard to tweak setup.exe so that it runs the autorebase postinstall script before running any others? Or would this be a bad idea for other reasons? 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-02 18:02 ` Ken Brown @ 2014-11-03 10:25 ` Corinna Vinschen 2014-11-03 12:44 ` Ken Brown 2014-11-03 18:03 ` Achim Gratz 0 siblings, 2 replies; 54+ messages in thread From: Corinna Vinschen @ 2014-11-03 10:25 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 2297 bytes --] On Nov 2 13:02, Ken Brown wrote: > On 10/30/2014 6:27 PM, Don MacDougall wrote: > >So, why the > >postinst scripts failed to run before, now becomes an academic matter for > >me. > > Nevertheless, let me point out for the sake of the archives that the answer > was contained in one of your earlier messages: > > On 10/24/2014 3:11 AM, Don MacDougall wrote: > > Can't fork, trying again in 5 seconds at /usr/bin/updmap line 59. > > 7 [main] perl 8088 child_info_fork::abort: unable to remap Fcntl.dll > > to same address as parent (0x2E0000) - try running rebaseall > > The problem is that many of the texlive postinstall scripts run perl > scripts, and these failed as above because rebaseall needed to be run. I > guess this problem will occur whenever perl and texlive are installed > simultaneously. > > I'm not sure what the solution is. Would it be hard to tweak setup.exe so > that it runs the autorebase postinstall script before running any others? > Or would this be a bad idea for other reasons? Off the top of my head I don't know how hard that would be, but it doesn't sound like an especially bad idea to me. Au contraire. The only reasons not to do that would be if an installer script would move DLLs around (Do we have that? I hope not) or if there's a simpler solution. One thing we could test is if we can't get away without tweaking setup.exe, by changing the dependencies only. Right now _autorebase requires rebase and dash packages. Both are in Base anyway, but they pull in more dependencies which result in something like a rat tail of dependencies. So I'm wondering if tweaking _autorebase' setup.hint file like this: sdesc: "Run rebaseall automatically" #external-source: rebase category: _PostInstallLast -requires: rebase dash autodep: .*/[^/]*\.(?:dll|so|oct)$ incver_ifdep: yes +noautodep: cygwin and tweaking cygwin's setup.hint file like this: sdesc: "The UNIX emulation engine" category: Base -requires: base-cygwin +requires: base-cygwin _autorebase noautodep: _update-info-dir autodep: .* would do the trick. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-03 10:25 ` Corinna Vinschen @ 2014-11-03 12:44 ` Ken Brown 2014-11-03 14:52 ` Corinna Vinschen 2014-11-03 18:03 ` Achim Gratz 1 sibling, 1 reply; 54+ messages in thread From: Ken Brown @ 2014-11-03 12:44 UTC (permalink / raw) To: cygwin On 11/3/2014 5:25 AM, Corinna Vinschen wrote: > On Nov 2 13:02, Ken Brown wrote: >> On 10/30/2014 6:27 PM, Don MacDougall wrote: >>> So, why the >>> postinst scripts failed to run before, now becomes an academic matter for >>> me. >> >> Nevertheless, let me point out for the sake of the archives that the answer >> was contained in one of your earlier messages: >> >> On 10/24/2014 3:11 AM, Don MacDougall wrote: >>> Can't fork, trying again in 5 seconds at /usr/bin/updmap line 59. >>> 7 [main] perl 8088 child_info_fork::abort: unable to remap Fcntl.dll >>> to same address as parent (0x2E0000) - try running rebaseall >> >> The problem is that many of the texlive postinstall scripts run perl >> scripts, and these failed as above because rebaseall needed to be run. I >> guess this problem will occur whenever perl and texlive are installed >> simultaneously. >> >> I'm not sure what the solution is. Would it be hard to tweak setup.exe so >> that it runs the autorebase postinstall script before running any others? >> Or would this be a bad idea for other reasons? > > Off the top of my head I don't know how hard that would be, but it > doesn't sound like an especially bad idea to me. Au contraire. > > The only reasons not to do that would be if an installer script would > move DLLs around (Do we have that? I hope not) or if there's a simpler > solution. > > One thing we could test is if we can't get away without tweaking > setup.exe, by changing the dependencies only. Right now _autorebase > requires rebase and dash packages. Both are in Base anyway, but they > pull in more dependencies which result in something like a rat tail of > dependencies. So I'm wondering if tweaking _autorebase' setup.hint file > like this: It's worth a try. > sdesc: "Run rebaseall automatically" > #external-source: rebase > category: _PostInstallLast ^^^^^^^^^^^^^^^ Wouldn't we also have to get rid of this? > -requires: rebase dash > autodep: .*/[^/]*\.(?:dll|so|oct)$ > incver_ifdep: yes > +noautodep: cygwin > > and tweaking cygwin's setup.hint file like this: > > sdesc: "The UNIX emulation engine" > category: Base > -requires: base-cygwin > +requires: base-cygwin _autorebase > noautodep: _update-info-dir > autodep: .* > > would do the trick. 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-03 12:44 ` Ken Brown @ 2014-11-03 14:52 ` Corinna Vinschen 2014-11-03 16:17 ` Corinna Vinschen 0 siblings, 1 reply; 54+ messages in thread From: Corinna Vinschen @ 2014-11-03 14:52 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 2524 bytes --] On Nov 3 07:43, Ken Brown wrote: > On 11/3/2014 5:25 AM, Corinna Vinschen wrote: > >On Nov 2 13:02, Ken Brown wrote: > >>On 10/30/2014 6:27 PM, Don MacDougall wrote: > >>>So, why the > >>>postinst scripts failed to run before, now becomes an academic matter for > >>>me. > >> > >>Nevertheless, let me point out for the sake of the archives that the answer > >>was contained in one of your earlier messages: > >> > >>On 10/24/2014 3:11 AM, Don MacDougall wrote: > >>>Can't fork, trying again in 5 seconds at /usr/bin/updmap line 59. > >>> 7 [main] perl 8088 child_info_fork::abort: unable to remap Fcntl.dll > >>>to same address as parent (0x2E0000) - try running rebaseall > >> > >>The problem is that many of the texlive postinstall scripts run perl > >>scripts, and these failed as above because rebaseall needed to be run. I > >>guess this problem will occur whenever perl and texlive are installed > >>simultaneously. > >> > >>I'm not sure what the solution is. Would it be hard to tweak setup.exe so > >>that it runs the autorebase postinstall script before running any others? > >>Or would this be a bad idea for other reasons? > > > >Off the top of my head I don't know how hard that would be, but it > >doesn't sound like an especially bad idea to me. Au contraire. > > > >The only reasons not to do that would be if an installer script would > >move DLLs around (Do we have that? I hope not) or if there's a simpler > >solution. > > > >One thing we could test is if we can't get away without tweaking > >setup.exe, by changing the dependencies only. Right now _autorebase > >requires rebase and dash packages. Both are in Base anyway, but they > >pull in more dependencies which result in something like a rat tail of > >dependencies. So I'm wondering if tweaking _autorebase' setup.hint file > >like this: > > It's worth a try. > > > sdesc: "Run rebaseall automatically" > > #external-source: rebase > > category: _PostInstallLast > ^^^^^^^^^^^^^^^ > Wouldn't we also have to get rid of this? This is just a category name, and to the best of my knowledge there's no special handling in terms of this category name in either setup or upset. It just starts with an underscore so that packages in this category don't show up in setup's package selection by default. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-03 14:52 ` Corinna Vinschen @ 2014-11-03 16:17 ` Corinna Vinschen 0 siblings, 0 replies; 54+ messages in thread From: Corinna Vinschen @ 2014-11-03 16:17 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 2806 bytes --] On Nov 3 15:52, Corinna Vinschen wrote: > On Nov 3 07:43, Ken Brown wrote: > > On 11/3/2014 5:25 AM, Corinna Vinschen wrote: > > >On Nov 2 13:02, Ken Brown wrote: > > >>On 10/24/2014 3:11 AM, Don MacDougall wrote: > > >>>Can't fork, trying again in 5 seconds at /usr/bin/updmap line 59. > > >>> 7 [main] perl 8088 child_info_fork::abort: unable to remap Fcntl.dll > > >>>to same address as parent (0x2E0000) - try running rebaseall > > >> > > >>The problem is that many of the texlive postinstall scripts run perl > > >>scripts, and these failed as above because rebaseall needed to be run. I > > >>guess this problem will occur whenever perl and texlive are installed > > >>simultaneously. > > >> > > >>I'm not sure what the solution is. Would it be hard to tweak setup.exe so > > >>that it runs the autorebase postinstall script before running any others? > > >>Or would this be a bad idea for other reasons? > > > > > >Off the top of my head I don't know how hard that would be, but it > > >doesn't sound like an especially bad idea to me. Au contraire. > > > > > >The only reasons not to do that would be if an installer script would > > >move DLLs around (Do we have that? I hope not) or if there's a simpler > > >solution. > > > > > >One thing we could test is if we can't get away without tweaking > > >setup.exe, by changing the dependencies only. Right now _autorebase > > >requires rebase and dash packages. Both are in Base anyway, but they > > >pull in more dependencies which result in something like a rat tail of > > >dependencies. So I'm wondering if tweaking _autorebase' setup.hint file > > >like this: > > > > It's worth a try. I changed that now on sourceware, but please keep in mind that this doesn't solve all problems. Assuming you update a few packages and then start setup again and install some more packages, then the version number of the _autorebase package hasn't changed and it won't be started by the second setup run. Only if a package gets updated which comes with DLLs, the _autorebase version number is bumped on the server and only then it will be started by setup anew. Same thing for _update-info-dir, but with minor consequences. In theory, we could need a solution which is built into setup, and which makes setup re-run the _autorebase script every time a package with DLLs is updated or installed. Analog for _update-info-dir. The dependency thingy is fine in upset, but the logic needs some support on the client side it seems. I would not be too unhappy if somebody would like to take a stab at setup's code for this... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-03 10:25 ` Corinna Vinschen 2014-11-03 12:44 ` Ken Brown @ 2014-11-03 18:03 ` Achim Gratz 2014-11-03 22:04 ` Ken Brown 2014-11-04 9:00 ` Corinna Vinschen 1 sibling, 2 replies; 54+ messages in thread From: Achim Gratz @ 2014-11-03 18:03 UTC (permalink / raw) To: cygwin Corinna Vinschen writes: > Off the top of my head I don't know how hard that would be, but it > doesn't sound like an especially bad idea to me. Au contraire. It should be quite easy since the postinstall scripts are run in POSIX sort order. Just give the script a name like 00001_autorebase.bat and it should always be the first one that runs. > One thing we could test is if we can't get away without tweaking > setup.exe, by changing the dependencies only. Right now _autorebase > requires rebase and dash packages. Both are in Base anyway, but they > pull in more dependencies which result in something like a rat tail of > dependencies. So I'm wondering if tweaking _autorebase' setup.hint file > like this: Dependencies are not evaluated at all when installing or running scripts. But it would really be better to use triggers for these sort of scripts. I have something implemented for my "perpetual" postinstall that does an incremental rebase after each setup run, but it could be extended to be controlled by setup.ini instead of a naming convention. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ DIY Stuff: http://Synth.Stromeko.net/DIY.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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-03 18:03 ` Achim Gratz @ 2014-11-03 22:04 ` Ken Brown 2014-11-04 16:21 ` Achim Gratz 2014-11-04 9:00 ` Corinna Vinschen 1 sibling, 1 reply; 54+ messages in thread From: Ken Brown @ 2014-11-03 22:04 UTC (permalink / raw) To: cygwin On 11/3/2014 1:03 PM, Achim Gratz wrote: > Corinna Vinschen writes: >> Off the top of my head I don't know how hard that would be, but it >> doesn't sound like an especially bad idea to me. Au contraire. > > It should be quite easy since the postinstall scripts are run in POSIX > sort order. That's now what I see here, unless I'm badly confused about what POSIX sort order is. I did an update a few days ago in which the postinstall scripts were run in the following order: update-info-dir.sh autorebase.bat wget.sh > Just give the script a name like 00001_autorebase.bat and > it should always be the first one that runs. > >> One thing we could test is if we can't get away without tweaking >> setup.exe, by changing the dependencies only. Right now _autorebase >> requires rebase and dash packages. Both are in Base anyway, but they >> pull in more dependencies which result in something like a rat tail of >> dependencies. So I'm wondering if tweaking _autorebase' setup.hint file >> like this: > > Dependencies are not evaluated at all when installing or running > scripts. > > But it would really be better to use triggers for these sort of scripts. > I have something implemented for my "perpetual" postinstall that does an > incremental rebase after each setup run, but it could be extended to be > controlled by setup.ini instead of a naming convention. 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-03 22:04 ` Ken Brown @ 2014-11-04 16:21 ` Achim Gratz 0 siblings, 0 replies; 54+ messages in thread From: Achim Gratz @ 2014-11-04 16:21 UTC (permalink / raw) To: cygwin Ken Brown writes: > That's now what I see here, unless I'm badly confused about what POSIX > sort order is. I did an update a few days ago in which the > postinstall scripts were run in the following order: > > update-info-dir.sh > autorebase.bat > wget.sh Yes you are right. Sorry, I should have looked at it more thoroughly. Anyway, I still think that we'd either should special-case autorebase (like I do locally for this and other reasons) or introduce triggers and trigger dependencies to setup. That would also make the texlive postinstall a lot less time-consuming. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-03 18:03 ` Achim Gratz 2014-11-03 22:04 ` Ken Brown @ 2014-11-04 9:00 ` Corinna Vinschen 2014-11-11 4:23 ` Yaakov Selkowitz 1 sibling, 1 reply; 54+ messages in thread From: Corinna Vinschen @ 2014-11-04 9:00 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 1733 bytes --] On Nov 3 19:03, Achim Gratz wrote: > Corinna Vinschen writes: > > Off the top of my head I don't know how hard that would be, but it > > doesn't sound like an especially bad idea to me. Au contraire. > > It should be quite easy since the postinstall scripts are run in POSIX > sort order. Just give the script a name like 00001_autorebase.bat and > it should always be the first one that runs. > > > One thing we could test is if we can't get away without tweaking > > setup.exe, by changing the dependencies only. Right now _autorebase > > requires rebase and dash packages. Both are in Base anyway, but they > > pull in more dependencies which result in something like a rat tail of > > dependencies. So I'm wondering if tweaking _autorebase' setup.hint file > > like this: > > Dependencies are not evaluated at all when installing or running > scripts. That's not correct. From the dependencies, setup generates a dependency graph which is used to get a sequential order in which to call the scripts. See /var/log/setup.log.full, it contains the dependency order before starting the scripts. Years ago we had some trouble to get the base-cygwin script running first due to a couple of dependency loops. And we have such loops again, apparently. My dependency list on 64 bit (not all packages installed) now starts like this: libbz2_1 _autorebase cygwin zlib0 libpng15 ... The worst thing AFAICS is that base-cygwin only comes after lots and lots of other packages for some reason. This needs some investigation. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-04 9:00 ` Corinna Vinschen @ 2014-11-11 4:23 ` Yaakov Selkowitz 2014-11-11 4:33 ` Yaakov Selkowitz 0 siblings, 1 reply; 54+ messages in thread From: Yaakov Selkowitz @ 2014-11-11 4:23 UTC (permalink / raw) To: cygwin On 2014-11-04 02:59, Corinna Vinschen wrote: > On Nov 3 19:03, Achim Gratz wrote: >> Dependencies are not evaluated at all when installing or running >> scripts. > > That's not correct. From the dependencies, setup generates a dependency > graph which is used to get a sequential order in which to call > the scripts. See /var/log/setup.log.full, it contains the dependency > order before starting the scripts. > > Years ago we had some trouble to get the base-cygwin script running > first due to a couple of dependency loops. And we have such loops > again, apparently. My dependency list on 64 bit (not all packages > installed) now starts like this: > > libbz2_1 _autorebase cygwin zlib0 libpng15 ... > > The worst thing AFAICS is that base-cygwin only comes after lots and > lots of other packages for some reason. > > This needs some investigation. There are two issues here: 1) upset was adding a requires: _autorebase to cygwin, which is incorrect because it requires dash and rebase, each of which (should) require cygwin (resulting in a dependency loop), not to mention that cygwin1.dll is never rebased. 2) Several libraries were missing requires: cygwin _autorebase, causing them to precede cygwin (and hence base-cygwin) in the dependency chain. I still have yet to understand why for some packages the autodep works and for others not. But by adding those requires to a downloaded setup.ini, resulting in the following: Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode libstdc++6 terminfo sed gzip libpcre1 grep libreadline7 bash libncursesw10 info _update-info-dir libgmp10 libiconv2 libintl8 libattr1 coreutils rebase _autorebase ... What libgcc1 is doing there first, I still don't know (it does have a requires: _autorebase cygwin). The other thing I realized is that Ports packages are missing these autodeps; only by chance (and that many of them depend on other distro libraries) do they not seem to interfere with the dependency order. The question is, can we just make the incver_ifdep code not dependent on autodep, then just have cygport add these dependencies to setup.hint and drop the apparently fragile autodep code from upset? Yaakov -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-11 4:23 ` Yaakov Selkowitz @ 2014-11-11 4:33 ` Yaakov Selkowitz 2014-11-11 11:53 ` Corinna Vinschen 0 siblings, 1 reply; 54+ messages in thread From: Yaakov Selkowitz @ 2014-11-11 4:33 UTC (permalink / raw) To: cygwin On 2014-11-10 22:23, Yaakov Selkowitz wrote: > Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode > libstdc++6 terminfo sed gzip libpcre1 grep libreadline7 bash > libncursesw10 [snip] Now that I think about it, regardless of libgcc1, that still doesn't make much sense. sed, grep, and bash depend on libintl8, which depends on libiconv2, and libreadline7 (which is required by bash) itself depends on libncursesw10, so that should be at least two places earlier. All of those dependencies are listed in setup.hint (and hence setup.ini), so is there something wrong with setup itself? Yaakov -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-11 4:33 ` Yaakov Selkowitz @ 2014-11-11 11:53 ` Corinna Vinschen 2014-11-11 14:14 ` Ken Brown 2014-11-13 14:18 ` Setup 2.774 texlive postinstall takes 10+ hours) Corinna Vinschen 0 siblings, 2 replies; 54+ messages in thread From: Corinna Vinschen @ 2014-11-11 11:53 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 1241 bytes --] On Nov 10 22:33, Yaakov Selkowitz wrote: > On 2014-11-10 22:23, Yaakov Selkowitz wrote: > >Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode > >libstdc++6 terminfo sed gzip libpcre1 grep libreadline7 bash > >libncursesw10 > [snip] > > Now that I think about it, regardless of libgcc1, that still doesn't make > much sense. sed, grep, and bash depend on libintl8, which depends on > libiconv2, and libreadline7 (which is required by bash) itself depends on > libncursesw10, so that should be at least two places earlier. All of those > dependencies are listed in setup.hint (and hence setup.ini), so is there > something wrong with setup itself? What about dependency loops? AFAICS, coreutils depends on tzcode, tzcode depends on coreutils. Both depend on libgcc1. This introduces a big problem in dependency resolution because there's no unambiguous starting point. What if we remove the coretuls dep from tzcode. Or, actually, what if we make sure that Base packages only depend on libs, but never on any other Base package? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-11 11:53 ` Corinna Vinschen @ 2014-11-11 14:14 ` Ken Brown 2014-11-11 15:02 ` Ken Brown 2014-11-13 14:18 ` Setup 2.774 texlive postinstall takes 10+ hours) Corinna Vinschen 1 sibling, 1 reply; 54+ messages in thread From: Ken Brown @ 2014-11-11 14:14 UTC (permalink / raw) To: cygwin On 11/11/2014 6:53 AM, Corinna Vinschen wrote: > On Nov 10 22:33, Yaakov Selkowitz wrote: >> On 2014-11-10 22:23, Yaakov Selkowitz wrote: >>> Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode >>> libstdc++6 terminfo sed gzip libpcre1 grep libreadline7 bash >>> libncursesw10 >> [snip] >> >> Now that I think about it, regardless of libgcc1, that still doesn't make >> much sense. sed, grep, and bash depend on libintl8, which depends on >> libiconv2, and libreadline7 (which is required by bash) itself depends on >> libncursesw10, so that should be at least two places earlier. All of those >> dependencies are listed in setup.hint (and hence setup.ini), so is there >> something wrong with setup itself? > > What about dependency loops? > > AFAICS, coreutils depends on tzcode, tzcode depends on coreutils. Both > depend on libgcc1. This introduces a big problem in dependency > resolution because there's no unambiguous starting point. > > What if we remove the coretuls dep from tzcode. > > Or, actually, what if we make sure that Base packages only depend > on libs, but never on any other Base package? Except that all Base packages (other than base-cygwin) should depend on base-cygwin. That will guarantee that base-cygwin precedes all other Base packages in the dependency order. And if we make _autorebase depend on nothing, then we're guaranteed that it precedes anything that depends on it. 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-11 14:14 ` Ken Brown @ 2014-11-11 15:02 ` Ken Brown 2014-11-11 16:02 ` Corinna Vinschen 0 siblings, 1 reply; 54+ messages in thread From: Ken Brown @ 2014-11-11 15:02 UTC (permalink / raw) To: cygwin On 11/11/2014 9:14 AM, Ken Brown wrote: > On 11/11/2014 6:53 AM, Corinna Vinschen wrote: >> On Nov 10 22:33, Yaakov Selkowitz wrote: >>> On 2014-11-10 22:23, Yaakov Selkowitz wrote: >>>> Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode >>>> libstdc++6 terminfo sed gzip libpcre1 grep libreadline7 bash >>>> libncursesw10 >>> [snip] >>> >>> Now that I think about it, regardless of libgcc1, that still doesn't >>> make >>> much sense. sed, grep, and bash depend on libintl8, which depends on >>> libiconv2, and libreadline7 (which is required by bash) itself >>> depends on >>> libncursesw10, so that should be at least two places earlier. All of >>> those >>> dependencies are listed in setup.hint (and hence setup.ini), so is there >>> something wrong with setup itself? >> >> What about dependency loops? >> >> AFAICS, coreutils depends on tzcode, tzcode depends on coreutils. Both >> depend on libgcc1. This introduces a big problem in dependency >> resolution because there's no unambiguous starting point. >> >> What if we remove the coretuls dep from tzcode. >> >> Or, actually, what if we make sure that Base packages only depend >> on libs, but never on any other Base package? > > Except that all Base packages (other than base-cygwin) should depend on > base-cygwin. That will guarantee that base-cygwin precedes all other > Base packages in the dependency order. And if we make _autorebase > depend on nothing, then we're guaranteed that it precedes anything that > depends on it. Of course, this still doesn't solve the problem of making sure that the _autorebase postinstall script runs whenever the user installs a package containing DLLs. I wonder if we should reconsider Achim's proposal. If I understand correctly, it is something like this (oversimplified): 1. Change autorebase.bat to do an incremental rebase instead of trying to do a full rebase. 2. Arrange for autorebase.bat to never be marked as "done". Achim, please correct me if my oversimplification distorts your suggestion too much. 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-11 15:02 ` Ken Brown @ 2014-11-11 16:02 ` Corinna Vinschen 2014-11-11 17:08 ` Achim Gratz 0 siblings, 1 reply; 54+ messages in thread From: Corinna Vinschen @ 2014-11-11 16:02 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 2787 bytes --] On Nov 11 10:02, Ken Brown wrote: > On 11/11/2014 9:14 AM, Ken Brown wrote: > >On 11/11/2014 6:53 AM, Corinna Vinschen wrote: > >>On Nov 10 22:33, Yaakov Selkowitz wrote: > >>>On 2014-11-10 22:23, Yaakov Selkowitz wrote: > >>>>Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode > >>>>libstdc++6 terminfo sed gzip libpcre1 grep libreadline7 bash > >>>>libncursesw10 > >>>[snip] > >>> > >>>Now that I think about it, regardless of libgcc1, that still doesn't > >>>make > >>>much sense. sed, grep, and bash depend on libintl8, which depends on > >>>libiconv2, and libreadline7 (which is required by bash) itself > >>>depends on > >>>libncursesw10, so that should be at least two places earlier. All of > >>>those > >>>dependencies are listed in setup.hint (and hence setup.ini), so is there > >>>something wrong with setup itself? > >> > >>What about dependency loops? > >> > >>AFAICS, coreutils depends on tzcode, tzcode depends on coreutils. Both > >>depend on libgcc1. This introduces a big problem in dependency > >>resolution because there's no unambiguous starting point. > >> > >>What if we remove the coretuls dep from tzcode. > >> > >>Or, actually, what if we make sure that Base packages only depend > >>on libs, but never on any other Base package? > > > >Except that all Base packages (other than base-cygwin) should depend on > >base-cygwin. That will guarantee that base-cygwin precedes all other > >Base packages in the dependency order. In theory that should be solved by the dependency to cygwin. Cygwin depends on base-cygwin, all other packages depend on cygwin. The problem is just that dependency loops can break that. > >And if we make _autorebase > >depend on nothing, then we're guaranteed that it precedes anything that > >depends on it. Per its setup.hint file it depends on nothing, just like base-cygwin, and both packages request that they don't get an automatic dependency to cygwin added. > Of course, this still doesn't solve the problem of making sure that the > _autorebase postinstall script runs whenever the user installs a package > containing DLLs. I wonder if we should reconsider Achim's proposal. If I > understand correctly, it is something like this (oversimplified): > > 1. Change autorebase.bat to do an incremental rebase instead of trying to do > a full rebase. > > 2. Arrange for autorebase.bat to never be marked as "done". > > Achim, please correct me if my oversimplification distorts your suggestion > too much. Achim, can you give a management summary how your proposal works? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-11 16:02 ` Corinna Vinschen @ 2014-11-11 17:08 ` Achim Gratz 2014-11-11 17:33 ` Corinna Vinschen 2014-11-11 23:36 ` Ken Brown 0 siblings, 2 replies; 54+ messages in thread From: Achim Gratz @ 2014-11-11 17:08 UTC (permalink / raw) To: cygwin Corinna Vinschen writes: > On Nov 11 10:02, Ken Brown wrote: >> Of course, this still doesn't solve the problem of making sure that the >> _autorebase postinstall script runs whenever the user installs a package >> containing DLLs. I wonder if we should reconsider Achim's proposal. If I >> understand correctly, it is something like this (oversimplified): >> >> 1. Change autorebase.bat to do an incremental rebase instead of trying to do >> a full rebase. >> >> 2. Arrange for autorebase.bat to never be marked as "done". >> >> Achim, please correct me if my oversimplification distorts your suggestion >> too much. > > Achim, can you give a management summary how your proposal works? As Ken already correctly summarized, the autorebase postinstall script will never be marked as done by setup.exe, so it will be run on each install or update. The incremental part ensures that this step doesn't take too much time if there's nothing to do. Currently this is based on the name of that script, but it could be done differently. The other part is that all "perpetual" postinstall scripts are run before any normal postinstall scripts, so these can assume to run in a correctly rebased environment. A slightly modified variant of the same mechanism could be used for those infodir, icon cache and fontconfig updates, which should probably be run after the normal postinstall scripts. I think I've sent Ken a sketch doing this from within a postinstall script for the texlive packages, but providing some support from setup.ini and setup.exe for stratified postinstalls (pre-post and post-post :-) would make this much more robust. I haven't yet coded up anything in that direction, though. If you're wondering what happens when you've just installed a fresh Cygwin: the perpetual rebase postinstall scripts detects the situation and bails out, while the normal postinstall script does the initial rebase (and is marked "done"). Which means we have to fix the dependency problem anyway. Incremental autorebase packages and patched setup.exe available on request. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-11 17:08 ` Achim Gratz @ 2014-11-11 17:33 ` Corinna Vinschen 2014-11-11 18:39 ` Achim Gratz 2014-11-11 23:36 ` Ken Brown 1 sibling, 1 reply; 54+ messages in thread From: Corinna Vinschen @ 2014-11-11 17:33 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 1642 bytes --] On Nov 11 18:08, Achim Gratz wrote: > Corinna Vinschen writes: > > On Nov 11 10:02, Ken Brown wrote: > >> Of course, this still doesn't solve the problem of making sure that the > >> _autorebase postinstall script runs whenever the user installs a package > >> containing DLLs. I wonder if we should reconsider Achim's proposal. If I > >> understand correctly, it is something like this (oversimplified): > >> > >> 1. Change autorebase.bat to do an incremental rebase instead of trying to do > >> a full rebase. > >> > >> 2. Arrange for autorebase.bat to never be marked as "done". > >> > >> Achim, please correct me if my oversimplification distorts your suggestion > >> too much. > > > > Achim, can you give a management summary how your proposal works? > > As Ken already correctly summarized, the autorebase postinstall script > will never be marked as done by setup.exe, so it will be run on each > install or update. The incremental part ensures that this step doesn't > take too much time if there's nothing to do. Currently this is based on > the name of that script, but it could be done differently. The other > part is that all "perpetual" postinstall scripts are run before any > normal postinstall scripts, so these can assume to run in a correctly > rebased environment. I understand that you're patching setup to recognize the autorebase package by name, but how does it recognize other "perpetual" postinstall scripts ATM? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-11 17:33 ` Corinna Vinschen @ 2014-11-11 18:39 ` Achim Gratz 0 siblings, 0 replies; 54+ messages in thread From: Achim Gratz @ 2014-11-11 18:39 UTC (permalink / raw) To: cygwin Corinna Vinschen writes: > I understand that you're patching setup to recognize the autorebase > package by name, but how does it recognize other "perpetual" postinstall > scripts ATM? I actually match an "_always" suffix before the file extension. So once such a file gets installed in /etc/postinstall, it effectively becomes a perpetual postinstall script. Not the most elegant way of doing it, but since I needed to carry that patch for setup.exe locally I didn't want to make it much more complicated, especially nothing that would require extra features in setup.ini. We can think about something else if this is meant to become official. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-11 17:08 ` Achim Gratz 2014-11-11 17:33 ` Corinna Vinschen @ 2014-11-11 23:36 ` Ken Brown 2014-11-12 9:15 ` Corinna Vinschen 1 sibling, 1 reply; 54+ messages in thread From: Ken Brown @ 2014-11-11 23:36 UTC (permalink / raw) To: cygwin On 11/11/2014 12:08 PM, Achim Gratz wrote: > Corinna Vinschen writes: >> On Nov 11 10:02, Ken Brown wrote: >>> Of course, this still doesn't solve the problem of making sure that the >>> _autorebase postinstall script runs whenever the user installs a package >>> containing DLLs. I wonder if we should reconsider Achim's proposal. If I >>> understand correctly, it is something like this (oversimplified): >>> >>> 1. Change autorebase.bat to do an incremental rebase instead of trying to do >>> a full rebase. >>> >>> 2. Arrange for autorebase.bat to never be marked as "done". >>> >>> Achim, please correct me if my oversimplification distorts your suggestion >>> too much. >> >> Achim, can you give a management summary how your proposal works? > > As Ken already correctly summarized, the autorebase postinstall script > will never be marked as done by setup.exe, so it will be run on each > install or update. The incremental part ensures that this step doesn't > take too much time if there's nothing to do. Currently this is based on > the name of that script, but it could be done differently. The other > part is that all "perpetual" postinstall scripts are run before any > normal postinstall scripts, so these can assume to run in a correctly > rebased environment. This seems like a very simple solution to the problem. I like it a lot. > A slightly modified variant of the same mechanism could be used for > those infodir, icon cache and fontconfig updates, which should probably > be run after the normal postinstall scripts. I think I've sent Ken a > sketch doing this from within a postinstall script for the texlive > packages, but providing some support from setup.ini and setup.exe for > stratified postinstalls (pre-post and post-post :-) would make this much > more robust. I haven't yet coded up anything in that direction, though. > > If you're wondering what happens when you've just installed a fresh > Cygwin: the perpetual rebase postinstall scripts detects the situation > and bails out, while the normal postinstall script does the initial > rebase (and is marked "done"). Which means we have to fix the > dependency problem anyway. > > Incremental autorebase packages and patched setup.exe available on > request. I'd like to see them. Thanks. 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-11 23:36 ` Ken Brown @ 2014-11-12 9:15 ` Corinna Vinschen 2014-11-12 17:53 ` Achim Gratz 0 siblings, 1 reply; 54+ messages in thread From: Corinna Vinschen @ 2014-11-12 9:15 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 1984 bytes --] On Nov 11 18:37, Ken Brown wrote: > On 11/11/2014 12:08 PM, Achim Gratz wrote: > >As Ken already correctly summarized, the autorebase postinstall script > >will never be marked as done by setup.exe, so it will be run on each > >install or update. The incremental part ensures that this step doesn't > >take too much time if there's nothing to do. Currently this is based on > >the name of that script, but it could be done differently. The other > >part is that all "perpetual" postinstall scripts are run before any > >normal postinstall scripts, so these can assume to run in a correctly > >rebased environment. > >[...] > >A slightly modified variant of the same mechanism could be used for > >those infodir, icon cache and fontconfig updates, which should probably > >be run after the normal postinstall scripts. I think I've sent Ken a > >sketch doing this from within a postinstall script for the texlive > >packages, but providing some support from setup.ini and setup.exe for > >stratified postinstalls (pre-post and post-post :-) would make this much > >more robust. I haven't yet coded up anything in that direction, though. > > > >If you're wondering what happens when you've just installed a fresh > >Cygwin: the perpetual rebase postinstall scripts detects the situation > >and bails out, while the normal postinstall script does the initial > >rebase (and is marked "done"). Which means we have to fix the > >dependency problem anyway. > > > >Incremental autorebase packages and patched setup.exe available on > >request. > > I'd like to see them. Thanks. Yes, me too. Achim, does your perpetual autorebase rely on the existing autorebase script? If so, do you see a good chance to consolidate the changes into a single package we're still calling _autorebase? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-12 9:15 ` Corinna Vinschen @ 2014-11-12 17:53 ` Achim Gratz 2014-11-13 8:55 ` Corinna Vinschen 0 siblings, 1 reply; 54+ messages in thread From: Achim Gratz @ 2014-11-12 17:53 UTC (permalink / raw) To: cygwin Corinna Vinschen writes: >> >Incremental autorebase packages and patched setup.exe available on >> >request. >> >> I'd like to see them. Thanks. I'll upload them on the weekend latest, I'm a bit swamped at work. I'll follow up on this in cygwin-applications. > Yes, me too. > > Achim, does your perpetual autorebase rely on the existing autorebase > script? If so, do you see a good chance to consolidate the changes > into a single package we're still calling _autorebase? No, I've replaced it with an incremental autorebase which can function as a normal autorebase as well. I've discussed bits of it on the list ~2 years ago, but at that time there was no further interest in having something run on every installation. Ah, here it is: http://thread.gmane.org/gmane.os.cygwin.applications/23733 http://thread.gmane.org/gmane.os.cygwin.applications/23772 Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-12 17:53 ` Achim Gratz @ 2014-11-13 8:55 ` Corinna Vinschen 2014-11-13 19:41 ` Achim Gratz 0 siblings, 1 reply; 54+ messages in thread From: Corinna Vinschen @ 2014-11-13 8:55 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 1488 bytes --] On Nov 12 18:53, Achim Gratz wrote: > Corinna Vinschen writes: > >> >Incremental autorebase packages and patched setup.exe available on > >> >request. > >> > >> I'd like to see them. Thanks. > > I'll upload them on the weekend latest, I'm a bit swamped at work. I'll > follow up on this in cygwin-applications. > > > Yes, me too. > > > > Achim, does your perpetual autorebase rely on the existing autorebase > > script? If so, do you see a good chance to consolidate the changes > > into a single package we're still calling _autorebase? > > No, No? > I've replaced it with an incremental autorebase which can function > as a normal autorebase as well. I've discussed bits of it on the list > ~2 years ago, but at that time there was no further interest in having > something run on every installation. > > Ah, here it is: > http://thread.gmane.org/gmane.os.cygwin.applications/23733 > http://thread.gmane.org/gmane.os.cygwin.applications/23772 From what I read here your _incautorebase would replace _autorebase just fine. I'm not concerned about an exact replacement for the rebaseall script. The idea would be to make _incautorebase into drop-in replacement for _autorebase and throw away my _autorebase stuff. Rebaseall would stay, it's part of the rebase package anyway. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours 2014-11-13 8:55 ` Corinna Vinschen @ 2014-11-13 19:41 ` Achim Gratz 0 siblings, 0 replies; 54+ messages in thread From: Achim Gratz @ 2014-11-13 19:41 UTC (permalink / raw) To: cygwin Corinna Vinschen writes: > No? … in the sense of something almost, but not quite entirely unlike _autorebase. > From what I read here your _incautorebase would replace _autorebase > just fine. I'm not concerned about an exact replacement for the > rebaseall script. The idea would be to make _incautorebase into > drop-in replacement for _autorebase and throw away my _autorebase > stuff. Rebaseall would stay, it's part of the rebase package anyway. Correct. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours) 2014-11-11 11:53 ` Corinna Vinschen 2014-11-11 14:14 ` Ken Brown @ 2014-11-13 14:18 ` Corinna Vinschen 2014-11-13 15:45 ` Ken Brown 1 sibling, 1 reply; 54+ messages in thread From: Corinna Vinschen @ 2014-11-13 14:18 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 3591 bytes --] On Nov 11 12:53, Corinna Vinschen wrote: > On Nov 10 22:33, Yaakov Selkowitz wrote: > > On 2014-11-10 22:23, Yaakov Selkowitz wrote: > > >Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode > > >libstdc++6 terminfo sed gzip libpcre1 grep libreadline7 bash > > >libncursesw10 > > [snip] > > > > Now that I think about it, regardless of libgcc1, that still doesn't make > > much sense. sed, grep, and bash depend on libintl8, which depends on > > libiconv2, and libreadline7 (which is required by bash) itself depends on > > libncursesw10, so that should be at least two places earlier. All of those > > dependencies are listed in setup.hint (and hence setup.ini), so is there > > something wrong with setup itself? > > What about dependency loops? > > AFAICS, coreutils depends on tzcode, tzcode depends on coreutils. Both > depend on libgcc1. This introduces a big problem in dependency > resolution because there's no unambiguous starting point. > > What if we remove the coretuls dep from tzcode. > > Or, actually, what if we make sure that Base packages only depend > on libs, but never on any other Base package? Ok, now after a collegue of mine informed me about the existence of tsort (*blush*), I could finally produce some more info about loops in our dependencies. I wrote a simple script: awk '/^@ /{ left=$2; } /^requires: /{ for (i=2; i<=NF; ++i) print left " " $i; } ' < setup.ini | tsort It found the following dependency loops which have to be fixed. Most notably are the dep loops of _autorebase and _update-info-dir, which we'll fix ASAP. GConf2 -> libgconf2_4 -> gconf-desktop-schemas -> GConf2 xf86-video-dummy -> xorg-server -> xf86-video-dummy xf86-video-nested -> xorg-server -> xf86-video-nested texlive -> texlive-collection-basic -> texlive libautotrace3 -> libMagickCore5 -> libautotrace3 libgeoclue0 -> geoclue -> libgeoclue0 shared-mime-info -> libglib2.0_0 -> shared-mime-info libatspi0 -> at-spi2-core -> libatspi0 libfam0 -> gamin -> libglib2.0_0 -> libfam0 gsettings-desktop-schemas -> libglib2.0_0 -> gsettings-desktop-schemas libdbus1_3 -> dbus -> libdbus1_3 php-Archive_Tar -> php-PEAR -> php-Archive_Tar autogen -> libopts-devel -> autogen python-libxslt -> python-libxml2 -> python-libxslt libopenldap2_4_2 -> libsasl2_3 -> libopenldap2_4_2 perl-Mozilla-CA -> perl-IO-Socket-SSL -> perl-Mozilla-CA rubygems -> ruby-io-console -> ruby -> rubygems ruby-rake -> rubygems -> ruby-rake ruby-rdoc -> rubygems -> ruby-rdoc ruby-rdoc -> rubygems -> ruby-io-console -> ruby -> ruby-rdoc mingw64-i686-runtime -> mingw64-i686-gcc-core -> mingw64-i686-runtime mingw64-x86_64-runtime -> mingw64-x86_64-gcc-core -> mingw64-x86_64-runtime _autorebase -> rebase -> sed -> libintl8 -> libiconv2 -> libgcc1 -> _autorebase _autorebase -> rebase -> coreutils -> libgmp10 -> _autorebase tesseract-ocr-eng -> tesseract-ocr -> tesseract-ocr-eng openmpi -> libopenmpi -> openmpi _autorebase -> rebase -> grep -> libpcre1 -> _autorebase _autorebase -> rebase -> grep -> bash -> libreadline7 -> libncursesw10 -> libstdc++6 -> _autorebase _update-info-dir -> bash -> _update-info-dir _update-info-dir -> bash -> coreutils -> _update-info-dir _update-info-dir -> info -> _update-info-dir Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours) 2014-11-13 14:18 ` Setup 2.774 texlive postinstall takes 10+ hours) Corinna Vinschen @ 2014-11-13 15:45 ` Ken Brown 2014-11-13 16:18 ` Corinna Vinschen 2014-11-13 19:47 ` Achim Gratz 0 siblings, 2 replies; 54+ messages in thread From: Ken Brown @ 2014-11-13 15:45 UTC (permalink / raw) To: cygwin On 11/13/2014 9:18 AM, Corinna Vinschen wrote: > On Nov 11 12:53, Corinna Vinschen wrote: >> On Nov 10 22:33, Yaakov Selkowitz wrote: >>> On 2014-11-10 22:23, Yaakov Selkowitz wrote: >>>> Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode >>>> libstdc++6 terminfo sed gzip libpcre1 grep libreadline7 bash >>>> libncursesw10 >>> [snip] >>> >>> Now that I think about it, regardless of libgcc1, that still doesn't make >>> much sense. sed, grep, and bash depend on libintl8, which depends on >>> libiconv2, and libreadline7 (which is required by bash) itself depends on >>> libncursesw10, so that should be at least two places earlier. All of those >>> dependencies are listed in setup.hint (and hence setup.ini), so is there >>> something wrong with setup itself? >> >> What about dependency loops? >> >> AFAICS, coreutils depends on tzcode, tzcode depends on coreutils. Both >> depend on libgcc1. This introduces a big problem in dependency >> resolution because there's no unambiguous starting point. >> >> What if we remove the coretuls dep from tzcode. >> >> Or, actually, what if we make sure that Base packages only depend >> on libs, but never on any other Base package? > > Ok, now after a collegue of mine informed me about the existence of > tsort (*blush*), I could finally produce some more info about loops > in our dependencies. I wrote a simple script: > > awk '/^@ /{ left=$2; } > /^requires: /{ for (i=2; i<=NF; ++i) print left " " $i; } > ' < setup.ini | tsort > > It found the following dependency loops which have to be fixed. > Most notably are the dep loops of _autorebase and _update-info-dir, > which we'll fix ASAP. > > GConf2 -> libgconf2_4 -> gconf-desktop-schemas -> GConf2 > > xf86-video-dummy -> xorg-server -> xf86-video-dummy > > xf86-video-nested -> xorg-server -> xf86-video-nested > > texlive -> texlive-collection-basic -> texlive > > libautotrace3 -> libMagickCore5 -> libautotrace3 > > libgeoclue0 -> geoclue -> libgeoclue0 > > shared-mime-info -> libglib2.0_0 -> shared-mime-info > > libatspi0 -> at-spi2-core -> libatspi0 > > libfam0 -> gamin -> libglib2.0_0 -> libfam0 > > gsettings-desktop-schemas -> libglib2.0_0 -> gsettings-desktop-schemas > > libdbus1_3 -> dbus -> libdbus1_3 > > php-Archive_Tar -> php-PEAR -> php-Archive_Tar > > autogen -> libopts-devel -> autogen > > python-libxslt -> python-libxml2 -> python-libxslt > > libopenldap2_4_2 -> libsasl2_3 -> libopenldap2_4_2 > > perl-Mozilla-CA -> perl-IO-Socket-SSL -> perl-Mozilla-CA > > rubygems -> ruby-io-console -> ruby -> rubygems > > ruby-rake -> rubygems -> ruby-rake > > ruby-rdoc -> rubygems -> ruby-rdoc > > ruby-rdoc -> rubygems -> ruby-io-console -> ruby -> ruby-rdoc > > mingw64-i686-runtime -> mingw64-i686-gcc-core -> mingw64-i686-runtime > > mingw64-x86_64-runtime -> mingw64-x86_64-gcc-core -> mingw64-x86_64-runtime > > _autorebase -> rebase -> sed -> libintl8 -> libiconv2 -> libgcc1 -> _autorebase > > _autorebase -> rebase -> coreutils -> libgmp10 -> _autorebase > > tesseract-ocr-eng -> tesseract-ocr -> tesseract-ocr-eng > > openmpi -> libopenmpi -> openmpi > > _autorebase -> rebase -> grep -> libpcre1 -> _autorebase > > _autorebase -> rebase -> grep -> bash -> libreadline7 -> libncursesw10 -> libstdc++6 -> _autorebase > > _update-info-dir -> bash -> _update-info-dir > > _update-info-dir -> bash -> coreutils -> _update-info-dir > > _update-info-dir -> info -> _update-info-dir Many of the dependency loops are harmless. If two packages A and B are involved in a loop, and if they both provide postinstall scripts, then you can't be sure which script will run first. So we only have to worry about those loops in which the order is important. The real problem here is that the "requires" line in setup.ini is being used for two unrelated purposes. The first one is to make sure that if package A requires package B in order to run properly, and if A is chosen for install, then so is B. For this purpose, loops are not only harmless, they're sometimes necessary. For example, the dependency loop between texlive and texlive-collection-basic is completely appropriate. How else can we make sure that if one is chosen, then so is the other? The second purpose is to determine the order of running postinstall scripts, and this is where loops are bad. We need to rethink how postinstall order is determined. What about just adding a provision for specifying postinstall dependencies, independent of the current "requires" line? We've already discussed a couple of situations where this would be useful: * base-cygwin needs to run first; * autorebase should be run as early as possible. A third one concerns texlive. I could greatly speed up the texlive postinstall scripts if I had a package (maybe called "_texlive_post") that provided a script to be run after all other texlive scripts. There's one final idea I'd like to throw out, possibly as an alternative to Achim's perpetual postinstall scripts: It would be useful to be able to specify that a certain package (such as _autorebase, or my proposed _texlive_post) should always be selected for *reinstall* whenever a package that depends on it is installed. Ken P.S. If there is support for any of my suggestions, I'll do all I can to help with the implementation. -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours) 2014-11-13 15:45 ` Ken Brown @ 2014-11-13 16:18 ` Corinna Vinschen 2014-11-13 19:47 ` Achim Gratz 1 sibling, 0 replies; 54+ messages in thread From: Corinna Vinschen @ 2014-11-13 16:18 UTC (permalink / raw) To: cygwin [-- Attachment #1: Type: text/plain, Size: 5666 bytes --] On Nov 13 10:46, Ken Brown wrote: > On 11/13/2014 9:18 AM, Corinna Vinschen wrote: > >Ok, now after a collegue of mine informed me about the existence of > >tsort (*blush*), I could finally produce some more info about loops > >in our dependencies. I wrote a simple script: > > > >awk '/^@ /{ left=$2; } > > /^requires: /{ for (i=2; i<=NF; ++i) print left " " $i; } > > ' < setup.ini | tsort > > > >It found the following dependency loops which have to be fixed. > >Most notably are the dep loops of _autorebase and _update-info-dir, > >which we'll fix ASAP. > > > > GConf2 -> libgconf2_4 -> gconf-desktop-schemas -> GConf2 > > > > xf86-video-dummy -> xorg-server -> xf86-video-dummy > > > > xf86-video-nested -> xorg-server -> xf86-video-nested > > > > texlive -> texlive-collection-basic -> texlive > > > > libautotrace3 -> libMagickCore5 -> libautotrace3 > > > > libgeoclue0 -> geoclue -> libgeoclue0 > > > > shared-mime-info -> libglib2.0_0 -> shared-mime-info > > > > libatspi0 -> at-spi2-core -> libatspi0 > > > > libfam0 -> gamin -> libglib2.0_0 -> libfam0 > > > > gsettings-desktop-schemas -> libglib2.0_0 -> gsettings-desktop-schemas > > > > libdbus1_3 -> dbus -> libdbus1_3 > > > > php-Archive_Tar -> php-PEAR -> php-Archive_Tar > > > > autogen -> libopts-devel -> autogen > > > > python-libxslt -> python-libxml2 -> python-libxslt > > > > libopenldap2_4_2 -> libsasl2_3 -> libopenldap2_4_2 > > > > perl-Mozilla-CA -> perl-IO-Socket-SSL -> perl-Mozilla-CA > > > > rubygems -> ruby-io-console -> ruby -> rubygems > > > > ruby-rake -> rubygems -> ruby-rake > > > > ruby-rdoc -> rubygems -> ruby-rdoc > > > > ruby-rdoc -> rubygems -> ruby-io-console -> ruby -> ruby-rdoc > > > > mingw64-i686-runtime -> mingw64-i686-gcc-core -> mingw64-i686-runtime > > > > mingw64-x86_64-runtime -> mingw64-x86_64-gcc-core -> mingw64-x86_64-runtime > > > > tesseract-ocr-eng -> tesseract-ocr -> tesseract-ocr-eng > > > > openmpi -> libopenmpi -> openmpi > > Update: All loops concerning _autorebase and _update-info-dir are gone now. This should help a lot. > Many of the dependency loops are harmless. If two packages A and B are > involved in a loop, and if they both provide postinstall scripts, then you > can't be sure which script will run first. So we only have to worry about > those loops in which the order is important. Right, but the maintainer should certainly have a look. > The real problem here is that the "requires" line in setup.ini is being used > for two unrelated purposes. The first one is to make sure that if package A > requires package B in order to run properly, and if A is chosen for install, > then so is B. For this purpose, loops are not only harmless, they're > sometimes necessary. For example, the dependency loop between texlive and > texlive-collection-basic is completely appropriate. How else can we make > sure that if one is chosen, then so is the other? In theory one could argue that the package split is not in the best interest of things... > The second purpose is to determine the order of running postinstall scripts, > and this is where loops are bad. We need to rethink how postinstall order > is determined. What about just adding a provision for specifying > postinstall dependencies, independent of the current "requires" line? This needs support by the upset perl script as well as Setup. It would sure be nice, but *basically* the requires also defines an order of postinstall scripts. If no dangerous loops occur. For the time being we should probably run my tiny awk|tsort script once a week or so :} > We've > already discussed a couple of situations where this would be useful: > > * base-cygwin needs to run first; > * autorebase should be run as early as possible. Right. This *should* be taken care of by the dependency order. There was a really bad bug in setup.ini. Originally the _autobase package depended on rebase, bash and cygwin. Despite removing the requires: line from _autobase'es setup.hint file, setup.ini still kept this line in all the time :-P I added an empty "requires:" line to _autobase/setup.hint, and the new setup.ini does not contain these old requirements anymore. What we really need short-term is some perl guru fixing upset. Is anybody feeling up to the task? > A third one concerns texlive. I could greatly speed up the texlive > postinstall scripts if I had a package (maybe called "_texlive_post") that > provided a script to be run after all other texlive scripts. > > There's one final idea I'd like to throw out, possibly as an alternative to > Achim's perpetual postinstall scripts: It would be useful to be able to > specify that a certain package (such as _autorebase, or my proposed > _texlive_post) should always be selected for *reinstall* whenever a package > that depends on it is installed. > > Ken > > P.S. If there is support for any of my suggestions, I'll do all I can to > help with the implementation. Yes, please! I don't know how often I repeated this in the past. If you feel like improving Cygwin one way or the other by providing code or documentation, to Cygwin itself or its infrastructure, please feel free. Yes, sometimes you'll struggle against my unwillingness or, more often than not, laziness, but I'm really open to improvements if they come with patches. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat [-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours) 2014-11-13 15:45 ` Ken Brown 2014-11-13 16:18 ` Corinna Vinschen @ 2014-11-13 19:47 ` Achim Gratz 1 sibling, 0 replies; 54+ messages in thread From: Achim Gratz @ 2014-11-13 19:47 UTC (permalink / raw) To: cygwin Ken Brown writes: > There's one final idea I'd like to throw out, possibly as an > alternative to Achim's perpetual postinstall scripts: It would be > useful to be able to specify that a certain package (such as > _autorebase, or my proposed _texlive_post) should always be selected > for *reinstall* whenever a package that depends on it is installed. That's roughly equivalent to what Debian calls postinstall triggers. Yes, these would be useful, but it requires some infrastructure in upset/genini and setup.exe that's simply not there yet. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2012-08-23 11:35 Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) Martin.Fitzpatrick ` (4 preceding siblings ...) 2014-07-20 14:01 ` leftwing @ 2014-10-21 3:23 ` Don MacDougall 2014-10-21 3:40 ` Don MacDougall 5 siblings, 1 reply; 54+ messages in thread From: Don MacDougall @ 2014-10-21 3:23 UTC (permalink / raw) To: cygwin If I changed it away from "default" was accidental. I did look through the list of packages to be installed and it looked like quite a list and all binary packages were checked but not the source packages. But, since the first time I have looked when I restarted the installation and it said "default" and I didn't change it. If it was accidentally changed the first time, would it then say "all" when I restart the installation? If so, then I know it says "default" when I restarted it. Don -- View this message in context: http://cygwin.1069669.n5.nabble.com/Setup-2-774-texlive-postinstall-takes-10-hours-resending-due-to-cygwin-bounce-tp92260p112045.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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] 54+ messages in thread
* Re: Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) 2014-10-21 3:23 ` Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) Don MacDougall @ 2014-10-21 3:40 ` Don MacDougall 0 siblings, 0 replies; 54+ messages in thread From: Don MacDougall @ 2014-10-21 3:40 UTC (permalink / raw) To: cygwin Oops, what I meant to say was that it says "default" not "install" when I restart the installation. If I had it set to "install" the first time rather than "default", presumably it would still say that on restarting, I would imagine, though this is my first time in at least 10 years to try to install cygwin since I usually use linux, not Windows. Don -- View this message in context: http://cygwin.1069669.n5.nabble.com/Setup-2-774-texlive-postinstall-takes-10-hours-resending-due-to-cygwin-bounce-tp92260p112046.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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] 54+ messages in thread
end of thread, other threads:[~2014-11-13 19:47 UTC | newest] Thread overview: 54+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2012-08-23 11:35 Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) Martin.Fitzpatrick 2012-08-23 13:29 ` Earnie Boyd 2012-08-23 14:35 ` Adam Dinwoodie 2012-08-23 15:27 ` Ken Brown 2012-08-25 6:47 ` Ken Brown 2012-08-25 7:26 ` Achim Gratz 2013-01-28 16:42 ` toddcs 2013-01-29 3:41 ` Ken Brown 2013-02-05 15:48 ` jeremycraven 2013-02-05 16:37 ` marco atzeri 2013-02-05 16:43 ` Ken Brown 2013-02-06 9:52 ` jeremycraven 2013-02-06 14:11 ` Ken Brown 2014-07-20 14:01 ` leftwing 2014-07-20 17:44 ` Ken Brown 2014-10-20 22:39 ` Setup 2.774 texlive postinstall takes 10+ hours Don MacDougall 2014-10-21 2:09 ` Ken Brown 2014-10-21 2:26 ` Ken Brown 2014-10-21 4:06 ` Don MacDougall 2014-10-21 12:58 ` Ken Brown 2014-10-24 7:11 ` Don MacDougall 2014-10-24 11:35 ` Andrey Repin 2014-10-29 5:06 ` Don MacDougall 2014-10-29 12:20 ` Andrey Repin 2014-10-30 22:27 ` Don MacDougall 2014-11-02 18:02 ` Ken Brown 2014-11-03 10:25 ` Corinna Vinschen 2014-11-03 12:44 ` Ken Brown 2014-11-03 14:52 ` Corinna Vinschen 2014-11-03 16:17 ` Corinna Vinschen 2014-11-03 18:03 ` Achim Gratz 2014-11-03 22:04 ` Ken Brown 2014-11-04 16:21 ` Achim Gratz 2014-11-04 9:00 ` Corinna Vinschen 2014-11-11 4:23 ` Yaakov Selkowitz 2014-11-11 4:33 ` Yaakov Selkowitz 2014-11-11 11:53 ` Corinna Vinschen 2014-11-11 14:14 ` Ken Brown 2014-11-11 15:02 ` Ken Brown 2014-11-11 16:02 ` Corinna Vinschen 2014-11-11 17:08 ` Achim Gratz 2014-11-11 17:33 ` Corinna Vinschen 2014-11-11 18:39 ` Achim Gratz 2014-11-11 23:36 ` Ken Brown 2014-11-12 9:15 ` Corinna Vinschen 2014-11-12 17:53 ` Achim Gratz 2014-11-13 8:55 ` Corinna Vinschen 2014-11-13 19:41 ` Achim Gratz 2014-11-13 14:18 ` Setup 2.774 texlive postinstall takes 10+ hours) Corinna Vinschen 2014-11-13 15:45 ` Ken Brown 2014-11-13 16:18 ` Corinna Vinschen 2014-11-13 19:47 ` Achim Gratz 2014-10-21 3:23 ` Setup 2.774 texlive postinstall takes 10+ hours (resending due to cygwin bounce) Don MacDougall 2014-10-21 3:40 ` Don MacDougall
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).