Mail Archives: cygwin/2001/11/02/05:10:57
>>Can you tell me how to reproduce?
>
>You would ask. I think it happens when you've downloaded a new version
>of setup.ini but there is an old version of a package in your sandbox.
>
>It annoyed me enough that I recently updated my download sandbox,
>thinking that I'd get around to fixing things since I knew
>just what was
>causing the problem. Of course, now I can't duplicate it anymore. I
>did go as far as investigating the problem a while ago and came to the
>conclusion that the "state machine" that I introduced in
>recent versions
>of setup.exe was flawed. I think the reason it is flawed is that we're
>overloading the selection part of the process.
>
>But, I can't duplicate it now, as hard as I try. I thought
>that someone
>had mentioned this in cygwin-developers, though. I'll check.
I've reported this some months ago. IIRC it happens when you chose not to
omit a new package for download. Starting the setup again for the local
installation, setup will deinstall the old version if
1) you omit the new package again (since you have not downloaded it) and
2) the old package in the local sandbox is older than the "last" package of
setup.ini
happened more than once to me ...
Regards,
Jorg
--
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/
- Raw text -