Wapt Upgrader Packet Error #Help

[renaud.counhaye]

Hello everyone

I would like a quick and effective helping hand with a very annoying situation that is really pushing me to my limit.

We had 3 WAPT servers in our company and recently decided to migrate all of them to 1 brand new one (1.5).
My idea then is to deploy on these 3 old servers (1.3) and old clients the wapt-upgrade package generated on the new one.

First problem, I can't access the repo of the new server, I'm getting a 403 from nginx and I can't find any documentation to unlock it.

Second problem: I used the console of the new server to download and edit the packet, then I transferred this content to the admin PC of an old server to "recompile" the packet and be able to upload it, result? FAIL.

Code: Select all

2018-04-24 10:18:59,569 WARNING error: (2, 'GetFileVersionInfo:GetFileVersionInfoSize', 'Le fichier sp\xe9cifi\xe9 est introuvable.')
2018-04-24 10:18:59,569 WARNING error: (2, 'GetFileVersionInfo:GetFileVersionInfoSize', 'Le fichier sp\xe9cifi\xe9 est introuvable.')
2018-04-24 10:18:59,571 WARNING error: (2, 'GetFileVersionInfo:GetFileVersionInfoSize', 'Le fichier sp\xe9cifi\xe9 est introuvable.')
  ERROR building C:\waptdev\ymg-deploy-ymagis-nxt-wapt: [Errno 2] No such file or directory: 'patchs\\version'

Looking at the Python code, we notice that it's calling a file that doesn't even exist...

Code: Select all

def update_control(entry):
    """Update package control file before build-upload"""
    waptget = get_file_properties(makepath('patchs','wapt-get.exe'))
    rev = open(makepath('patchs','version')).read().strip()
    entry.package = '%s-waptupgrade' % WAPT.config.get('global','default_package_prefix')
    entry.version = '%s-%s' % (waptget['FileVersion'],rev)

because indeed in the "patches" folder, there is only waptdeploy.exe and no "version" folder.

The real problem is that all the variables in Python are filled dynamically, making the code difficult to read and adapt if you don't want to use sha256.

Ultimately, will my solution even work and allow the old PCs to connect to the new server smoothly, or should I torture myself with the idea of ​​creating a powershell that destroys the old WAPT agent before simply installing the new one... (I've already tried in Python, but obviously, killing the WAPT service and launching the uninstallation doesn't work well together).

I hope you can help me; this migration project is causing a roadblock for us...

Sincerely,

Renaud.