public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* RE: setup.exe 2.218.2.8/9 broken
@ 2002-05-17 12:23 Harig, Mark A.
  2002-05-17 13:00 ` Jon LaBadie
  2002-05-17 14:52 ` Christopher Faylor
  0 siblings, 2 replies; 18+ messages in thread
From: Harig, Mark A. @ 2002-05-17 12:23 UTC (permalink / raw)
  To: cygwin



> -----Original Message-----
> From: Charles Wilson [mailto:cwilson@ece.gatech.edu]
> Sent: Friday, May 17, 2002 1:00 PM
> To: Harig, Mark A.
> Cc: cygwin@cygwin.com
> Subject: Re: setup.exe 2.218.2.8/9 broken
> 
> 
> Harig, Mark A. wrote:
> >>-----Original Message-----
> >>From: Charles Wilson [mailto:cwilson@ece.gatech.edu]
> >>Sent: Thursday, May 16, 2002 11:52 PM
> >>To: John Haggerty
> >>Cc: cygwin@cygwin.com
> >>Subject: Re: setup.exe 2.218.2.8/9 broken
> >>
> > 
> > (text deleted)
> > 
> >>(3) bug #2: minor issues with parsing "buried" setup.ini 
> >>files -- that 
> >>belong to things NOT cygwin-setup.exe-related.  This happens 
> >>only when 
> >>someone says "My local setup directory is HERE" when HERE has 
> >>subdirectories that don't belong to cygwin-setup.  (That's 
> >>bad, don't do 
> >>that: setup's 'local directory' is his own personal 
> playground and he 
> >>doesn't play well with others)
> > 
> > 
> > I hope that this isn't going to be the solution to the problem of
> > setup.exe finding non-setup.exe setup.ini files.  Although 
> I don't think
> > that I will make this mistake again, I expect that it will happen to
> > future users who are not reading this list today.
> 
> Perhaps some explanatory text on the panel where setup asks 
> for "local 
> directory" would be nice.  Something like "This is the cygwin setup 
> program's private cache.  Do not choose a directory with pre-existing 
> contents, unless those contents are the result of an earlier 
> run of this 
> setup program".  Care to provide a patch?
> 
> But no, it's not "the solution".  Chris has already added 
> some code that 
> assists setup in parsing only "proper" setup.ini files and skipping 
> non-setup.exe-related ones.
> 

It's the "do not choose" portion of this solution that I hope setup.exe
would avoid because it isn't paying attention to Murphy's Law.  The way
setup.exe runs now there are (at least) two possible sources of errors:

  1) setup.exe's setup.ini has become corrupted.  This is well handled
by setup.exe with its display of parsing errors.

  2) The user may have selected a Local Package Directory that contains
