Gitlab package upgrade issues (again)

Zygote · 2016-09-04 13:20:03

So I've been running Gitlab on ArchLinux for about a 6 months now and I've experienced significant issues with upgrading the package a couple of times. I cant figure out how to resolve the newest issue though and I fear I need to backup the data and do a fresh install.

I'm trying to upgrade gitlab and gitlab-shell.

community/gitlab       8.10.6-1           -> 8.11.4-1
community/gitlab-shell 3.2.1-1            -> 3.4.0-2

Here is the output from Pacman.

The issue seems to be due to the gitlab package suddenly pulling in ruby-bundler 1.12.5-1 as a new dependency and that conflicts with the existing ruby installation. If I do a force-install gitlab just throws 500-errors whenever I try to access it and error logs complain about redis issues.

Not sure what's going on with the gitlab package maintenance but this is the third time an upgrade has rendered my existing gitlab installation completely broken. Thank god for VM snapshots.

Any ideas?

Trilby · 2016-09-04 14:17:04

1) that's not actually pacman output. You conveniently hid the actual command used. I don't think it's relevant, but please do not try to disguise what you are actually doing when you are reporting issues.

2) See the wiki:
https://wiki.archlinux.org/index.php/Pa … 9.22_error

Arch Linux

#1 2016-09-04 13:20:03

Gitlab package upgrade issues (again)

#2 2016-09-04 14:17:04

Re: Gitlab package upgrade issues (again)

Board footer