On Mon, Dec 17, 2018 at 11:45 PM Pirate Praveen
wrote:
>
> I think it is trying to use the previous bundler configuration. Try
> purging gitlab and reinstall (make sure /var/lib/gitlab and
> /usr/share/gitlab* are really removed).
>
This doesn't work. I purged gitlab and removed gitlab-shell dir
On 12/18/18 12:20 PM, Pranith Kumar wrote:
> OK, made some more progress after removing the local bundler. Now I am
> getting the following error:
>
> Setting up gitlab (11.5.4+dfsg-1) ...
>
> We trust you have received the usual lecture from the local System
> Administrator. It usually boils dow
OK, made some more progress after removing the local bundler. Now I am
getting the following error:
Setting up gitlab (11.5.4+dfsg-1) ...
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of
On 12/18/18 12:07 PM, Pranith Kumar wrote:
> Thanks for the pointer.
>
> I renamed /var/lib/gems and when I run dpkg configure, I get:
>
> Setting up gitlab (11.5.4+dfsg-1) ...
> Traceback (most recent call last):
> 1: from /usr/local/bin/bundle:23:in `'
> :23:in `load': cannot load such fil
Thanks for the pointer.
I renamed /var/lib/gems and when I run dpkg configure, I get:
Setting up gitlab (11.5.4+dfsg-1) ...
Traceback (most recent call last):
1: from /usr/local/bin/bundle:23:in `'
/usr/local/bin/bundle:23:in `load': cannot load such file --
/usr/share/rubygems-integration/al
On 2018, ഡിസംബർ 18 4:01:01 AM IST, Pranith Kumar wrote:
>After starting nginx manually, the gems issue seems to be back again.
>Any idea on how to clean up gems and let the installation proceed?
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915053#67
It is not a good idea to mix gems
After starting nginx manually, the gems issue seems to be back again.
Any idea on how to clean up gems and let the installation proceed?
Running final rake tasks and tweaks...
Initializing database...
rake aborted!
NoMethodError: undefined method `allow_access_with_scope' for
#
/usr/share/gitlab/l
On 2018, ഡിസംബർ 14 1:22:52 AM IST, Pranith Kumar wrote:
>OK. I manually copied gitlab-debian.conf from /var/lib/gitlab/ to
>/etc/gitlab/ and it was overwritten during the configure step with the
>package maintainers version. It now proceeds past the previous error
>message.
>
>Now, I am seeing
OK. I manually copied gitlab-debian.conf from /var/lib/gitlab/ to
/etc/gitlab/ and it was overwritten during the configure step with the
package maintainers version. It now proceeds past the previous error
message.
Now, I am seeing a new error as follows:
$ sudo dpkg --configure gitlab
Setting up
On 12/14/18 12:58 AM, Pranith Kumar wrote:
> Hmm, I don't understand what you mean by "feel of the installation".
Just so you see the prompt, but you saw it already, so ignore that part.
> The fqdn prompt did show up the first time, but due to other errors
> the installation did not finish then.
Hmm, I don't understand what you mean by "feel of the installation".
The fqdn prompt did show up the first time, but due to other errors
the installation did not finish then.
Now that the other problems are resolved, I need a way to reset the
fqdn setting. Ideally, a purge should remove the confi
On 12/14/18 12:25 AM, Pranith Kumar wrote:
>>
>> Also try changing GITLAB_HOST value in /etc/gitlab/gitlab-debian.conf
>>
>
> That file does not exist for me since gitlab is not configured yet (I think).
>
Try installing first on a virtual machine or an lxc container to get a
feel of the install
On 12/14/18 12:22 AM, Pirate Praveen wrote:
> On Thu, 13 Dec 2018 10:22:12 -0800 Pranith Kumar
> wrote:
>> Purging gitlab does not help. Is there any other package I should
>> purge for the fqdn option to show up?
>> On Thu, Dec 13, 2018 at 2:49 AM Pirate Praveen
>> wrote:
>>>
>>> On 12/13/18
>
> Also try changing GITLAB_HOST value in /etc/gitlab/gitlab-debian.conf
>
That file does not exist for me since gitlab is not configured yet (I think).
--
Pranith
On Thu, 13 Dec 2018 10:22:12 -0800 Pranith Kumar
wrote:
> Purging gitlab does not help. Is there any other package I should
> purge for the fqdn option to show up?
> On Thu, Dec 13, 2018 at 2:49 AM Pirate Praveen
> wrote:
> >
> > On 12/13/18 1:49 PM, Pranith Kumar wrote:
> > > Hmm, how do I chan
On Thu, 13 Dec 2018 10:22:12 -0800 Pranith Kumar
wrote:
> Purging gitlab does not help. Is there any other package I should
> purge for the fqdn option to show up?
gitlab-common
signature.asc
Description: OpenPGP digital signature
Purging gitlab does not help. Is there any other package I should
purge for the fqdn option to show up?
On Thu, Dec 13, 2018 at 2:49 AM Pirate Praveen wrote:
>
> On 12/13/18 1:49 PM, Pranith Kumar wrote:
> > Hmm, how do I change this? Doesn't ask during configuration.
>
> Try sudo dpkg-reconfigure
On 12/13/18 1:49 PM, Pranith Kumar wrote:
> Hmm, how do I change this? Doesn't ask during configuration.
Try sudo dpkg-reconfigure gitlab or purge and reinstall. See the
attached screenshot.
signature.asc
Description: OpenPGP digital signature
On Thu, Dec 13, 2018 at 12:06 AM Pirate Praveen
wrote:
>
> On Wed, 12 Dec 2018 23:52:35 -0800 Pranith Kumar
> wrote:
> > Package: gitlab
> > Version: 11.3.11+dfsg-1
> > Followup-For: Bug #916306
> >
> > Here is the config after purging postgresql and gitlab, gitaly and trying to
> > install gitla
On Wed, 12 Dec 2018 23:52:35 -0800 Pranith Kumar
wrote:
> Package: gitlab
> Version: 11.3.11+dfsg-1
> Followup-For: Bug #916306
>
> Here is the config after purging postgresql and gitlab, gitaly and trying to
> install gitlab.
You are entering wrong value for fqdn.
* gitlab/fqdn: https://gitlab
Package: gitlab
Version: 11.3.11+dfsg-1
Followup-For: Bug #916306
Here is the config after purging postgresql and gitlab, gitaly and trying to
install gitlab.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (450, 'testing'), (50, 'unstable')
Architecture: amd
Purging still does not fix this.
$ sudo apt-get purge gitaly\* gitlab\*
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'gitaly' for glob 'gitaly*'
Note, selecting 'gitlab-shell' for glob 'gitlab*'
Note, selecting 'gitlab-common' for glob 'g
On Wed, 12 Dec 2018 12:49:37 -0800 Pranith Kumar
wrote:
> Package: gitlab
> Version: 11.3.11+dfsg-1
> Severity: normal
>
> Dear Maintainer,
>
> While installing gitlab, I am getting the following error. Please fix.
>
> Setting up gitlab (11.3.11+dfsg-1) ...
> Creating runtime directories for gi
Package: gitlab
Version: 11.3.11+dfsg-1
Severity: normal
Dear Maintainer,
While installing gitlab, I am getting the following error. Please fix.
Setting up gitlab (11.3.11+dfsg-1) ...
Creating runtime directories for gitlab...
Updating file permissions...
Configuring hostname and email...
sed: -
24 matches
Mail list logo
