error during build "bad magic number for file header"

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
seb b
Messages: 23
Registration: Oct 26, 2017 - 3:12 p.m.

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:

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
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
High
Locked

Return to “WAPT Packages”


  • To go further with WAPT