error during build "bad magic number for file header"
Published: October 31, 2018 - 3:06 PM
Hello everyone,
We recently switched from version 1.3 to version 1.6 of wapt (server under debian 9) and several packages that worked on 1.3 "fell" during the migration.
Since the files still exist, I tried to re-import the packages without success.
So I wanted to recreate one of the packages "from scratch", but when I tried to run the build-package command, I got the following message:
I tried replacing the custom_zip.py file as indicated in viewtopic.php?f=9&t=1105&hilit=bad+magi ... r&start=20
After spending quite a bit of time on it, I realized that all the packages that had been dropped during the migration have an "x64" folder at the root of the package.
So I did a test on a simple package by renaming this folder to "source" and modifying setup.py accordingly, and it works.
The problem is that quite a few software programs (Autodesk software in particular) have the source paths hardcoded in the setup.exe files, so it's more difficult to work around the problem.
Does anyone have any ideas?
Thank you and have a good day.
Seb
We recently switched from version 1.3 to version 1.6 of wapt (server under debian 9) and several packages that worked on 1.3 "fell" during the migration.
Since the files still exist, I tried to re-import the packages without success.
So I wanted to recreate one of the packages "from scratch", but when I tried to run the build-package command, I got the following message:
Code: Select all
Building c:\waptdev\gc-test-wapt
...done building. Package filename c:\waptdev\gc-test_11.0.31-0_all.wapt
Signing c:\waptdev\gc-test_11.0.31-0_all.wapt with key <SSLPrivateKey u'C:\\private\\XXXXX.pem'> and certificate XXXXX (C:\private\XXXXXCS.crt)
ERROR building c:\waptdev\gc-test-wapt: Bad magic number for file header
0 packages successfully built
1 packages failed
List of errors :
c:\waptdev\gc-test-wapt
After spending quite a bit of time on it, I realized that all the packages that had been dropped during the migration have an "x64" folder at the root of the package.
So I did a test on a simple package by renaming this folder to "source" and modifying setup.py accordingly, and it works.
The problem is that quite a few software programs (Autodesk software in particular) have the source paths hardcoded in the setup.exe files, so it's more difficult to work around the problem.
Does anyone have any ideas?
Thank you and have a good day.
Seb