Tranquil IT Forum

Hello,

I'm using WAPT on Linux (Debian 13) exclusively for self-service, and here are my two questions:

If I import a new version of a package from the self-service repository, I can directly trigger the update on the machines that have the application installed by right-clicking and selecting "Run Installations" (without needing to modify the self-service repository or anything else).
But if I don't do this, the update never seems to arrive on the clients; it's been 24 hours and it still hasn't arrived, even though the machine is powered on. However, the machine is correctly reporting its audits every two hours.
Is this normal client behavior, as it only works with "push" updates?

Some machines didn't present their full DN on their first connection, so they didn't receive the corresponding "unit" package. I then manually assigned them the self-service repository via "Edit Machine," which pushed them a package with the machine's name. If I try to uninstall this now-obsolete package, it keeps reappearing; I can't find it in the "Private Repository".
Is it possible to remove this package?

Hello,

1- The audit every 2 hours triggers the detection and download of new packages to install, but not their installation. For automatic installation, on Windows clients it should happen when the machine shuts down. For Linux clients, this feature is not available, so you need to add a parameter to the global section of your agent configuration (wapt-get.ini): waptupgrade_task_period (default None). For example: waptupgrade_task_period = 360.

2- If the package is still dependent on a machine or a package installed on a machine, you must first create a conflict to force its uninstallation, or remove it from the dependencies before uninstalling it and then forget about it.

Regards

The first issue is fixed.

For the second, I'd already tried removing the dependencies from the `machine` package, and it's now empty when I double-click on it.
It was this package that initially deployed the `self-service` package, but it's now being deployed by the `unit` package, which ended up being installed on the machine.
Should I uninstall the `self-service` package to remove the `machine` package?

It's a cosmetic issue, but I'm curious to know how to fix it properly.