RE: New setup pre-release - feedback needed

RE: New setup pre-release - feedback needed

[Harig, Mark A.]

Bug Report:

   When setup.exe completes, but encounters a problem, then it displays
the following message: "Installation incomplete.  Check /setup.log.full
for details."  There is no setup.log.full file in the root directory.
Instead, setup.exe sensibly writes the file in in /var/log.  The message
should tell users to look in that directory.

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

Re: New setup pre-release - feedback needed

[Peter A. Castro]

On Wed, 17 Jul 2002, Robert Collins wrote:

> ----- Original Message -----
> From: "Peter A. Castro" <doctor@fruitbat.org>
> To: <cygwin@cygwin.com>
> Sent: Wednesday, July 17, 2002 5:15 PM
> 
> > On Sun, 14 Jul 2002, Robert Collins wrote:
> >
> > > 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'.
> >
> > While I do like the status of knowing just what setup is scanning as part
> > of the package loading process, it now takes much, much longer to load
> > from an "Install from Local Directory" scenario :-) (up from 5 seconds to
> > about 1 minute, 45 seconds).  It's a kind of a rare scenario (I'm
> > probably one of the few who keeps a full downloaded image of all of
> > cygwin (kinda like a mirror site)), and it's not like I run setup more
> > than once every few days, so it's an adequate trade-off for more status
> > on the package load.
> 
> This is actually the MD5 checking, not the feedback. (I implemented the
> feedback so that we won't get 'setup takes forever on local installs' :} ).

I'm curious, then (that and I've been staying up waaaay to late!).  Is
the MD5 checking new, or just the visual feedback with this version of
setup?  If only the visual feedback is new, then it appears Windows'
graphic elements are slowing down the process.  Any chance you can, you
know, speed up Windows ? ;^)

> > > It *should* be bug free, although there may be a minor bug with
> > > autodetection of upgrades (we have one report, but no debugging info).
> >
> > I did some test installs and re/de-installs and it appears to work well.
> > The only thing I did notice was that during the actual package
> > installation part, the Progress bar is showing "full" when it's installed
> > only about 3/4ths of the files from the package.  I noticed this more
> > with source packages than binaries, but did see it a few times with some
> > binary-only package installs.  It's really just a cosmetic thing and
> > didn't seem to effect the actual installation.  I view it as a reversal
> > of the old '98% finished' phenomenon :-)
> 
> Hmm. Thats strange - I suspect it's a race of some sort with the gui updates
> (we have two threads for blocking IO operations - one to do the UI, one to
> do the IO.) Nothing much has changed there, which is why it's strange.

That is strange.  But as long as nothing goes wrong as a result, it
doesn't matter too much.

> Thanks for the feedback,

Sure thing!

> Rob

-- 
Peter A. Castro <doctor@fruitbat.org> or <Peter.Castro@oracle.com>
	"Cats are just autistic Dogs" -- Dr. Tony Attwood


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

Re: New setup pre-release - feedback needed

[Max Bowsher]

Peter A. Castro wrote:
> On Sun, 14 Jul 2002, Robert Collins wrote:
>
> While I do like the status of knowing just what setup is scanning as
> part of the package loading process, it now takes much, much longer
> to load from an "Install from Local Directory" scenario :-) (up from
> 5 seconds to about 1 minute, 45 seconds).  It's a kind of a rare
> scenario (I'm probably one of the few who keeps a full downloaded
> image of all of cygwin (kinda like a mirror site)),

I do too. I am bandwidth-challenged (24K dialup - poor telephone lines), so I
always have a local copy of anything I install.

>and it's not like
> I run setup more than once every few days, so it's an adequate trade-
> off for more status on the package load.

I suppose it might be better at the completion of each download, and when a
package is actually installed - but then we lose the possibility of marking bad
packages in the chooser.

Max.


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

Re: New setup pre-release - feedback needed

[Max Bowsher]

Robert Collins wrote:
> ----- Original Message ----- From: "Max Bowsher" <maxb@ukf.net>
>> How about 'Source Only' to emphasize the fact that most people don't
>> need setup?
>
> Once there is a binary (which will happen as soon as I get the self-
> update code tested properly) then setup will be needed by most people!

Ah - OK. At that time, will setup.exe be given an official location in /usr/bin
or somesuch, or will it be a special case (potentially outside cygwin's / - just
update in place) ?

Max.


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

RE: New setup pre-release - feedback needed

[Harig, Mark A.]

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/

RE: New setup pre-release - feedback needed

[Robert Collins]

