Hi Robert,
I've removed all the git:// urls from the app, now gems and submodules use
https protocol. Ce-installer still installs 3.0.0, we are going to release
another version and update the ce-installer in couple of days, but if you
don't want to wait, you could try installing Gitorious version with the fix
by setting '30d878caa18278d2af85211977e9a8ad91b3e5f5' as gitorious::version
in ce-installer/manifests/nodes.pp

Cheers,
Pawel


On Fri, Dec 13, 2013 at 11:04 PM, Robert Putt <[email protected]> wrote:

> On Friday, 13 December 2013 19:22:08 UTC, Robert Putt  wrote:
> > Hi All,
> >
> >
> >
> > Following the previous post regarding installation issues with CentOS
> 6.4 and 6.5 and the SSL issue being resolved with Ruby I am still running
> into issues with the de-installer script. Hopefully you can help.
> >
> >
> >
> > Just to clarify, I am installing this on a newly installed CentOS 6.4
> host with a minimal install with no previous installation of puppet or ruby.
> >
> >
> >
> > So far I have installed git from yum, cloned the installer as per the
> docs at getgitorious and ran the install script… All appears good until the
> puppet recipe starts installing and I see a lot of the following outputs.
> >
> >
> >
> >
> >
> >
> >
> > Error:
> /Stage[main]/Gitorious::Core/Exec[init_gitorious_submodules]/returns:
> change from notrun to 0 failed: env GIT_SSL_NO_VERIFY=true git submodule
> update --init --recursive returned 1 instead of one of [0]
> >
> > Error: sh -c 'export GIT_SSL_NO_VERIFY=true && cd /var/www/gitorious/app
> && bundle install --deployment --without development test && env
> GIT_SSL_NO_VERIFY=true git submodule update --init --recursive && chown -R
> git:git db vendor && bin/rake db:migrate && touch
> /tmp/post_version_upgrade_done' returned 1 instead of one of [0]
> >
> > Error:
> /Stage[main]//Node[gitorious-ce]/Gitorious::Version[942b6ef1b16efcb10745cf75a0c377e13ee77875]/Exec[post_version_upgrade]/returns:
> change from notrun to 0 failed: sh -c 'export GIT_SSL_NO_VERIFY=true && cd
> /var/www/gitorious/app && bundle install --deployment --without development
> test && env GIT_SSL_NO_VERIFY=true git submodule update --init --recursive
> && chown -R git:git db vendor && bin/rake db:migrate && touch
> /tmp/post_version_upgrade_done' returned 1 instead of one of [0]
> >
> >
> >
> >
> >
> >
> >
> > After 15 attempts it gives up. If you would like some detail from the
> puppet log let me know.
> >
> >
> >
> > I am confused as to why this isn't working. Please can you guys offer an
> insight into what I am doing wrong.
> >
> >
> >
> > Best Regards,
> >
> >
> >
> > Rob
>
>
> Hi,
>
> I have worked out the problem here, during the puppet recipe it tries to
> clone from github for eve using git://. Unfortunately within our labs port
> 9418 is blocked to the outside world, leaving us with just the ability to
> http or ssh clone.
>
> This poses a bit of a problem because it means I cannot install gitorious,
> and they will not agree to open this port.
>
> I have tried a recursive grep on the installation scripts in ce-installer
> to try and see where this is referenced to do a cheeky swap to http
> cloning. Although I cannot find it, I can only assume this script is pulled
> dynamically as part of the recipe.
>
> Please can you advise on how I can install gitorious without access to the
> outside world via port 9418?
>
> Best Regards,
>
> Rob
>
> --
> --
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Gitorious" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
-- 
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]

--- 
You received this message because you are subscribed to the Google Groups 
"Gitorious" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to