This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: MD5s of setup.exe on mirrors.


"Dave Korn" <dave.korn@artimi.com> writes:

> On 12 May 2007 09:54, ls-cygwin-2006 wrote:
>
>>>>   b31ddcef84f25919a5d3184167b4a90d  setup.exe
>>>> 
>>>> whereas the setup.exe has actually the md5sum:
>>>> 
>>>>   fbc848393ed05ef4f51a253f75bcafeb
>
>
> --- mirror-set.txt      2007-05-12 10:18:58.688913700 +0100
> +++ orig-set.txt        2007-05-12 10:19:07.564595300 +0100
> @@ -25,7 +25,7 @@
>  0001c0 00 00 00 00 40 00 00 e0 2e 72 73 72 63 00 00 00
>  0001d0 00 30 00 00 00 a0 0e 00 00 28 00 00 00 7c 04 00
>  0001e0 00 00 00 00 00 00 00 00 00 00 00 00 40 00 00 c0
> -0001f0 32 2e 30 32 00 55 50 58 21 0d 09 08 07 cf a8 f5
> +0001f0 32 2e 30 33 00 55 50 58 21 0d 09 08 07 cf a8 f5
>  000200 a3 55 5e 01 4d c4 7f 0e 00 c3 77 04 00 00 ea 0c
>  000210 00 26 0d 00 15 7f fb ff ff 55 89 e5 83 ec 18 89
>  000220 5d f8 8b 45 08 31 db 89 75 fc 8b 00 31 f6 06 3d
>
>   The setup.exe on cygwin.com is compressed by upx v2.03 whereas the setup.exe
> on ftp.mirror.ac.uk was compressed by upx v2.02.  Can't guess off the top of
> my head why that doesn't trigger a redownload.  Here's ftp.mirror.ac.uk:
>
> -rwxr-xr-x    1 ftp      ftp        304128 Sep 08  2005 setup.exe
>
>   Here's cygwin.com:
>
> -rwxrwxr-x  1 cgf cygwin 304128 2005-09-08 16:17:51.000000000 +0000 setup.exe
>

>   I wonder how accurately rsync measures timestamps.  Perhaps some
>   mirrors use



The time stamps are partly different in some mirrors, but all from
2005-09-08.

I had been wondering (this is a very wild guess) wether some time zone
issue is creeping in there, but, no, I can't believe that.  Another
guess would be the following scenario:

 - A builds setup.exe with upx 2.0.3 and doesn't upload it yet.
 - B builds setup.exe with upx 2.0.2 and uploads it immediately.
 - Mirrors do the mirroring.

 - A uploads setup.exe (e.g. with cp(1)) -- which means the time stamp
   at the server is now earlier than before.

I imagine (I've a very wild imagination) that could happen if cygwin
had different build machines, perhaps even build on the same
NFS-exported tree, but the build machines had different versions of
UPX.

> the --modify-window option.

Or that. But then md5sum should have changed at the same time and I
wonder why that had been picked up, but setup.exe was not.

Please anyone touch setup.exe? If the mirrors pick it up then we (you!
:) know that it is, somehow, a time stamping issue. The issue can
probably not be cleared up right now and is probably not worth the
trouble, but perhaps it can be just fixed.

Regards -- Markus


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]