RE: MD5 support
-Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 2:05 AM Ok. There is a setup-md5.ini in /sourceware/ftp/anonftp/pub/cygwin (home of setup.exe and setup.ini). I generated it against my local release directory so there may be some irregularities in things like sdesc/ldesc and some versions may be off. However, it is usuable as a proof of concept. Thank you. Is it ok with you if I call it setup.ini and put it in a dir called test after inserting ../ in front of every instance of 'release/'? That will allow real testing against the production data. Rob
RE: MD5 support
-Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 2:55 AM Thank you. Is it ok with you if I call it setup.ini and put it in a dir called test after inserting ../ in front of every instance of 'release/'? I guess so. I wonder if it would make sense to have a completely separate test site for this kind of thing so as not to have the mirrors update testing stuff and, more importantly, so that we can make changes in real time. If you've got the bandwidth and disk space... cool. I figured that a single copy of setup.ini getting mirrored was a low-cost solution (vs a completely separate site). Rob
Re: MD5 support
On Fri, May 03, 2002 at 08:44:01AM +1000, Robert Collins wrote: -Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 2:55 AM Thank you. Is it ok with you if I call it setup.ini and put it in a dir called test after inserting ../ in front of every instance of 'release/'? I guess so. I wonder if it would make sense to have a completely separate test site for this kind of thing so as not to have the mirrors update testing stuff and, more importantly, so that we can make changes in real time. If you've got the bandwidth and disk space... cool. I figured that a single copy of setup.ini getting mirrored was a low-cost solution (vs a completely separate site). By site I meant something besides sources.redhat.com that wouldn't rely on accessing a mirror site to be useful. cgf
RE: MD5 support
-Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 9:13 AM If you've got the bandwidth and disk space... cool. I figured that a single copy of setup.ini getting mirrored was a low-cost solution (vs a completely separate site). By site I meant something besides sources.redhat.com that wouldn't rely on accessing a mirror site to be useful. Exactly. Rob
RE: MD5 support
-Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Friday, May 03, 2002 11:27 AM Actually, I decided to just creat a version of setup.exe (based on the setup200202 branch) which silently skips extra the md5 element in install: and source: tags. This version is now installed in /sourceware/ftp/anonftp/pub/cygwin. Cool. Can you checkin the changes (if you haven't already). Thanks, Rob
RE: MD5 support
-Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 2:35 AM I have upset ready to go for this. Will it actually break setup.exe if I check in my changes? I'm away from a Windows system right now so I can't check myself. It will cause parsing errors, so even though setup is (somewhat) resilient, it will generate questions. If you could get upset to make a ini in a new location (perhaps test) that refers to the release directory source files, that would be a great test, and let me be sure that nothing will go ... wrong. ie: /setup.ini /release/. /test/setup.ini -- this contains MD5 information. Can this be done? Rob
RE: MD5 support
-Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 1:32 AM Hmm. Dueling you do the work scenarios. Why not just release an interim version of setup that silently ignores the third field? That's what we've done in the past. I planned to, but then, without realising it, I'd done the code :}. It seemed like to much effort to strip it out, just to ensure more testing... Rob
Re: MD5 support
On Thu, May 02, 2002 at 01:33:52AM +1000, Robert Collins wrote: Hmm. Dueling you do the work scenarios. Why not just release an interim version of setup that silently ignores the third field? That's what we've done in the past. I planned to, but then, without realising it, I'd done the code :}. It seemed like to much effort to strip it out, just to ensure more testing... Hmm. Dueling you do the work scenarios. cgf
Re: MD5 support
On Wed, May 01, 2002 at 11:47:59AM -0400, Christopher Faylor wrote: On Thu, May 02, 2002 at 01:33:52AM +1000, Robert Collins wrote: Hmm. Dueling you do the work scenarios. Why not just release an interim version of setup that silently ignores the third field? That's what we've done in the past. I planned to, but then, without realising it, I'd done the code :}. It seemed like to much effort to strip it out, just to ensure more testing... Hmm. Dueling you do the work scenarios. Ok. There is a setup-md5.ini in /sourceware/ftp/anonftp/pub/cygwin (home of setup.exe and setup.ini). I generated it against my local release directory so there may be some irregularities in things like sdesc/ldesc and some versions may be off. However, it is usuable as a proof of concept. cgf
Re: MD5 support
On Tue, Apr 30, 2002 at 12:40:43PM +1000, Robert Collins wrote: I've uploaded a snapshot (bin src) that detects corrupt files based on md5. It's backward compatible with the current .ini format. The code needs reorganising before I commit it, this is simply for folk to play and test with. There is -no- UI change at this point. The md5 corruption is silently detected (and that will have to change before committing too). I have upset ready to go for this. Will it actually break setup.exe if I check in my changes? I'm away from a Windows system right now so I can't check myself. cgf
