Am Dienstag, 4. Juni 2019, 08:32:23 CEST schrieb Bernhard Voelker:
On 6/3/19 1:50 PM, Thorsten Kukuk wrote:
Put the default, by a Linux distributor shipped configuration files somewhere below /usr, and /etc only contains the overwrite.
My first feeling: I'm (often) not a fan of such big changes - like in this case.
a) You started with this point as source of the problem: "rpm cannot merge properly". Has anyone tried to enhance / fix it?
Well, I've done something directly related minutes ago, and will show, that
your general solution is able to mitigate the issue (which is a good thing of
course, hence thumbs up from my side), but I want to outline the workflow,
that has to be done for the cases beyond your proposal.
Running a local GitLab installation from home:darix:apps since about 2 years
(now on 15.0). I went though a lot of ups and downs due to package complexity.
Most of the times, where automatic updates fail (rpms install correctly, but
the gitlab-ce-update fails with some obscure traceback...), installation
produced a couple of .rpm{new,save} files. Let's not discuss weal and woe of
this specific package, Darix is doing a tough job here, but what's needed to
address the cases, that your proposal will not fix, and how this could be
provided with a real example.
GitLab upgrade from 11.11.0 to 11.11.2.
$ gitlab-ce-update
Hoping into the basedir within env production
3a51abc8a15d4d06511e9b7331b07175a8ec235ef9c9f818e31b39b3ee314ff7 Gemfile.lock
04112ef0c0e80c1be2093ea3f004770a2ae8daa5afccec364d95fa38a18d189d Gemfile
Running rake
WARNING: Nokogiri was built against LibXML version 2.9.7, but has dynamically
loaded 2.9.9
rake aborted!
NameError: uninitialized constant Gitlab::ProxyHTTPConnectionAdapter
/srv/www/vhosts/gitlab-ce/config/initializers/hipchat_client_patch.rb:4:in
`class:Client'
/srv/www/vhosts/gitlab-ce/config/initializers/hipchat_client_patch.rb:3:in
`module:HipChat'
/srv/www/vhosts/gitlab-ce/config/initializers/hipchat_client_patch.rb:2:in
`