ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Forums » Discuss »

Installation/Update to CP3.3.0 on Windows failing

Added by Carsten Schaudel at 2012-09-11 01:48 pm

Hi together!

I'm successfully running CP 2.2.1 on a Windows/Apache installation.

Now I tried to upgrade to 2.3.0 - and fail (even with a new installation).

I keep getting the error

"No such file or directory - "git" --git-dir="C:/chiliproject/.git" rev-parse --short=9 HEAD"

Either on the step
"bundle exec rake generate_session_store" (when I use the zip-package)

or
"bundle exec rake db:migrate RAILS_ENV=production" (when I got CP via GIT)

Any hints?

Regards

Smartie


Replies (3)

RE: Installation/Update to CP3.3.0 on Windows failing - Added by Felix Schäfer at 2012-09-12 10:11 am

Any reason for sticking to 2.3.0? And do you really mean 2.3.0 or 3.3.0 (your title and post are conflicting).

I seem to remember that we added the short git hash to the ChiliProject version in the UI around then, that might cause problems. Do you install ChiliProject from git? Is git installed on your system and available in the command line?

RE: Installation/Update to CP3.3.0 on Windows failing - Added by Carsten Schaudel at 2012-09-13 01:16 pm

My bad. The title is correct. I tried upgrading from 3.2.2 to 3.3.0 - and fail with the mentioned error.

Git is working fine. I tried to install from GIT aswell, but with the same issue.
And what should I say, the errormessage even seems right, since there is neither a file nor a folder named "git" in c:/chiliproject/.git (this path is existing).

RE: Installation/Update to CP3.3.0 on Windows failing - Added by Felix Schäfer at 2012-09-13 03:43 pm

No, the error says that it tries to execute "git" --git-dir="C:/chiliproject/.git" rev-parse --short=9 HEAD, i.e. calling the git executable with some options.

Just for the sake of trying to narrow down the problem: could you try to rename the .git folder and see if stuff works? Don't forget to rename it "back" after that so as not to completely freak out git.

(1-3/3)