Tranquil IT Forum

Hello,
I'm using WAPT 2.4 Enterprise.

I have a question about the package update logic:
- A package can be installed on a machine either via wapt get or through the console.

If I understand the logic correctly:
- A group package (of packages) only includes the package names, without their version numbers
. - When a package is added to a machine via the console, the package name is added to the machine package (which is itself signed).

When the update command is run (from the console, for example), and then the upgrade command is run, all installed packages are updated. Even those installed but not directly (or indirectly) dependent on the machine package (i.e., those installed via wapt get, or remnants of old packages whose dependencies have been removed). Is that correct?

Is that all right?

Hello Florian,

flo777 wrote: ↑March 20, 2024 - 10:34 AM I'm using WAPT 2.4 Enterprise.

A question about the package update logic:
- A package can be installed on a machine either via wapt get or via the console.

If I understand the logic correctly:
- A group package (of packages) only includes the package names, without their version numbers
. - When a package is added to a machine via the console, the package name is added to the machine package (which is itself signed).

When the update command is run (from the console, for example), then upgrade, all installed packages are updated. Even those installed but not directly (or indirectly) dependent on the machine package (i.e., those installed via wapt get, or remnants of old packages whose dependency has been removed). Is that correct?

Am I right?

Yes, absolutely. You have to understand that it's the local agent that calculates what it needs, so whether the package was installed locally via command line (or through self-service) or through a dependency (machine package, OU package, group package, etc.) does not change the mechanism by which the agent checks for updates for all installed packages.

We looked into implementing the "hold" function of `apt`, like in Debian, to freeze a version (if that's your next question), but it's not currently on the roadmap. If you want to freeze a package, the best way is to include the version number in the package name.

There's also the concept of `apt autoremove`, which could be implemented to remove packages that were installed as dependencies but are no longer needed. However, like `hold`, this isn't in the roadmap.

Sincerely,

Denis

Thanks for the reply.
Actually, I'm trying to understand how the machine package works. If it's modified when you do a wapt-get, does that mean the machine keeps a private key locally, or is there a hidden, unsigned machine package? I want to know if a package added via wapt-get is treated exactly the same as a package added via the machine package.
Regards,
Florian