Tranquil IT Forum

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

Hello,

at what stage do the packages appear? When they are added as dependencies to a machine?

Regards,

Ingrid

Yes, that's it

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

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

Good morning,

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

Thank you for this information.

You can close the topic.