[RESOLVED] Waptagent 2.6 source code for Linux (Ubuntu) inaccessible

[jpass]

WAPT Server Enterprise

WAPT Server version: 2.6.1.17870
WAPT Agent version: 2.6.1.17870
WAPT Setup version: 2.6.1.17870
WAPT Deploy version: 2.6.1.17870

ubuntu 24.04 (Noble)
ubuntu 26.04 (Resolute)

Hello,

for the past few days, we have been unable to install the WAPT agent from https://wapt.tranquil.it/ubuntu/wapt-2. ... lute/main/ or https://wapt.tranquil.it/ubuntu/wapt-2. ... oble/main/ as indicated in the procedure: https://www.wapt.fr/en/doc-2.6/wapt-dep ... -and-macos.

The package (located at https://wapt.tranquil.it/ubuntu/wapt-2. ... 4/Packages , just like the Noble version) no longer references Waptagent, and we're left struggling to understand how to work around this issue.

I've also read that you're encouraging administrators to deploy the .deb, sometimes from https://wapt.tranquil.it/wapt/releases/, which forces us to include an inelegant reference in a script and lock in a version, and sometimes from our own server, which doesn't have a directly accessible .deb (this doesn't work for Linux since the link redirects to the same URL).

In short, I confess I don't understand this change of heart, especially for a version that is otherwise stable and awaiting migration to 2.7.
Furthermore, using a .deb is a source of problems in the case of dependencies or updates (which APT handles very well, by the way).

Would you be so kind as to allow users of version 2.6 to continue using the old method of deploying the agent on Linux workstations (which would certainly represent the least amount of work compared to the suggestion below)?
If not, could you publish an updated procedure to guide administrators on the deployment method?

Overall, shouldn't these changes in strategy and methodology be communicated in advance to facilitate change management for your clients?


Thank you for any assistance you can provide.

[sfonteneau]

Hello

Denis, you replied to a similar message here:

viewtopic.php?p=17992#p17992.

Pointing the agent directly to our WAPT repositories is no longer considered a best practice. It's preferable for the agent to be in the same release as the server. However, if the agent points directly to Tranquil IT's WAPT repositories, it risks being a more recent version.

Therefore, it's preferable to import the .deb package onto your server and use this .deb for the initial installation, and then perform updates using a WAPT package. This is why the agent .deb packages were not synchronized to the Debian/Ubuntu 2.7 repository.

This also applies to the 2.6 repository (release script modification).

From the console, you can create the WaptUpgrade packages for Linux/Windows/Mac, so the installation is done via the console.

Once the upload is complete, the WaptUpgrade packages are available, and the binaries are available on the web interface (still at the same link, so nothing changes in the scripts):

the installation script is simple:

`wget https://srvwapt.ad.tranquil.it/wapt/wap ... -amd64.deb`
followed by `apt-get install ./tis-waptagent

And most importantly, it works offline without internet access.

Our documentation does indeed need updating.

I'll see about restoring it if it's really a blocking issue, but it will be removed eventually anyway.

[sfonteneau]

I just reinstalled it for version 2.6

However, consider that this will not be the case for version 2.7

The "add to repo" command during installation will need to be replaced with:

Code: Select all

wget -O /tmp/tis-waptagent-amd64.deb https://srvwapt.mydomain.lan/wapt/waptagent/tis-waptagent-amd64.deb
apt-get install -y /tmp/tis-waptagent-amd64.deb

which allows installation without our repo and of a version that matches the one present on the server.

[jpass]

Thank you for the quick help and for restoring accessibility for version 2.6, as well as for explaining the installation method for version 2.7.

Have a good day.