deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dies Koper (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-362) can't start DC with ./bin/deltacloudd, need to add "ruby"
Date Sat, 10 Nov 2012 00:09:19 GMT


Dies Koper commented on DTACLOUD-362:

Found it!
My code is checked out on Windows, I'm using it from CentOS by mounting the deltacloud directory.
deltacloudd shows DOS newlines on CentOS and that seems to be causing the issue.
If I do a tr -d '\r' < deltacloudd >, the latter file works.

How to fix it? Not sure on git, but deltacloudd (being a unix script) should never be checked
out with DOS newlines, no matter whether I'm checking out on Linux or Windows.
With svn there are file options to ensure newlines are not changed on particular files. How
about git?

> can't start DC with ./bin/deltacloudd, need to add "ruby"
> ---------------------------------------------------------
>                 Key: DTACLOUD-362
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Website
>         Environment: CentOS 6.2 (and Win 7)
>            Reporter: Dies Koper
>            Priority: Minor
> I can't start DC with ./bin/deltacloudd:
> [root@localhost server]# ./bin/deltacloudd -i mock
> : No such file or directory
> [root@localhost server]# ls
> 0001-fgcp-activate-new-ip-as-soon-as-allocated.patch  deltacloud-core.gemspec  LICENSE
 Rakefile   tests
> bin                                                   Gemfile                  log  tmp
> config                                                Gemfile.lock             NOTICE
  support    views
>                                             lib                      public
> [root@localhost server]# pwd
> /mnt/hgfs/deltacloud/server
> but "ruby ./bin/deltacloudd" does work.
> See also and note:
>  $ /usr/bin/env ruby --version
> ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message