Preparing to unpack .../gitlab-ce_15.0.2-ce.0_amd64.deb ...
* gitlab_rails['lfs_object_store_direct_upload'] has been deprecated since 14.9 and was removed in 15.0. Starting with GitLab 15.0, only direct uploads will be permitted deprecating this configuration key.
* gitlab_rails['lfs_object_store_background_upload'] has been deprecated since 14.9 and was removed in 15.0. Starting with GitLab 15.0, only direct uploads will be permitted deprecating this configuration key.
Deprecations found. Please correct them and try again.
dpkg: error processing archive /var/cache/apt/archives/gitlab-ce_15.0.2-ce.0_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
Running 'reconfigure' is required to re-read config. That is relatively common with Linux services (most only read their config file at start time). It would be possible to monitor the /etc/gitlab/gitlab.rb file and auto reconfigure GitLab on changes, although I'm not sure that it would be optimal in all situations.
Regardless, I'm glad to hear you worked it out and thanks for posting back. I'm sure it'll save someone else some mucking around.
I didn't imply the gitlab reconfiguration should happen automatically at any occasion, I specifically meant the part when dpkg runs when updating, as this is the point of failure. So in my opinion there the script should check if the etc file has changed (usually that's exactly what happens anyway in many apps) and if yes, then run the reconfigure.
I agree that in other situations "trying to be that smart" might not be optimal, so I suggest to do it only in this situation. :-)
Sorry I misunderstood the context that you were meaning. With your added context, yes, I agree. The package should have a post-install script which runs the reconfigure command. IMO it's probably worth just running it anytime an update is done.
The content of this field is kept private and will not be shown publicly. If you have a
Gravatar
account associated with the e-mail address you provide, it will be used to display your avatar.
Running 'reconfigure' is required to re-read config. That is relatively common with Linux services (most only read their config file at start time). It would be possible to monitor the /etc/gitlab/gitlab.rb file and auto reconfigure GitLab on changes, although I'm not sure that it would be optimal in all situations.
Regardless, I'm glad to hear you worked it out and thanks for posting back. I'm sure it'll save someone else some mucking around.