> -----Original Message-----
> From: Harig, Mark A. [mailto:maharig@idirect.net] 
> Sent: Thursday, 18 July 2002 1:00 AM
> To: Robert Collins; cygwin@cygwin.com
> Subject: RE: New setup pre-release - feedback needed
> 
> 
> Thanks for the response!  I have a question/observation below.
> 
> > 
> > > 
> > > Here are some minor changes that might be worth making (no, 
> > they don't
> > > identify bugs):
> > > 
> > >   1. Move the 'emacs'-related items from 'Misc' to 
> 'Editors' so that
> > > they can be found more easily.
> > 
> > This is a setup.ini driven item - you need to talk to whoever is
> > packaging emacs for you and get them to add a categories tag.
> > 
> 
> Hmm.  As far as I know, no one (or only setup.exe) is packaging emacs
> for me.  The only program that I know of that has touched setup.ini is
> setup.exe.  Are you saying that I need to edit setup.ini?  
> Have I missed
> some documentation?

The only way emacs gets in the setup.exe list is if someone packages it.

If you'd like to see some doco on setup.exe, have a look at
http://www.cygwin.com/setup.html.

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/

RE: New setup pre-release - feedback needed

[Harig, Mark A.]

Thanks for the response!  I have a question/observation below.

> 
> > 
> > Here are some minor changes that might be worth making (no, 
> they don't
> > identify bugs):
> > 
> >   1. Move the 'emacs'-related items from 'Misc' to 'Editors' so that
> > they can be found more easily.
> 
> This is a setup.ini driven item - you need to talk to whoever is
> packaging emacs for you and get them to add a categories tag.
> 

Hmm.  As far as I know, no one (or only setup.exe) is packaging emacs
for me.  The only program that I know of that has touched setup.ini is
setup.exe.  Are you saying that I need to edit setup.ini?  Have I missed
some documentation?

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

Re: New setup pre-release - feedback needed

[John Vincent]

Hi,

I've just followed the link to test your pre-release of
setup, and I very much like the changes you've made.

I think I've found a bug however:

I'm using Win2k SP2 with NTFS local disk. I downloaded from
http://www.cygwin.com/setup-snapshots/setup-2.259.2.4.exe
and selected Download for internet. I downloaded from
http://programming.ccp14.ac.uk, changing "default" to "install"
against the "all" option so everything new was downloaded.
Everything went OK, until I got a pop-up box saying "download
incomplete. Try again ?" On trying again, setup determined
there was nothing to download, and then produced the pop-up box
again. I selected "No" and then continued the setup process.
I then re-started setup to "install from local directory"
and everything appears to have gone OK.

I then restarted setup.exe again, and selected "download from internet"
I selected the same source, and to install all, as before. Setup
determined there was nothing to download, but again produced
the "download incomplete"pop-up box.

I hope this report is detailed enough to be helpful.

/John Vincent.




_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com


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

Re: New setup pre-release - feedback needed

[Robert Collins]

----- Original Message -----
From: "Max Bowsher" <maxb@ukf.net>
To: <cygwin@cygwin.com>
Sent: Wednesday, July 17, 2002 5:21 AM
Subject: Re: New setup pre-release - feedback needed


> Harig, Mark A. wrote:
> > Here are some minor changes that might be worth making (no, they don't
> > identify bugs):
> ...
> >   3. 'setup' is available under both 'System' and 'Utils'.  'Admin'
> > seems to me like the most appropriate group for 'setup'.
>
> How about 'Source Only' to emphasize the fact that most people don't need
setup?

Once there is a binary (which will happen as soon as I get the self-update
code tested properly) then setup will be needed by most people!

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/

Re: New setup pre-release - feedback needed

[Robert Collins]

----- Original Message -----
From: "Peter A. Castro" <doctor@fruitbat.org>
To: <cygwin@cygwin.com>
Sent: Wednesday, July 17, 2002 5:15 PM


> On Sun, 14 Jul 2002, Robert Collins wrote:
>
> > 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'.
>
> While I do like the status of knowing just what setup is scanning as part
> of the package loading process, it now takes much, much longer to load
> from an "Install from Local Directory" scenario :-) (up from 5 seconds to
> about 1 minute, 45 seconds).  It's a kind of a rare scenario (I'm
> probably one of the few who keeps a full downloaded image of all of
> cygwin (kinda like a mirror site)), and it's not like I run setup more
> than once every few days, so it's an adequate trade-off for more status
> on the package load.

