Hello,
I wanted to report a bug (display issue?).
When I upload a package via my Linux console (2.5.4.15342),
the upload itself goes smoothly. However, when I try to use this package from a Windows console,
not all of the package's properties appear in the dependency add window.
In fact, only the "package" name is displayed, with no other information (Section / Name / Description / Signatory / Signed on / Publisher, etc.),
whereas everything displays correctly in the "Private Repository" tab.
It's not a major problem at the moment, but since I'm increasingly using the Linux console, it could become an issue someday.
I haven't explored the application to see if this might affect other tabs.
Best regards,
Baptiste.
[SOLVED] wapt console linux 2.5.4.15342
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
Last edited by bgallois on May 28, 2024 - 21:07, edited 1 time.
- 1 WAPT 2.5.5.15602 Enterprise server (3000 workstations) + 1 WAPT 2.4.0.14058 Enterprise server (10000 workstations)
- WAPT server OS: Linux REHL 8.7
- Administration/package creation machine OS: Windows Server 2019 v1809
- WAPT server OS: Linux REHL 8.7
- Administration/package creation machine OS: Windows Server 2019 v1809
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Baptiste,
actually it's not a bug, but a feature, or at least a feature fix...
In WAPT's operation, the agent chooses the correct version of the package it will use, not the package selection window. To illustrate this, in the machine package, only the package name is added, not the OS version or the package version: the agent takes the latest available version based on the installation constraints (OS, OS version, language, etc.).
So, to be closer to reality, we stopped filling in the grid, because it could be misleading, and the information wasn't always correct (only the package name is guaranteed to be correct).
So this is normal, and it will work correctly even if you're using a Linux console, and whether you have Linux or Windows agents.
In a multi-platform environment, when importing packages in the "Import Packages" window, be sure to check the "Compatible with known machines" box. This will automatically select available packages based on the OS type/version/language/architecture present in your repository.
I hope this explanation is clear enough.
Sincerely,
Denis
actually it's not a bug, but a feature, or at least a feature fix...
In WAPT's operation, the agent chooses the correct version of the package it will use, not the package selection window. To illustrate this, in the machine package, only the package name is added, not the OS version or the package version: the agent takes the latest available version based on the installation constraints (OS, OS version, language, etc.).
So, to be closer to reality, we stopped filling in the grid, because it could be misleading, and the information wasn't always correct (only the package name is guaranteed to be correct).
So this is normal, and it will work correctly even if you're using a Linux console, and whether you have Linux or Windows agents.
In a multi-platform environment, when importing packages in the "Import Packages" window, be sure to check the "Compatible with known machines" box. This will automatically select available packages based on the OS type/version/language/architecture present in your repository.
I hope this explanation is clear enough.
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
Good evening Denis,
okay, I understand how it works better now,
thank you for this additional information
. Have a good evening.
Baptiste
okay, I understand how it works better now,
thank you for this additional information
. Have a good evening.
Baptiste
- 1 WAPT 2.5.5.15602 Enterprise server (3000 workstations) + 1 WAPT 2.4.0.14058 Enterprise server (10000 workstations)
- WAPT server OS: Linux REHL 8.7
- Administration/package creation machine OS: Windows Server 2019 v1809
- WAPT server OS: Linux REHL 8.7
- Administration/package creation machine OS: Windows Server 2019 v1809
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Baptiste,
thanks for your feedback , I'm marking the topic as resolved.
Denis
thanks for your feedback
, I'm marking the topic as resolved. 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
