Univention Bugzilla – Bug 54255
During upgrade to 5.0-1 postgres11/autostart is set to "no"
Last modified: 2021-12-16 18:11:44 CET
During update to 5.0-1 the ucr variable postgress11/autostart was set to no. This was left over from preup modifications for ucs 5. We should release a new univention-postgresql version in which the ucr variable is unset again, if it was originally set between the release of ucs 5.0-1 and today.
[5.0-1] e36d390bcc fix[postgresql]: Unset 12.0.2-2 postgresql/autostart doc/errata/staging/univention-postgresql.yaml | 11 +++++++++++ services/univention-postgresql/debian/changelog | 6 ++++++ services/univention-postgresql/debian/univention-postgresql-11.postinst | 13 ++++++------- 3 files changed, 23 insertions(+), 7 deletions(-) Package: univention-postgresql Version: 12.0.2-2A~5.0.0.202112161724 Branch: ucs_5.0-0 Scope: errata5.0-1 [5.0-1] 3ca7a3d05b Bug #54255: univention-postgresql 12.0.2-2A~5.0.0.202112161724 doc/errata/staging/univention-postgresql.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) OK: apt-get install univention-postgresql-11/apt > Unsetting postgres11/autostart
OK: UCRv postgress11/autostart reset to 'unset' state if the the variable value was set to 'no' between 2021-12-14 - 2021-12-16 OK: postgresql is running after the u-postgresql-11 package update, regardless of the state before the package update OK: yaml Verified
<https://errata.software-univention.de/#/?erratum=5.0x176>