Our update is currently broken, since openvstorage-extensions is not being installed during an update scenario. This is because 'apt' does not upgrade dependencies when its requirements have already been met.
Eg: Our current control files contain openvstorage-extensions ( >= 0.2.0)
When an update is launched openvstorage will be updated, but the extensions will not since the prerequisites have already been met.
This is a major issue for when updating to the experimental branch.
This won't be an issue if we always bump the version in our control files (framework, alba-asdmanager, iscsi-manager)
Example:
openvstorage-extensions ( >= 0.2.0) in control file
openvstorage-extensions:
Installed: 0.2.0-dev.1504523843.ec3d7d6-1
Candidate: 0.2.0-dev.1504600484.eaf0288-1
With settings above, openvstorage-extensions package will not be updated during update of openvstorage package because the version is already >= 0.2.0
Our update is currently broken, since openvstorage-extensions is not being installed during an update scenario. This is because 'apt' does not upgrade dependencies when its requirements have already been met.
Eg: Our current control files contain
openvstorage-extensions ( >= 0.2.0)When an update is launched
openvstoragewill be updated, but the extensions will not since the prerequisites have already been met.This is a major issue for when updating to the experimental branch.
This won't be an issue if we always bump the version in our control files (framework, alba-asdmanager, iscsi-manager)
Example:
openvstorage-extensions ( >= 0.2.0) in control fileWith settings above, openvstorage-extensions package will not be updated during update of openvstorage package because the version is already >= 0.2.0