BUG - change package of existing/deployed application

[T1mey]

Hi,

we have a deployed BSP application on an S4 system.
For that application the package must be changed. We're invoking the tooling with command.

deploy ... url: https://url.com service: /it/ABAP_REPOSITORY_SRV client: 100 transport: ABC1234567 package: /COMP/T1 name: /COMP/BSPAPPNAME description: Some desc`

the app is deployed in package T2 and must be updated to T1.

The output:

`
2025-02-28 05:05:20 info    abap-deploy-task: Starting to deploy.\
2025-02-28 05:05:21 info    abap-deploy-task: /COMP/BSPAPPNAME found on target system: true 
2025-02-28 05:05:24 info    abap-deploy-task: SAPUI5 Application /COMP/BSPAPPNAME has been uploaded and registered successfully 
2025-02-28 05:05:24 info    abap-deploy-task: ***** Upload of SAPUI5 App or Library from ZIP-Archive into SAPUI5 ABAP Repository ***** 
2025-02-28 05:05:24 info    abap-deploy-task: Running in regular mode, brief log 
2025-02-28 05:05:24 info    abap-deploy-task: 29 Files found in Archive. 
2025-02-28 05:05:24 info    abap-deploy-task: * Parameters * 
2025-02-28 05:05:24 info    abap-deploy-task: A BAdI implementation for /UI5/BADI_REPOSITORY_LOAD is active: Operation parameters may have been adjusted. 
2025-02-28 05:05:24 info    abap-deploy-task: The name of the SAPUI5 repository "/COMP/BSPAPPNAME" has been determined from the corresponding import parameter. 
2025-02-28 05:05:24 info    abap-deploy-task: The binary files are identified using the standard settings. 
2025-02-28 05:05:24 info    abap-deploy-task: The text files are identified using the standard settings. 
2025-02-28 05:05:24 info    abap-deploy-task: The files and folders to be ignored are determined from the built-in standard settings. 
2025-02-28 05:05:24 info    abap-deploy-task: Transport Request "ABC1234567 " has been determined from the corresponding import parameter. 
2025-02-28 05:05:24 info    abap-deploy-task: The external Code Page Name "UTF8" has been determined from the corresponding import parameter. 
2025-02-28 05:05:24 info    abap-deploy-task: The acceptance of Unix style end of line markers in text files has been determined from the corresponding import parameter. 
2025-02-28 05:05:24 info    abap-deploy-task: Unix style end of line markers in text files get accepted. 
2025-02-28 05:05:24 info    abap-deploy-task: The delta mode has been turned on. 
2025-02-28 05:05:24 info    abap-deploy-task: Safe mode is not activated 
2025-02-28 05:05:24 info    abap-deploy-task: Updating existing SAPUI5 ABAP repository /COMP/BSPAPPNAME 
2025-02-28 05:05:24 info    abap-deploy-task: Upload File    : resources/sap-ui-version.json (Text) 
2025-02-28 05:05:24 info    abap-deploy-task: { 
2025-02-28 05:05:24 info    abap-deploy-task: 	name: com.bsp.appname, 
2025-02-28 05:05:24 info    abap-deploy-task: 	version: 0.0.1, 
2025-02-28 05:05:24 info    abap-deploy-task: 	buildTimestamp: 202502280501, 
2025-02-28 05:05:24 info    abap-deploy-task: 	scmRevision: , 
2025-02-28 05:05:24 info    abap-deploy-task: 	libraries: [] 
2025-02-28 05:05:24 info    abap-deploy-task: } 
2025-02-28 05:05:24 info    abap-deploy-task: * Updating the Application Index * 
2025-02-28 05:05:24 info    abap-deploy-task: Messages from its application log: 
2025-02-28 05:05:24 info    abap-deploy-task: Writing descriptor apps/com.bsp.appname/app/comp/bspappname/ 
2025-02-28 05:05:24 info    abap-deploy-task: For details see the application log (SLG1) in client 000 for object /UI5/APPIDX . 
2025-02-28 05:05:24 info    abap-deploy-task: A BAdI implementation for /UI5/BADI_REPOSITORY_LOAD is active: Final activities may have been performed. 
2025-02-28 05:05:24 info    abap-deploy-task: SAPUI5 Application  has been uploaded and registered successfully 
2025-02-28 05:05:24 info    abap-deploy-task: * Done * 
2025-02-28 05:05:24 info    abap-deploy-task: App available at https://url... 
2025-02-28 05:05:24 info    abap-deploy-task: Deployment Successful. 

After the command run the package is still T2.

We would either expect that a failure is thrown OR the package is changed. But not a successful deployment message...