non-setup.exe setup.ini files.  The message that is reported for this
user error (that is, 'user selected a Local Package Directory that has
non-setup.exe package files in it') is, unfortunately, the same message
as that used to report problem 1, above.

     This can be doubly confusing because a user can run setup.exe
successfully for a long time, and then find that it stops working due to
mysterious parsing errors because s/he has installed some other package
("I'm keeping all of my installations in a single, separate directory
tree").

     So, even if we add the text you suggested telling the user about
the rules for 'Local Package Directory', setup.exe should report the
error better (i.e., not reuse the error processing method of different
kind of error) when the user doesn't follow the rules.

-mark

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

^ permalink raw reply	[flat|nested] 18+ messages in thread
* RE: setup.exe 2.218.2.8/9 broken
@ 2002-05-17 20:35 Robert Collins
  0 siblings, 0 replies; 18+ messages in thread
From: Robert Collins @ 2002-05-17 20:35 UTC (permalink / raw)
  To: Harig, Mark A., cygwin



> -----Original Message-----
> From: Harig, Mark A. [mailto:maharig@idirect.net] 
> Sent: Saturday, May 18, 2002 4:07 AM
> 
> It's the "do not choose" portion of this solution that I hope 
> setup.exe
> would avoid because it isn't paying attention to Murphy's 
> Law.  The way
> setup.exe runs now there are (at least) two possible sources 
> of errors:
> 
>   1) setup.exe's setup.ini has become corrupted.  This is well handled
> by setup.exe with its display of parsing errors.
> 
>   2) The user may have selected a Local Package Directory 
> that contains
> non-setup.exe setup.ini files.  The message that is reported for this
> user error (that is, 'user selected a Local Package Directory that has
> non-setup.exe package files in it') is, unfortunately, the 
> same message
> as that used to report problem 1, above.

This is because setup cannot tell the difference. Can it be taught to
tell the difference? Possibly, but I won't be doing the teaching.
 
>      This can be doubly confusing because a user can run setup.exe
> successfully for a long time, and then find that it stops 
> working due to
> mysterious parsing errors because s/he has installed some 
> other package
> ("I'm keeping all of my installations in a single, separate directory
> tree").

I keep all mine in a single separate directory tree too. This
functionality will never go away. It's keeping setup's 'local package
dir' at a logical node in the tree rather than a leaf that is the
problem.
 
>      So, even if we add the text you suggested telling the user about
> the rules for 'Local Package Directory', setup.exe should report the
> error better (i.e., not reuse the error processing method of different
> kind of error) when the user doesn't follow the rules.

It's the same sort of error to setup. I'll accept a patch that can
-accurately- differentiate between the problems. Don't diff against the
distributed source, diff against CVS for this please, as the HEAD parser
is somewhat...different.

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/

^ permalink raw reply	[flat|nested] 18+ messages in thread
* RE: setup.exe 2.218.2.8/9 broken
@ 2002-05-17 20:35 Robert Collins
  0 siblings, 0 replies; 18+ messages in thread
From: Robert Collins @ 2002-05-17 20:35 UTC (permalink / raw)
  To: Jon LaBadie, cygwin



> -----Original Message-----
> From: Jon LaBadie [mailto:jcyg@jgcomp.com] 
> Sent: Saturday, May 18, 2002 4:46 AM

> 
> Not being a PC person, are "setup.exe" and "setup.ini" the 
> names used by convention or is there some Windows requirement 
> for these names.

Convention.
 
> If convention, could situation 2 be eliminated by adding a 
> "cygwin" id to the name e.g. setup-cyg.ini.  setup.exe 
> (?setup-cyg.exe?) could look for the new version 
> preferentially, falling back to the old if not found.

Until a new piece of software - say a cygwin related tool - calls it's
ini files setup-cyg.ini. I see this as an interesting idea, but
fundamentally just a kludge.

The real solution IMO is to
* Rather than default to CWD if there is no stored preferemce default to
CWD + /archive (to catch what could be a common approach of making
c:\cygwin and then running setup from there. This is an approach
'taught' to folk older auto-extracting archive programs).
* When the local package dir is chosen, do a scan for ini files, and if
any parsing errors occur, complain at that point (and not with the
parsing error), rather than when heading into the chooser. This allows
us to say 'The local package dir you have chosen contains setup.exe
specific files that are corrupt or invalid. Please see
http://www.cygwin.com/setup-ug.html for more information'.

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/

^ permalink raw reply	[flat|nested] 18+ messages in thread
* RE: setup.exe 2.218.2.8/9 broken
@ 2002-05-17 10:11 Harig, Mark A.
  2002-05-17 11:03 ` Charles Wilson
  0 siblings, 1 reply; 18+ messages in thread
From: Harig, Mark A. @ 2002-05-17 10:11 UTC (permalink / raw)
  To: cygwin

> -----Original Message-----
> From: Charles Wilson [mailto:cwilson@ece.gatech.edu]
> Sent: Thursday, May 16, 2002 11:52 PM
> To: John Haggerty
> Cc: cygwin@cygwin.com
> Subject: Re: setup.exe 2.218.2.8/9 broken
> 
(text deleted)
> 
> (3) bug #2: minor issues with parsing "buried" setup.ini 
> files -- that 
> belong to things NOT cygwin-setup.exe-related.  This happens 
> only when 
> someone says "My local setup directory is HERE" when HERE has 
> subdirectories that don't belong to cygwin-setup.  (That's 
> bad, don't do 
> that: setup's 'local directory' is his own personal playground and he 
> doesn't play well with others)

I hope that this isn't going to be the solution to the problem of
setup.exe finding non-setup.exe setup.ini files.  Although I don't think
that I will make this mistake again, I expect that it will happen to
future users who are not reading this list today.

Also, I'd like to suggest that when setup.exe finds syntax errors in a
setup.ini file, it log those messages in a file so that the messages can
be used in reporting problems with setup.exe.  I've been unable to
cut&paste the text from the windows that list the parsing errors.

-mark

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

^ permalink raw reply	[flat|nested] 18+ messages in thread
* RE: setup.exe 2.218.2.8/9 broken
@ 2002-05-17  3:16 Robert Collins
  0 siblings, 0 replies; 18+ messages in thread
From: Robert Collins @ 2002-05-17  3:16 UTC (permalink / raw)
  To: Chris Down, cygwin



> -----Original Message-----
> From: Chris Down [mailto:chris@alcor.demon.co.uk] 
> Sent: Friday, May 17, 2002 6:27 PM
> To: 'cygwin@cygwin.com'
> Subject: Re: setup.exe 2.218.2.8/9 broken
> 
> 
> Some info that may help ( or not ).
> 
>  I regularly update my Cygwin installation ( Win2k) and I do 
> not usually 
> get any problems. However I recently updated using 
> setup-2.218.2.9 and the 
> "Download Incomplete" window popped up. After investigating I 
> found that 
> this only occurred if I tried to do an internet install  on the Setup 
> sources. If I omit this everything is fine. I use mirrors.rcn.net for 
> installs. This is repeatable on my set up.
> 
> This may or may not help users.

It will help the developers. Thanks.

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/

^ permalink raw reply	[flat|nested] 18+ messages in thread
* Re: setup.exe 2.218.2.8/9 broken
@ 2002-05-17  2:33 Chris Down
  0 siblings, 0 replies; 18+ messages in thread
From: Chris Down @ 2002-05-17  2:33 UTC (permalink / raw)
  To: 'cygwin@cygwin.com'

Some info that may help ( or not ).

 I regularly update my Cygwin installation ( Win2k) and I do not usually 
get any problems. However I recently updated using setup-2.218.2.9 and the 
"Download Incomplete" window popped up. After investigating I found that 
this only occurred if I tried to do an internet install  on the Setup 
sources. If I omit this everything is fine. I use mirrors.rcn.net for 
installs. This is repeatable on my set up.

This may or may not help users.

Regards

Chris Down

E-Mail Chris.Down@tptdesigns.co.uk




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

^ permalink raw reply	[flat|nested] 18+ messages in thread
* setup.exe 2.218.2.8/9 broken
@ 2002-05-16 20:55 Dockeen
  2002-05-16 21:11 ` Christopher Faylor
  2002-05-16 21:56 ` John Haggerty
  0 siblings, 2 replies; 18+ messages in thread
From: Dockeen @ 2002-05-16 20:55 UTC (permalink / raw)
  To: haggerty, cygwin

Preamble:
I don't work at Cygnus, I am just another user.
(Well, maybe less skilled that any other user)

Why I am writing:
I have been upgrading Cygwin essentially daily on my work
and home machines, using the newest setup almost all the
time, and I have almost never seen a failure.  This can NOT be
because of above average skill or intelligence on my part!
Though I too am a physicist, I possess neither.  :-)
I do want to help though.

Now, almost all of my operations with setup have been
incremental installs, in the last two weeks, I have
done only one download to a CD and install on a non-networked,
no Cygwin present (at all, never installed) machine.

What sort of operation are you performing? New full install,
new partial install, install over a deleted older version,
incremental install etc?

Now, in all but one of my recent installs, I have used
"install from the internet", "all users", "unix".

I have a designated directory I let install work with,
c:\xfer\cygtemp, that is where it puts its temporary stuff.
That is the directory where I keep setup.  That is the
directory where I designate in "Select Local Package Directory".
There seem to be some issues with people using their 
c:\cygwin in this role.  Note also that I do not designate
any of the mirror subdirectories that are in my cygtemp
directory.  My connection, I use "Use IE5 Settings".  I 
have always used the mirror ftp://archive.progeny.com ,
if you look in my Cygtemp directory, you will see that there
is only one mirror folder in there.  Note though that I have
done successful incremental installs in which I have deleted
the mirror subdirectory.

This takes me through to the Cygwin Setup menu.  I open
all the categories, and install almost everything.  Ooops,
Wayne, you have been guilty of that omission - I have nearly
all the Cygwin packages installed, even the bloody games,
which are there for no intellegent reason I can tell you.

Now, this procedure works for me, for the use I describe.
It has worked for this machine, which is Win98, and my on-base
machine, which is XP-Pro.  The machine I did the virgin install
on runs Win2000 Pro.

Now, this evening, I did see a failure of the sort you note, because
I messed up and did not download the new .9 version of setup.
This is the only failure I noted.  (I also noted that gsl is
now included, that made my evening, I use it a goodly amount and
have been installing it seperately before)

I hope my experience helps in solving your problem.  I hope
it also encourages you to report the sorts of things I have
told you about my install procedure.  It really helps the guys
in trouble shooting.

Wayne Keen


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

^ permalink raw reply	[flat|nested] 18+ messages in thread
* setup.exe 2.218.2.8/9 broken
@ 2002-05-16 20:36 John Haggerty
  2002-05-16 20:43 ` Christopher Faylor
  2002-05-16 22:59 ` Charles Wilson
  0 siblings, 2 replies; 18+ messages in thread
From: John Haggerty @ 2002-05-16 20:36 UTC (permalink / raw)
  To: cygwin

As far as I can see, setup 2.218.2.8 and 2.218.2.9 are still broken, as
described on this list.  

In case it's not clear, you go through an entire download, and the last
thing to be downloaded reports "Download Incomplete" on a popup, and as
far as I can see, you can never correctly install Cygwin.  Like other
correspondents, I've tried several combinations of mirrors and download
styles, and none of them seem to work correctly or completely or at
least without very alarming sounding error messages.  Beats me whether
the post-install script works or not.

If you're going to work on this, could you leave a working version in
place while you do so, and try it before posting it?  Thanks.

-- 
John Haggerty
internet: haggerty@bnl.gov
voice/fax: 631 344 2286/4592
http://www.phenix.bnl.gov/~haggerty

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

^ permalink raw reply	[flat|nested] 18+ messages in thread

end of thread, other threads:[~2002-05-18  0:13 UTC | newest]

Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-05-17 12:23 setup.exe 2.218.2.8/9 broken Harig, Mark A.
2002-05-17 13:00 ` Jon LaBadie
2002-05-17 14:52 ` Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2002-05-17 20:35 Robert Collins
2002-05-17 20:35 Robert Collins
2002-05-17 10:11 Harig, Mark A.
2002-05-17 11:03 ` Charles Wilson
2002-05-17  3:16 Robert Collins
2002-05-17  2:33 Chris Down
2002-05-16 20:55 Dockeen
2002-05-16 21:11 ` Christopher Faylor
2002-05-16 21:56 ` John Haggerty
2002-05-17  9:09   ` David T-G
2002-05-16 20:36 John Haggerty
2002-05-16 20:43 ` Christopher Faylor
2002-05-16 22:59 ` Charles Wilson
2002-05-16 23:36   ` Alan Dobkin
2002-05-17  0:04   ` John Haggerty

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