Univention Bugzilla – Bug 31856
MinPhysicalRAM should be tested only when installing a app, not during an update
Last modified: 2013-11-19 06:41:22 CET
The fix for the bug below disabled the test for MinPhysicalRAM completely for updates but leaves it untouched for installations. We should test it in both cases the same way: Just warn the user that his machine does not meet the requirements but let him continue anyway. +++ This bug was initially created as a clone of Bug #31354 +++ I have a UCS 3.1 (1024MB memory) with ox 6.2 and a NON-key-ID license. Then i switched to the test appcenter to update my ox to 7.2. But there is no update Button. presumption: There is not enough free memory. The ox app defines "MinPhysicalRAM=640" but my running system has only -> free -m total used free shared buffers cached Mem: 1002 915 87 0 6 167 But it is ox itself that uses all this memory. At the moment, i need 2 * MinPhysicalRAM to update my ox app (or stop ox before the update). I think it is better not to test MinPhysicalRAM when updating a app, or?
Fixed since univention-management-console-module-appcenter (3.0.21-1)
OK - warning during installation OK - no warning during update if old.MinPhysicalRAM == new.MinPhysicalRAM OK - warning during update if new.MinPhysicalRAM > old.MinPhysicalRAM OK - no warning if no MinPhysicalRAM is set OK - Changelog
UCS 3.2 has been released: http://docs.univention.de/release-notes-3.2-en.html http://docs.univention.de/release-notes-3.2-de.html If this error occurs again, please use "Clone This Bug".