Your message dated Sun, 19 Feb 2023 01:03:08 +0000
with message-id <e1pty6e-00aph6...@fasolo.debian.org>
and subject line Bug#1031519: Removed package(s) from unstable
has caused the Debian Bug report #846180,
regarding gitlab not restarted after redis-server upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
846180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.13.6+dfsg1-2
Severity: normal
Dear Maintainer,
I just installed an upgraded version of redis-server (but not of gitlab
itself), and after the upgrade gitlab was no longer running. The
following reproduces this easily for me:
$ for i in "" -mailroom -sidekiq -unicorn -workhorse; do
s=gitlab$i; echo $s; sudo service $s status | grep Active; done
gitlab
Active: active (exited) since Mon 2016-11-28 21:06:38 EST; 3s ago
gitlab-mailroom
Active: active (running) since Mon 2016-11-28 21:06:26 EST; 15s ago
gitlab-sidekiq
Active: active (running) since Mon 2016-11-28 21:06:38 EST; 3s ago
gitlab-unicorn
Active: active (running) since Mon 2016-11-28 21:06:26 EST; 15s ago
gitlab-workhorse
Active: active (running) since Mon 2016-11-28 21:06:26 EST; 15s ago
$ sudo apt-get install redis-server --reinstall
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not
upgraded.
Need to get 0 B/407 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 253802 files and directories currently installed.)
Preparing to unpack .../redis-server_3%3a3.2.5-2_amd64.deb ...
Unpacking redis-server (3:3.2.5-2) over (3:3.2.5-2) ...
Processing triggers for systemd (232-6) ...
Processing triggers for man-db (2.7.5-2) ...
Setting up redis-server (3:3.2.5-2) ...
$ for i in "" -mailroom -sidekiq -unicorn -workhorse; do
s=gitlab$i; echo $s; sudo service $s status | grep Active; done
gitlab
Active: inactive (dead) since Mon 2016-11-28 21:06:49 EST; 13s ago
gitlab-mailroom
Active: inactive (dead) since Mon 2016-11-28 21:06:50 EST; 13s ago
gitlab-sidekiq
Active: inactive (dead) since Mon 2016-11-28 21:06:52 EST; 10s ago
gitlab-unicorn
Active: inactive (dead) since Mon 2016-11-28 21:06:50 EST; 12s ago
gitlab-workhorse
Active: inactive (dead) since Mon 2016-11-28 21:06:49 EST; 13s ago
I have no idea whether this is something wrong in the gitlab service
files, something wrong in redis-server, or something elsewhere (e.g. in
debhelper's scripts for restarting on upgrade).
Jason Rhinelander
--- End Message ---
--- Begin Message ---
Version: 13.4.7-2+rm
Dear submitter,
as the package gitlab has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1031519
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
