and it worked for going to the latest version (when the installed version was lower than the new version to install), but not to a previous one (rollback, when the installed version was higher than the proposed new version to install)
without that, I think the only approach is to "apt upgrade" manually through ssh, and after that run the cdist type (maybe apt update/upgrade is broken)
removing the jitsi version parameter: all should be upgraded with each version: config files, version number, etc.
related to #13
Today I tried this formula
```
JITSI_VERSION='2.0.6826-1'
__package_apt jitsi-meet --version "${JITSI_VERSION}"
```
and it worked for going to the latest version (when the installed version was lower than the new version to install), but not to a previous one (rollback, when the installed version was higher than the proposed new version to install)
without that, I think the only approach is to "apt upgrade" manually through ssh, and after that run the cdist type (maybe apt update/upgrade is broken)
Proposal:
1. I suggest doing an apt mark of the jitsi packages - https://www.cdi.st/manual/latest/man7/cdist-type__apt_mark.html
2. removing the jitsi version parameter: all should be upgraded with each version: config files, version number, etc.
related to #13
Today I tried this formula
and it worked for going to the latest version (when the installed version was lower than the new version to install), but not to a previous one (rollback, when the installed version was higher than the proposed new version to install)
without that, I think the only approach is to "apt upgrade" manually through ssh, and after that run the cdist type (maybe apt update/upgrade is broken)
Proposal: