public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Mark Himsley" <mark@mdsh.com>, "Cygwin" <cygwin@sources.redhat.com>
Subject: RE: New version of setup - prerelease available
Date: Fri, 03 May 2002 04:19:00 -0000	[thread overview]
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C5FA7@itdomain003.itdomain.net.au> (raw)

Sounds like there is a memory leak or somesuch. With the MD5 sums in
ini's I'll be able to do some proper testing myself now.

How many packages where you installing?
Which ones?

Rob

> -----Original Message-----
> From: Mark Himsley [mailto:mark@mdsh.com] 
> Sent: Friday, May 03, 2002 9:17 PM
> To: Cygwin
> Subject: Re: New version of setup - prerelease available
> 
> 
> On Wed, 1 May 2002 21:33:22 +1000 you wrote:
> 
> >I've uploaded a new version of setup.exe, and source, to
> >http://www.cygwin.com/setup-snapshots/setup-md5-20020501.exe
> 
> I've just tried to use this...
> 
> As usual, I did a 'Download from Internet' followed by an 
> 'Install from Local Drive'.
> 
> The download worked like a dream.
> The install didn't.
> 
> For the install it got as far as the page which says:
> -----------------------------------------------------------------
> Process
> This page displays the progress of the download or installation.
> 
> Installing...
> (PKG)
> (FILE)
> Package [ bar graph... ]
> -----------------------------------------------------------------
> 
> The package chooser window is not opened. Nothing is 
> displayed after the
> (PKG) or (FILE) and the bar graph does not move. The process 
> eats memory until it gets up to ~168MB and then ends.  
> Nothing is installed. setup.log and setup.log.full are not 
> modified (the last things logged were the downloads of the 
> files from the previous run).
> 
> Version 2.194.2.25 happily installed the packages which your 
> beta had downloaded.
> 
> -- 
> Mark Himsley
> In Acton
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2002-05-03 11:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03  4:19 Robert Collins [this message]
2002-05-03  5:07 ` Mark Himsley
  -- strict thread matches above, loose matches on Subject: below --
2002-05-03 19:01 Robert Collins
     [not found] <FC169E059D1A0442A04C40F86D9BA7600C5F8A@itdomain003.itdomain.net .au>
2002-05-02  4:41 ` Robert Collins
2002-05-02 14:08   ` Alan Dobkin
2002-05-01  5:58 Robert Collins
2002-05-01  6:08 ` Cliff Hones
2002-05-01  6:12 ` Cliff Hones
2002-05-01  6:26 ` Cliff Hones
2002-05-01  5:15 Robert Collins
2002-05-01  5:54 ` Cliff Hones
     [not found] <FC169E059D1A0442A04C40F86D9BA7600C5F6B@itdomain003.itdomain.net .au>
2002-05-01  4:33 ` Robert Collins
2002-05-01  5:09   ` Cliff Hones
2002-05-01 10:54   ` Alan Dobkin
2002-05-03  4:16   ` Mark Himsley

Reply instructions:

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

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

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

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

  git send-email \
    --in-reply-to=FC169E059D1A0442A04C40F86D9BA7600C5FA7@itdomain003.itdomain.net.au \
    --to=robert.collins@itdomain.com.au \
    --cc=cygwin@sources.redhat.com \
    --cc=mark@mdsh.com \
    /path/to/YOUR_REPLY

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

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).