Installed version not correct and choco -update not valid
Posted: Mon Oct 09, 2023 12:14 pm
Hi Cubert.
Thanks for your ongoing help with this, we are unfortunatley still having real issues making the application manager work as we had hoped.
Firstly the use of Choco --update in use on line 57 and 168 is not a valid command function. The correct replacement from what i can tell would be --upgrade with the flag in use to skip if the package is not installed.
As such i have modified these two lines to use @CHOCOEXE@ upgrade -fy --failonnotinstalled. This seems to be progressing further but is not updating any applications
2nd and possibly a contribution factor to the former. The installed version reported in the application manager is not matching either the actual installed version, or the version reported in the software listing for that machine.
This attachment shows that chrome is installed at version 116.0.5845.141, however both on the machine and in the table provided by automate itself, the application google chrome on this machine is returning 117.0.5938.150.
Further, as you can see in the attachment, a number of software is listed as -9999 rather than the name of the application? I am unable to work out where this originates.
I am overall happy and impressed with the features of habitat thus far but this slew of issues with application manager is a bit disappointing, it was the main component on which we had counted on for getting our 3rd party packages into compliance for rapidly approaching compliance frameworks. Any help getting the case cracked would be hugely appreciated!
Kindest
Sam
Thanks for your ongoing help with this, we are unfortunatley still having real issues making the application manager work as we had hoped.
Firstly the use of Choco --update in use on line 57 and 168 is not a valid command function. The correct replacement from what i can tell would be --upgrade with the flag in use to skip if the package is not installed.
As such i have modified these two lines to use @CHOCOEXE@ upgrade -fy --failonnotinstalled. This seems to be progressing further but is not updating any applications
2nd and possibly a contribution factor to the former. The installed version reported in the application manager is not matching either the actual installed version, or the version reported in the software listing for that machine.
This attachment shows that chrome is installed at version 116.0.5845.141, however both on the machine and in the table provided by automate itself, the application google chrome on this machine is returning 117.0.5938.150.
Further, as you can see in the attachment, a number of software is listed as -9999 rather than the name of the application? I am unable to work out where this originates.
I am overall happy and impressed with the features of habitat thus far but this slew of issues with application manager is a bit disappointing, it was the main component on which we had counted on for getting our 3rd party packages into compliance for rapidly approaching compliance frameworks. Any help getting the case cracked would be hugely appreciated!
Kindest
Sam