[DRE-maint] Bug#868246: gitlab: broken after upgrade on sid due to new ruby-asana

Aurelien Jacobs aurel at gnuage.org
Thu Jul 13 17:00:25 UTC 2017


Package: gitlab
Version: 8.13.11+dfsg1-8

I have a working gitlab instance running on sid.
After my latest apt upgrade, gitlab stopped working.

Here are the messages I got during the upgrade:

Preparing to unpack .../097-ruby-asana_0.6.0-1_all.deb ...
Unpacking ruby-asana (0.6.0-1) over (0.4.0-1) ...
[...]
Processing triggers for gitlab (8.13.11+dfsg1-8) ...
Creating/updating gitlab user account...
Making gitlab owner of /var/lib/gitlab...
Could not find gem 'asana (~> 0.4.0)' in any of the gem sources listed in your
Gemfile.
#########################################################################
# Failed to detect gitlab dependencies; if you are in the middle of an #
# upgrade, this is probably fine, there will be another attempt later.  #
#                                                                       #
# If you are NOT in the middle of an upgrade, there is probably a real  #
# issue. Please report a bug.                                           #
#########################################################################

So ruby-asana was upgraded to 0.6.0 while gitlab requires 0.4.0.
The actual gitlab dependency is ruby-asana (>= 0.4.0~).

After the upgrade, here is what I get in the log:

juil. 13 16:25:43 gitlab systemd[1]: Dependency failed for GitLab Services.
juil. 13 16:25:43 gitlab systemd[1]: gitlab.service: Job gitlab.service/start failed with result 'dependency'.

I downgraded ruby-asana to version 0.4.0-1 from stretch, and gitlab
started working again.

I guess the dependency should be updated in some way in gitlab, or at
worst gitlab should Conflict with ruby-asana > 0.4.0-1.

--
Aurel



More information about the Pkg-ruby-extras-maintainers mailing list