From: "Harig, Mark A." <maharig@idirect.net>
To: "Robert Collins" <robert.collins@syncretize.net>, <cygwin@cygwin.com>
Subject: RE: New setup pre-release - feedback needed
Date: Wed, 17 Jul 2002 11:25:00 -0000 [thread overview]
Message-ID: <BADF3C947A1BD54FBA75C70C241B0B9E10AA5E@ex02.idirect.net> (raw)
Bug report:
This problem occurs whether I install from internet or locally and
only occurs with the new pre-release (i.e., does *not* occur with
version 2.249.2.5). Steps to reproduce:
1. Using the latest release of setup.exe: on the Select Packages
dialogue window, in the 'Devel' category, 'Keep' is selected for
autoconf-stable (version 2.13-4) and automake-stable (version 1.4p5-5).
'Skip' is selected for 'autoconf', 'autoconf-devel', 'automake',
'automake-devel', and 'binutils'.
2. I run 'setup.exe' through to successful completion.
3. Using'setup-2.259.2.4.exe': on the Select Packages dialogue window,
setup has erroneously turned on 'autoconf' (2.53a-1), 'autoconf-devel'
(2.52-4), and 'binutils' (20020706-1). As far as I know, this is an
error. setup should not be selecting packages that I have skipped. Or,
is there some relationship among these packages that I'm not
understanding?
> -----Original Message-----
> From: Robert Collins [mailto:robert.collins@syncretize.net]
> Sent: Saturday, July 13, 2002 10:11 AM
> To: cygwin@cygwin.com
> Subject: New setup pre-release - feedback needed
>
>
> We're coming up on a new release of setup.exe, with a number of user
> interface enhancements to make it more obvious what setup is
> doing when it
> 'pauses'.
>
> It *should* be bug free, although there may be a minor bug with
> autodetection of upgrades (we have one report, but no debugging info).
>
> The pre-release snapshot can be found at
> http://www.cygwin.com/setup-snapshots/setup-2.259.2.4.exe.
>
> As usual, the quality of this release will depend on feedback
> from you, the
> users. Please give the new version a go, and if you have
> *any* trouble, send
> me the setup.log and setup.log.full from your run of setup.exe.
>
> Cheers,
> Rob
>
>
> --
> 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/
next reply other threads:[~2002-07-17 16:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 11:25 Harig, Mark A. [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-17 10:12 Harig, Mark A.
2002-07-17 9:26 Harig, Mark A.
2002-07-17 9:56 ` Robert Collins
2002-07-17 6:56 John Vincent
2002-07-16 13:18 Harig, Mark A.
2002-07-16 14:36 ` Max Bowsher
2002-07-17 3:26 ` Robert Collins
2002-07-17 11:43 ` Max Bowsher
2002-07-16 18:18 ` Robert Collins
2002-07-16 8:22 Demmer, Thomas
2002-07-16 8:41 ` Robert Collins
2002-07-13 12:21 Robert Collins
2002-07-15 22:13 ` Joerg R. Schaible
2002-07-17 3:11 ` Peter A. Castro
2002-07-17 3:24 ` Robert Collins
2002-07-18 2:42 ` Peter A. Castro
2002-07-17 11:59 ` Max Bowsher
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=BADF3C947A1BD54FBA75C70C241B0B9E10AA5E@ex02.idirect.net \
--to=maharig@idirect.net \
--cc=cygwin@cygwin.com \
--cc=robert.collins@syncretize.net \
/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).