[DRE-maint] Bug#815133: gitlab installation fails with LoadError: cannot load such file -- /usr/share/gitlab/config/application

[Johannes Schauer]

Control: retitle -1 upgrading from gitlab (<< 8.4.3+dfsg-9) to to later versions requires purge and reinstall

Hi,

On Sat, 20 Feb 2016 21:34:50 +0530 Pirate Praveen <praveen at onenetbeyond.org> wrote:
> I'm not able to reproduce it in a fresh install (after apt-get purge).
> 
> Can you check if config is a symlink to /etc/gitlab?
> 
> There are other symlinks too
> 
> config -> /etc/gitlab
> Gemfile.lock -> /var/lib/gitlab/Gemfile.lock
> log -> /var/log/gitlab
> public -> /var/lib/gitlab/public
> tmp -> /run/gitlab
> shared/cache -> /var/lib/gitlab/cache
> /usr/share/gitlab/.secret -> /var/lib/gitlab/.secret
> 
> Can you check if all symlinks are in order?

I already told you in bug #814714, but you again forgot to CC me so I only am
reading this now that I manually checked this bug after having read your reply
to the thread on debian-devel. Thus let me repeat it here:

 | Notice, that the Debian bug tracker does *not* automatically send replies to
 | bugs to the submitter (or participants) of the bug. One has to manually
 | subscribe to the bug to receive updates. So if you want to reach the
 | submitter of a bug, then you either have to put their email in the CC
 | explicitly or add nnn-submitter at bugs.debian.org to the CC where nnn is the
 | current bug number.  The bts will then forward your email to the actual
 | submitter. You can not rely on the submitter of a bug having subscribed to
 | it.

Since by now you sent a few more emails, I assume that you no longer need my
answer to your question above?

> On Sat, 20 Feb 2016 22:37:20 +0530 Pirate Praveen <praveen at onenetbeyond.org> wrote:
> > Hi Josch,
> > 
> > You'll have to do a fresh install as directory structure has changed significantly.
> > 
> > 1. apt-get purge gitlab (removes files, so new version can add symlinks)
> > 2. rm -rf /usr/share/gitlab (config, tmp, log were not empty).
> > 3. userdel -r gitlab (/var/lib/gitlab is new home or .gitconfig can't be created)
> > 4. apt-get install gitlab
> 
> You have to also remove /usr/share/gitlab-shell/.gitlab_shell_secret

Thanks, I'll do a full reinstall then.

Just to make sure I backup all the important stuff, let me summarize:

 - /usr/share/gitlab/public/uploads/ is now /var/lib/gitlab/public/uploads
 - /usr/share/gitlab/.ssh/authorized_keys is now ??

Anything else that I don't want to loose from /usr/share/gitlab before purging?

I also updated the title of this bug so that other users know to look at this
bug before they try to upgrade to a version before 8.4.3+dfsg-9.

Will you implement facilities for a smooth transition in the future?

Otherwise, I'd keep this bug open until gitlab is part of the next stable
release at least.

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20160221/823c7f71/attachment.sig>