Hello,
When I select a subset of the machines I manage in the console and filter by package name, I sometimes get two lines pointing to the same package (same name and same version). This doesn't seem normal to me, but perhaps I've misunderstood a concept?
Regards,
WAPT server installed on Debian 12.12
WAPT Server version: 2.6.0.17392
WAPT Agent version: 2.6.0.17392
WAPT Setup version: 2.6.0.17392
WAPT Deploy version: 2.6.0.17392
Duplicate in the console
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
I took a quick look and I understand the reason.
This tab identifies the different packages by their package_uuid.
I have the same issue here, and it happens, for example, when the package has been re-signed without an increment. (New package_uuid, no new version)
I'm not sure if we should merge the two here... (technically, it's not exactly the same package that was installed)
I took a quick look and I understand the reason.
This tab identifies the different packages by their package_uuid.
I have the same issue here, and it happens, for example, when the package has been re-signed without an increment. (New package_uuid, no new version)
I'm not sure if we should merge the two here... (technically, it's not exactly the same package that was installed)
This can also be due to the last audit status, which varies between machines.
If the "Last Audit Status" column is not displayed, you can add it.
This is useful for filtering machines whose audit status is not OK for a given package (by double-clicking on the number).
If the "Last Audit Status" column is not displayed, you can add it.
This is useful for filtering machines whose audit status is not OK for a given package (by double-clicking on the number).
Tranquil IT
