Wapt Enterprise 2.6.0.17392
Debian 12 server,
Windows 11 package machine.
Hello,
I would like to know if I change the name of a package (package in the control file), will it be seen as a new package or as an update to the existing package?
Regards,
[RESOLVED] Package name change
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 Benoît,
it's the package name that's used for dependency calculations. So if the name is changed, you'll need to assign the new name to the machines and remove (and forget about) the old package.
Regards,
Denis
it's the package name that's used for dependency calculations. So if the name is changed, you'll need to assign the new name to the machines and remove (and forget about) the old package.
Regards,
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
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Benoît,
thanks for the feedback. If the package was assigned individually to the machine, you can use its name to select all the affected machines and add a new package, removing the old one from the dependencies. You can then add the old name to the conflicts list so it gets uninstalled (or do a direct forget/uninstall if the machines are online).
WAPT, like Debian or Red Hat environments, is based on the concept of packages (and package names), indexes (Packages), and dependencies. This leads to several advantages in terms of packaging, load balancing, and horizontal scalability with secondary repositories. But it's true, it does create a stronger adherence to the naming convention.
I'm marking the topic as resolved.
Best regards,
Denis
thanks for the feedback. If the package was assigned individually to the machine, you can use its name to select all the affected machines and add a new package, removing the old one from the dependencies. You can then add the old name to the conflicts list so it gets uninstalled (or do a direct forget/uninstall if the machines are online).
WAPT, like Debian or Red Hat environments, is based on the concept of packages (and package names), indexes (Packages), and dependencies. This leads to several advantages in terms of packaging, load balancing, and horizontal scalability with secondary repositories. But it's true, it does create a stronger adherence to the naming convention.
I'm marking the topic as resolved.
Best regards,
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