This is actually the MD5 checking, not the feedback. (I implemented the
feedback so that we won't get 'setup takes forever on local installs' :} ).

> > It *should* be bug free, although there may be a minor bug with
> > autodetection of upgrades (we have one report, but no debugging info).
>
> I did some test installs and re/de-installs and it appears to work well.
> The only thing I did notice was that during the actual package
> installation part, the Progress bar is showing "full" when it's installed
> only about 3/4ths of the files from the package.  I noticed this more
> with source packages than binaries, but did see it a few times with some
> binary-only package installs.  It's really just a cosmetic thing and
> didn't seem to effect the actual installation.  I view it as a reversal
> of the old '98% finished' phenomenon :-)

Hmm. Thats strange - I suspect it's a race of some sort with the gui updates
(we have two threads for blocking IO operations - one to do the UI, one to
do the IO.) Nothing much has changed there, which is why it's strange.

Thanks for the feedback,
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/

Re: New setup pre-release - feedback needed

[Peter A. Castro]

On Sun, 14 Jul 2002, Robert Collins wrote:

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

While I do like the status of knowing just what setup is scanning as part
of the package loading process, it now takes much, much longer to load
from an "Install from Local Directory" scenario :-) (up from 5 seconds to
about 1 minute, 45 seconds).  It's a kind of a rare scenario (I'm
probably one of the few who keeps a full downloaded image of all of
cygwin (kinda like a mirror site)), and it's not like I run setup more
than once every few days, so it's an adequate trade-off for more status
on the package load. 

> It *should* be bug free, although there may be a minor bug with
> autodetection of upgrades (we have one report, but no debugging info).

I did some test installs and re/de-installs and it appears to work well.
The only thing I did notice was that during the actual package
installation part, the Progress bar is showing "full" when it's installed
only about 3/4ths of the files from the package.  I noticed this more
with source packages than binaries, but did see it a few times with some
binary-only package installs.  It's really just a cosmetic thing and
didn't seem to effect the actual installation.  I view it as a reversal
of the old '98% finished' phenomenon :-)

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

I haven't tried a full reload of cygwin (might try that later), but doing
a few minor updates and a few re/de-installs did not turn up any
problems.  Looking good!

> Cheers,
> Rob

-- 
Peter A. Castro <doctor@fruitbat.org> or <Peter.Castro@oracle.com>
	"Cats are just autistic Dogs" -- Dr. Tony Attwood


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

RE: New setup pre-release - feedback needed

[Robert Collins]

Thanks for the feedback.. Responses inline

> -----Original Message-----
> From: cygwin-owner@cygwin.com 
> [mailto:cygwin-owner@cygwin.com] On Behalf Of Harig, Mark A.
> Sent: Wednesday, 17 July 2002 3:37 AM
> To: cygwin@cygwin.com
> Subject: RE: New setup pre-release - feedback needed
> 
> 
> Here are some minor changes that might be worth making (no, they don't
> identify bugs):
> 
>   1. Move the 'emacs'-related items from 'Misc' to 'Editors' so that
> they can be found more easily.

This is a setup.ini driven item - you need to talk to whoever is
packaging emacs for you and get them to add a categories tag.

 
>   2. Combine the 'Devel' and 'Development' groups, unless there's some
> reason for their being separate that I've missed.

There isn't, theres a single package (guile-devel) that has invented a
new category on the fly. Jan, Ohhh Jan!
 
>   3. 'setup' is available under both 'System' and 'Utils'.  'Admin'
> seems to me like the most appropriate group for 'setup'.

Hmm, it could go there I suppose. For now, as there is no binary :}, I'm
happy with the status quo.

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/

Re: New setup pre-release - feedback needed

[Max Bowsher]

Harig, Mark A. wrote:
> Here are some minor changes that might be worth making (no, they don't
> identify bugs):
...
>   3. 'setup' is available under both 'System' and 'Utils'.  'Admin'
> seems to me like the most appropriate group for 'setup'.

How about 'Source Only' to emphasize the fact that most people don't need setup?

Max.


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

RE: New setup pre-release - feedback needed

[Harig, Mark A.]

Here are some minor changes that might be worth making (no, they don't
identify bugs):

  1. Move the 'emacs'-related items from 'Misc' to 'Editors' so that
they can be found more easily.

  2. Combine the 'Devel' and 'Development' groups, unless there's some
reason for their being separate that I've missed.

  3. 'setup' is available under both 'System' and 'Utils'.  'Admin'
seems to me like the most appropriate group for 'setup'.

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

RE: New setup pre-release - feedback needed

[Robert Collins]

