[BUG] ioncube loaders are never updated

[interfasys]

Let's take today's ioncube update as an example

# ./build ioncube
File already exists:    ioncube_loaders_fre_9_x86-64.tar.gz
ionCube loader has been installed.

Really?

-rw-r--r--  1 root  wheel   4.7M Jan  4 07:37 ioncube_loaders_fre_9_x86-64.tar.gz

Hmmm... 4.5.2 was not available on January the 4th.
What does versions.txt say?

# cat versions.txt | grep fre_9_x86-64
ioncube_loaders_fre_9_x86-64:4.5.2:160102d972fdf404ec95ee9861adc1e2

And the file I have?

# md5 ioncube_loaders_fre_9_x86-64.tar.gz
MD5 (ioncube_loaders_fre_9_x86-64.tar.gz) = 69944cd9c75f450f5ac78c93fbd447fe

They don't match!

Must be a bug then.

 

[smtalk]

Have you tried "./build update" for it? That should re-download the file because of the md5 checksum mismatch.

 

[ditto]

I have upgraded to ioncube loaders 4.5.2 on 4 servers and did not have any problems at all. My guess is that smtalk is correct, that you need to run ./build update - also read DirectAdmin support reply in this thread: http://forum.directadmin.com/showthread.php?t=48161

 

[interfasys]

Have you tried "./build update" for it? That should re-download the file because of the md5 checksum mismatch.

You're right, I didn't do a "./build update". I just assumed that CB would always fetch the latest version from versions.conf, which I just remembered is not the default behaviour. I usually download the archives prior to using CB.

But still, if there is a md5 mismatch, the process should not continue and the user should be told to do a "./build update", no?