I thought only I did this kind of stuff but I see I am not alone :o
(http://www.apachehaus.info/temp/zlib_finfo.png)
zlib has been to version 1.2.3 since 18th july 2005. See zlib.net
I can't see the funny thing you see :o
Look at the different file version for the dll.
Right off the get-go it says 1.2.2 but then later i says 1.2.3 twice.
If you open the win32/zlib1.rc file you can plainly see this as well.
Now I see what you mean ;D
I guess someone forgot to change the upper part.
Send this as a bug ;) to the developer.
I do not think I'll go that far. Then again, maybe I will.
Interestingly, there are three .rc files for windows that I can see, two of them are properly updated and just this one is not. Of course this is the one used when building the dll.
A problem that could stem from this is Installers, if they compare those values to determine whether to update the file or not, some may not update the file if the user has v. 1.2.2 on the machine. Any other existing version will still get updated.
They must know and have chosen not to do anything about it. They have to know since GNUWin32 has "fixed" theirs for their build. I would think they would have mentioned it to the author/s.
It's not looking good,
Delivery to the following recipient has been delayed:
zlib At zlib doT net
Message will be retried for 1 more day(s)
Technical details of temporary failure:
-snip-
The error that the other server returned was: 451 451 Temporary local problem - please try later (state 14).
Maybe you can try to send an email to the dev guys themself
jloup