6.6.4-3 build is actually 6.6.4-2 build

[tilman]

Hello,

I just downloaded these two 6.6.4-3 files from http://imagemagick.com/script/binary-re ... hp#windows :

http://www.imagemagick.org/download/bin ... static.exe
http://www.imagemagick.org/download/bin ... indows.zip

However both are the 6.6.4-2 versions, not the 6.6.4-3.

Tilman Hausherr

[tilman]

Seems to have been fixed now.

Tilman

Hello,

I just downloaded these two 6.6.4-3 files from http://imagemagick.com/script/binary-re ... hp#windows :

http://www.imagemagick.org/download/bin ... static.exe
http://www.imagemagick.org/download/bin ... indows.zip

However both are the 6.6.4-2 versions, not the 6.6.4-3.

Tilman Hausherr

[Drarakel]

But the Win32 files now contain x64 builds.
http://www.imagemagick.org/download/bin ... ws-dll.exe
http://www.imagemagick.org/download/bin ... static.exe
ftp://ftp.imagemagick.org/pub/ImageMagi ... ws-dll.exe
ftp://ftp.imagemagick.org/pub/ImageMagi ... static.exe

[Drarakel]

The Win32 dynamic binaries are fixed.
But the static binaries for Win32 still (or again?) contain x64 binaries:
http://www.imagemagick.org/download/bin ... static.exe
ftp://ftp.imagemagick.org/pub/ImageMagi ... static.exe

By the way: The changes with version 6.6.4-3 are still listed as 6.6.4-2 in the changelog.

[anthony]

By the way: The changes with version 6.6.4-3 are still listed as 6.6.4-2 in the changelog.

as I am probably at fault. that is typically because of SVN.

I have a downloaded copy of SVN which I update to make changes then merge into the offical repository. The result is that while the SVN I update is one version, the offical SVN repository has been released and the version updated, typically for some other addition or fix that has been made.

As such when I merge, the version number is slightly out by a a day or two (one version release) in the change log version entry to the actual release version.

I try to be careful about this, but it happens.

[Drarakel]

Well, I thought, only the changes from 2010-09-16 belong to version 6.6.4-3. (But not sure..)
Anyway, the main thing are the updates itself - not the changelog. So, thanks!

[Drarakel]

http://www.imagemagick.org/script/binar ... hp#windows
OK.. While I wanted to write another post, some of the 6.6.4-5 files have been updated again. In the Win32 files, "convert -version" now says "6.6.4-6". The Win32 dynamic installer of course works. Even the latest Win32 static installer now works again. Thank you!

But the portable package seems to have problems?
http://www.imagemagick.org/download/bin ... indows.zip
ftp://ftp.imagemagick.org/pub/ImageMagi ... indows.zip
The latest version of this package reports itself as v6.6.4-6. (By the way: The output from "convert -list configure" looks a bit confusing - as 'configure.xml' still has "6,6,2,5" as version number.)
The main thing is: These Win32 files don't work anymore on Win32 systems (at least that's true for my Windows XP installation). When executing 'convert', Windows says that 'vcomp100.dll' is not a valid Windows file. It seems that the EXE files are for Win32, but the DLLs are for x64.(?) These packages work only if I replace the DLLs with the DLLs from the 'normal' Win32 installers.

[magick]

Thanks for the problem report. We reissued the Windows portable distribution. Download and let us know if you have any additional problems.

[Drarakel]

OK, I tested the current Win32 portable distribution. And yeah, this version seems to have the correct Win32 DLLs - so, it works flawlessly now. Thank you!

[tilman]

I think there's still some trouble:
The current distribution is labelled as 6-6-4-5 on the web page, the static portable one is labelled as 6.6.4, but it is 6-6-4-4. Thats what convert and IMDisplay tell me.

Tilman Hausherr

[Drarakel]

You mean this distribution, right?
ftp://ftp.imagemagick.org/pub/ImageMagi ... indows.zip
Did you really re-download it? What you write was true for the.. 'first edition' of the 6.6.4-5 portable files. But the latest (third?) edition reports "6.6.4-6" as version number. (The version numbers don't really fit, but it's a working 6.6.4-5 version at the moment, I think.)

[tilman]

You mean this distribution, right?
ftp://ftp.imagemagick.org/pub/ImageMagi ... indows.zip
Did you really re-download it? What you write was true for the.. 'first edition' of the 6.6.4-5 portable files. But the latest (third?) edition reports "6.6.4-6" as version number. (The version numbers don't really fit, but it's a working 6.6.4-5 version at the moment, I think.)

No I took it from http://www.imagemagick.org/download/bin ... indows.zip .

I'll redownload it tomorrow. Whats even weirder is that I believe that my little bugfix for IMDisplay was active a few days ago in a static portable build, and now it wasn
t there.

[Drarakel]

No I took it from http://www.imagemagick.org/download/bin ... indows.zip .

That's usually the same file. You just have to re-download.

[tilman]

No I took it from http://www.imagemagick.org/download/bin ... indows.zip .

That's usually the same file. You just have to re-download.

It's now the correct version, but the IMDisplay bug is still in the static portable. (mouse cursor vanishes within selection window, see viewtopic.php?f=3&t=17099 )

I'll have a look at the sources at ftp://ftp.imagemagick.org/pub/ImageMagi ... indows.zip and will edit this post after that.

Edit: the RC file is incorrect, see other thread.

Tilman Hausherr

[Drarakel]

Thanks for new versions. The Windows binaries are working. But there's still this version number mismatch.

At least the v6.6.4-6 Win32 files are only renamed (from the 6.6.4-5 files). "convert -version" says v6.6.4-6, but it's really v6.6.4-5. (As for example the "do not break words if caption size is absolute" patch is not contained.)
http://www.imagemagick.org/download/bin ... ws-dll.exe
http://www.imagemagick.org/download/bin ... static.exe
ftp://ftp.imagemagick.org/pub/ImageMagi ... ws-dll.exe
ftp://ftp.imagemagick.org/pub/ImageMagi ... static.exe

The only real v6.6.4-6 version is the portable distribution at the moment:
http://www.imagemagick.org/download/bin ... indows.zip
ftp://ftp.imagemagick.org/pub/ImageMagi ... indows.zip
AND the Win32 static installer - that is stored INSIDE the portable distribution - is also v6.6.4-6.
(That's also the reason why the portable distribution has 70MB! )
Both versions say v6.6.4-7 with "convert -version". The static installer (the one inside the portable distribution) itself first says v6.6.4-5 (that's also the version number in configure.xml here). But it's really v6.6.4-6.

As I said: All Windows versions are working. (Well, I can't check the x64 versions at the moment.) And the Windows binaries doesn't have to be always up-to-date, I would say. But the false version numbers could create confusion (e.g. when one reports a bug for a specific version). And it also creates more traffic (for example, I now always download a lot of files in search for the right versions).