> -----Original Message-----
> From: cygwin-owner@cygwin.com 
> [mailto:cygwin-owner@cygwin.com] On Behalf Of Demmer, Thomas
> Sent: Wednesday, 17 July 2002 12:06 AM
> To: 'Robert Collins'
> Cc: 'cygwin@cygwin.com'
> Subject: RE: New setup pre-release - feedback needed
> 
> 
> It kept on printing on it's canvas that it tried to exectue 
> iu-config.sh.
> Looked to me like spawning the process and then repainting. 
> In either the setup.log[.full] it clearly stated that it 
> couldn't create
> the file, that's how I figured it out. 

Cool, thank you. Any chance you can send me the log files?

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/

RE: New setup pre-release - feedback needed

[Demmer, Thomas]

It kept on printing on it's canvas that it tried to exectue iu-config.sh.
Looked to me like spawning the process and then repainting. 
In either the setup.log[.full] it clearly stated that it couldn't create
the file, that's how I figured it out. 

Ciao
Tom

> -----Original Message-----
> From:	Robert Collins [SMTP:robert.collins@syncretize.net]
> Sent:	Tuesday, July 16, 2002 1:51 PM
> To:	Demmer, Thomas
> Subject:	RE: New setup pre-release - feedback needed
> 
> 
> 
> > -----Original Message-----
> > From: Demmer, Thomas [mailto:TDemmer@krafteurope.com] 
> > Sent: Tuesday, 16 July 2002 9:11 PM
> > To: 'Robert Collins'
> > Subject: RE: New setup pre-release - feedback needed
> > 
> > 
> > Hi Rob,
> > I can confirm what a previous poster mentioned: Issues with
> > auto-upgrading, it does not retrieve the latest version of cygwin, 
> > checked on a couple of mirrors.
> > 
> > 
> > 
> > And another way to stumble: I had the permissions on my 
> > /etc/postinstall
> > and /etc/setup set to 755, so set-up failed to create the postinstall
> > shell scripts, but kept on trying regardless and had to be killed via
> > Task Manager. The first was a stupidity of mine, the problem 
> > here is that
> > cygwin apps think I am in the group "DomainUsers", whereas non-cygwin
> > apps create files with group EUUsers (the domain I log into)+ I start
> > setup from a samba share, where I am somebody completely different...
> > The second is probably a glitch in setup that it does not give up
> > with an error message after the first attempt (Yes, I do know 
> > that this
> > case is rather unlikely...)
> 
> When you say it kept on trying, can you describe in more detail what
> setup was (visibly) doing?
> 
> 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/

Re: New setup pre-release - feedback needed

[Joerg R. Schaible]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2678 bytes --]

Hi Robert,

> The pre-release snapshot can be found at
> http://www.cygwin.com/setup-snapshots/setup-2.259.2.4.exe.
>
> 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).

I tried this setup version, but I got some really strange results regarding
the autodetection.

My system was upgraded last time roughly 3 months ago. I always use the
2-step method: Download from Internet; Install from local. I used sunsite.dk
for download.

1) Setup did not present me all updates. E.g. packages like cygwin, cygutils
were at "keep" although I knew there were newer versions (I never switched
between Prev/Curr/Exp, only between the View Category/Full).
2) Even when I'd explicitly chosen e.g. cygutils for the new version 1.1.1.1
(I had still 1.0.0.1) the package was not loaded ... the checkbox in the
binary col was not set. I *assume* any package without a default selection
for the binary column is not selected automatically for an upgrade (possibly
only if the current version is not available as previous version anymore ...
??).
3) Even harded was the upgrade from cygwin 1.3.10.x to 1.3.12-2, since every
time I toggled any other package, the cygwin package was reset to version
1.3.10.x with "keep"
4) I cannot download the gettext package anymore. The explicit selection of
gettext-1.11.2-2 will download it, but it is not available for local
installation toggling the second column (although I got the
gettext-devel-1.11.2-2 package).

The behaviour for the dependencies was equal for "download" and "local
install" mode (except topic 4, since nothing was downloaded).

I tried another download/install loop with the mirror
sunsite.cnlabs-switch.ch because of gettext. Setup warned me that it found
an older setup.ini, but I used it anyway. I supposed that no package would
be downloaded, except of my (again) exlicitly selected gettext-1.11.2-2. I
was astonished, but setup did not only download gettext-1.11.2-2 again, but
also an older version of expat and _PostInstallLast. From the local
installation I had to chose for these two packages "keep" explicitly,
otherwise the two packages would have been downgraded! And again, the
gettext-1.11.2-2 is not avalable for local installation.

Regards,
Jörg





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

New setup pre-release - feedback needed

[Robert Collins]

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/