Page 2 of 2

Re: Package resignation error (WAPT 2.0 transition)

Published: June 28, 2021 - 09:58
by Christophe0110
vcardon wrote: June 18, 2021 - 5:17 PM However, the documentation clearly states that a Linux server is better suited for production.

I'm commenting here to emphasize to any readers who might come across this post that a WAPT server running Windows is a courtesy granted, not a commitment.

You have the solution to your problem in your first post. Why not use Debian 10 for your production environment, as you successfully do for your pre-production environment? If your management insists on using a supported OS for your production environment, then Red Hat will be your best choice.
Good morning,

I understand that a Linux server is more suitable than a Windows server (and I agree with you on that point), but indeed, my management is "anti-Linux" and only wants Windows Server. I already had to negotiate to be able to run my pre-production server on Linux instead of Windows...
That's why I have no other choice but to use Windows for our production server... However, although I understand that this is not what is recommended, I had not had any particular problems before this 2.0 update.

In the meantime, I "solved" my problem with a rebuild followed by a manual upload-package for the large packages that weren't uploading. It's more work, but oh well...