[From nobody Tue May 26 11:27:17 2026
Received: (at submit) by bugs.debian.org; 5 Apr 2016 06:49:38 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.0-bugs.debian.org_2005_01_02
 (2014-02-07) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-16.8 required=4.0 tests=BAYES_00,FROMDEVELOPER,
 HAS_PACKAGE,HELO_MISC_IP,XMAILER_REPORTBUG,X_DEBBUGS_CC autolearn=ham
 autolearn_force=no version=3.4.0-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 5; hammy, 149; neutral, 64; spammy, 1.
 spammytokens:0.955-+--H*r:bugs.debian.org
 hammytokens:0.000-+--H*M:reportbug, 
 0.000-+--H*MI:reportbug, 0.000-+--H*x:reportbug, 0.000-+--H*UA:reportbug,
 0.000-+--UD:Debian
Return-path: <josch@debian.org>
Received: from win7217.informatik.uni-wuerzburg.de ([132.187.9.217]
 helo=[127.0.0.1])
 by buxtehude.debian.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <josch@debian.org>) id 1anKnx-0003sf-Nu
 for submit@bugs.debian.org; Tue, 05 Apr 2016 06:49:37 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Johannes Schauer <josch@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: gitlab: please adapt the postinst output for Debian
Message-ID: <20160405064934.22597.42037.reportbug@localhost>
X-Mailer: reportbug 6.6.4
Date: Tue, 05 Apr 2016 08:49:34 +0200
X-Debbugs-Cc: josch@debian.org
Delivered-To: submit@bugs.debian.org

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
]