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?
Package update
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Florian,
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
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.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?
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
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
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
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
