Hello,
I have a problem with maturity management.
I'm the only one who has `maturities=DEV,PREPROD,PROD` in their wapt-get.ini configuration file.
Previously, DEV packages only appeared on my machine, but now they appear everywhere, especially when packages have gone through the DEV>PROD>DEV path.
If I take a machine with `maturities=PROD` in wapt-get.ini
on Wapt Enterprise 2.6.1.17665:
- if I create a DEV package, it doesn't appear (OK)
- I create a PROD package
- I now have DEV, PROD (NO, I only want PROD to appear)
- I delete the PROD package
- the package still appears, and in the maturity column, I still have DEV,PROD.
Do you have any idea why?
Previously, it seems to me that it worked differently, with DEV packages only appearing if the destination machine had the DEV maturity level
.
I just ran another test by moving a package to PREPROD, and now all three maturity levels are displayed in the console, even though I only have one package present and I've correctly removed the older versions.
I have the impression that it's keeping track of all the maturity levels the package has gone through, instead of just the latest one
.
Alternatively, is there another way to display DEV packages only for certain technicians in the console? In addition to checking on the destination machines.
Sincerely,
Yoann
All levels of maturity are displayed
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
Indeed, at this level all packages are displayed, regardless of their maturity level, even if that maturity level no longer exists in the private repository. However, a DEV package will not install on a machine that does not have DEV maturity.
If you wish to limit the actions of the technicians, the simplest solution is to manage packages by signing them with a certificate and deploying them only to certain machines, using ACLs to grant specific rights to certain packages.
Sincerely,
Ingrid
If you wish to limit the actions of the technicians, the simplest solution is to manage packages by signing them with a certificate and deploying them only to certain machines, using ACLs to grant specific rights to certain packages.
Sincerely,
Ingrid
Tranquil IT
Good morning,italbot wrote: ↑Apr 30, 2026 - 3:45 PM Indeed, at this level all packages are displayed, regardless of maturity and even if that maturity level no longer exists in the private repository. However, a DEV package will not install on a machine that does not have DEV maturity.
If you wish to limit the actions of the technicians, the simplest solution is to manage this by signing packages with a certificate and deploying them only on certain machines, using ACLs to grant specific rights to certain packages.
Sincerely,
Ingrid
Thank you for your reply. I assume there are no plans to change this or to filter packets using a simple keyword
For example, I have packages that have dependencies, and sometimes I would like to see only the main package in the list without having the dependent packages displayed
Sincerely,
Yoann
Hello,
The list displays all packages in the repository, so I don't think it's possible to distinguish between packages and their dependencies. The only possible filters are those already present for package name and type.
Regards,
Ingrid
The list displays all packages in the repository, so I don't think it's possible to distinguish between packages and their dependencies. The only possible filters are those already present for package name and type.
Regards,
Ingrid
Tranquil IT
