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 #820065,
regarding gitlab: please adapt the postinst output for Debian
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.)


-- 
820065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.5.8+dfsg-3
Severity: wishlist

Hi,

when upgrading gitlab, the user might be presented with stanzas like
this:


     [...]
     Check GitLab API access: FAILED. code: 502
     gitlab-shell self-check failed
       Try fixing it:
       Make sure GitLab is running;
       Check the gitlab-shell configuration file:
       sudo -u gitlab -H editor /usr/share/gitlab-shell/config.yml
       Please fix the error above and rerun the checks.
     [...]
     Checking Sidekiq ...
     
     Running? ... no
       Try fixing it:
       sudo -u gitlab -H RAILS_ENV=production bin/background_jobs start
       For more information see:
       doc/install/installation.md in section "Install Init Script"
       see log/sidekiq.log for possible errors
       Please fix the error above and rerun the checks.
     [...]
     All migrations up? ... no
       Try fixing it:
       sudo -u gitlab -H bundle exec rake db:migrate RAILS_ENV=production
       Please fix the error above and rerun the checks.
     [...]


As a user, I'd expect that after installing the "gitlab" package, I can
follow the above instructions without problems. Unfortunately, this is
not the case, because:

 - the gitlab package does not Depends, Recommends or Suggests sudo or
   an editor
 - executing bin/background_jobs does not seem to work on a Debian
   system
 - as described in README.Debian, the "sudo -u gitlab -H bundle exec
   rake" line will not work on Debian gitlab

I see the following ways to fix this:

 - suggest sudo and editor
 - adapt the messages such that they give advice which can be executed
   on a Debian gitlab installation
 - add more sections to README.Debian like "if gitlab tells you to run
   A, run B instead"

Thanks!

cheers, josch

--- 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 ---

Reply via email to