Downloaded VM is corrupt

User Support
1

Downloaded the latest VM. md5 sum is correct, yet zip file is corrupt. I have tried this several times now. Any suggestions?

md5sum 2017.5
b36d2b44a720d7c231ce6261fc93f53d  2017.5
gisle@NB67035:~$ unzip 2017.5
Archive:  2017.5
warning [2017.5]:  4294967296 extra bytes at beginning or within zipfile
  (attempting to process anyway)
file #1:  bad zipfile offset (local header sig):  4294967296
  (attempting to re-compensate)
replace QIIME 2 Core - 2017.5 (1495755264)/QIIME 2 Core - 2017.5 (1495755264)-disk001.vmdk? [y]es, [n]o, [A]ll, [N]one, [r]ename: A
  inflating: QIIME 2 Core - 2017.5 (1495755264)/QIIME 2 Core - 2017.5 (1495755264)-disk001.vmdk
  error:  invalid compressed data to inflate
file #3:  bad zipfile offset (local header sig):  476126507
  (attempting to re-compensate)
  inflating: QIIME 2 Core - 2017.5 (1495755264)/QIIME 2 Core - 2017.5 (1495755264).ovf
3

Hi @gisle, I took a closer look at this — some ZIP clients seem to make some noise related to 4GB files and 64bit zip. I repackaged the ZIP with some additional flags on it, and on those noisy clients I no longer see those warnings. The new MD5 sum is 86ec1835e41e24495478443a84464034 (you can download at the same URL as before, I hot-swapped the file). For what it’s worth, even with the old zip file, when I used a client that complained about the offset (like what you saw above), the OVF file still loaded up in VirtualBox just fine. Good luck!

1 Like
5

Never got it to work, but 2017.6 works perfectly.

Thanks for the quick response,
Gisle

1 Like
6

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.