[DRE-maint] Bug#847420: gitlab fails to start (shows only 502) after upgrade of ruby-grape-entity

[Antonio Terceiro]

On Thu, Dec 08, 2016 at 10:23:42AM +0530, Pirate Praveen wrote:
> Control: severity -1 normal
> 
> On 2016, ഡിസംബർ 8 8:42:57 AM IST, Johannes Schauer <josch at debian.org> wrote:
> >
> >When I now enter my gitlab instance I only get a 502 error with the
> >message "Whoops, GitLab is taking too much time to respond".
> >
> >Since the last time I changed the version of a ruby package you told me
> >to run assets:precompile, I ran the following command:
> >
> >runuser -u gitlab -- sh -c 'cd /usr/share/gitlab && export $(cat
> >/etc/gitlab/gitlab-debian.conf) && rake assets:precompile
> >RAILS_ENV=production'
> >Could not find grape-entity-0.5.1 in any of the sources
> >Run `bundle install` to install missing gems.
> >
> >Given the error above, I suspect that the new ruby-grape-entity version
> >is the culprit here.
> 
> I think its just the old Gemfile.lock expecting the older version. We should truncate Gemfile.lock in postinst.

You need to both discard Gemfile.lock on upgrades of dependencies as
well, using dpkg triggers. redmine does this for a while, you might want
to check it out.

the same applies to precompiling assets ...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20161208/d754e5a2/attachment.sig>