Your message dated Sun, 21 Feb 2016 20:18:33 +0530
with message-id <56c9ce41.3060...@autistici.org>
and subject line Re: gitlab installation fails with LoadError: cannot load such
file -- /usr/share/gitlab/config/application
has caused the Debian Bug report #815133,
regarding upgrading from gitlab (<< 8.4.3+dfsg-9) to to later versions requires
purge and reinstall
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
815133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.4.3+dfsg-9
Severity: grave
Justification: renders package unusable
Hi,
I just tried to upgrade my gitlab installation from 8.4.3+dfsg-8 to
8.4.3+dfsg-9 and this happened:
Your bundle is complete!
Use `bundle show [gemname]` to see where a bundled gem is installed.
Running final rake tasks...
Initializing database...
gitlab_production database is not empty, skipping gitlab setup
Precompiling assets...
rake aborted!
LoadError: cannot load such file -- /usr/share/gitlab/config/application
/usr/share/gitlab/Rakefile:5:in `require'
/usr/share/gitlab/Rakefile:5:in `<top (required)>'
(See full trace by running task with --trace)
dpkg: error processing package gitlab (--configure):
subprocess installed post-installation script returned error exit
status 1
Errors were encountered while processing:
gitlab
E: Sub-process /usr/bin/dpkg returned an error code (1)
Thus, the package is uninstallable.
Thanks!
cheers, josch
--- End Message ---
--- Begin Message ---
On Sun, 21 Feb 2016 14:06:18 +0100 Johannes Schauer <jo...@debian.org>
wrote:
> 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-submit...@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.
Sorry, I missed this comment in #814714.
> Since by now you sent a few more emails, I assume that you no longer need my
> answer to your question above?
>
Rahul was able to reproduce it and we confirmed these steps.
> 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 ??
home directory of gitlab user is now changed from /usr/share/gitlab to
/var/lib/gitlab, so /usr/share/gitlab/.ssh/authorized_keys is now
/var/lib/gitlab/.ssh/authorized_keys
> Anything else that I don't want to loose from /usr/share/gitlab before
> purging?
Take a backup of /usr/share/gitlab to be sure.
> 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?
Well, official support for updates are provided only for stable to next
stable. It will not be viable to support updates between unstable versions.
> Otherwise, I'd keep this bug open until gitlab is part of the next
> stable release at least.
I don't think this should block gitlab migration to testing. If someone
is choosing to install a package from unstable, they know what level of
support to expect.
I'm closing this bug now.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
