Tranquil IT Forum

Hello everyone!
After updating to version 2.3.0, I'm having problems when changing maturity levels, for example, with the following errors:
CRITICAL Error uploading package ... Package filename / name is forbidden
CRITICAL merge_stripped_package failed EWaptForbiddden('Package filename / name is forbidden

Any idea what the problem is?
THANKS!

Hello Guillaume,

guigeek wrote: ↑Jan 25, 2023 - 09:20 CRITICAL merge_stripped_package failed EWaptForbiddden('Package filename / name is forbidden

What is the name of the package?

Sincerely,

Denis

I have the problem with waptupgrade for example:
;Package;Version;Maturity;Status;Message
;stm-waptupgrade;2.3.0.13438-43;PROD;ERROR;Upload error for stm-waptupgrade_2.3.0.13438-43_Change maturity to DEV_33995ddb-86fd-4a67-be97-16bbd7900019: Error on server:
EWaptForbiddden('Package filename / name is forbidden: stm-waptupgrade_2.3.0.13438-43_all_Change maturity to DEV_all_336e4baee8e892aa9725b8c0470b1fb6.wapt')

Oops, there's a usability issue. In the maturity change window, you must select a maturity level from the combo box at the top; otherwise, the text "change maturity to" is selected.

This will be fixed in the next version. That said, it's important to choose the correct package maturity.

Regards,

Denis

Ah yes, my bad... weird, I don't think I did it before. I think production was selected by default when I changed the maturity level of a development package...
Or maybe I'm not fully awake yet... quite possible
. Thanks a lot!

Oh no, I'm not crazy!
I tried again with WaptUpgrade... if I switch from production to development... development is pre-selected, but I get an error. However, if I activate the maturity combobox to choose development, it works!
Thanks!

This will be fixed in the next release. Thank you for reporting the bug. I'm marking this topic as resolved.

Regards,

Denis