rake fails
Reported by Alex Miller | April 13th, 2010 @ 05:42 AM
See copypasta'd terminal output:
gentoo@a-gentoo /tmp $ hg clone http://bitbucket.org/carbonica/amp/
destination directory: amp
requesting all changes
adding changesets
adding manifests
adding file changes
added 481 changesets with 1643 changes to 466 files
updating to branch default
368 files updated, 0 files merged, 0 files removed, 0 files unresolved
gentoo@a-gentoo /tmp $ cd amp/
gentoo@a-gentoo /tmp/amp $ rake
(in /tmp/amp)
** README.txt is missing or in the wrong format for auto-intuiting.
run `sow blah` and look at its text files
rake aborted!
No such file or directory - /home/gentoo/.rubyforge/user-config.yml
/tmp/amp/Rakefile:24:in `<top (required)>'
(See full trace by running task with --trace)
gentoo@a-gentoo /tmp/amp $ gem list
*** LOCAL GEMS ***
haml (2.2.23)
hoe (2.6.0)
json_pure (1.2.4)
minitest (1.6.0)
rake (0.8.7)
rtfm (0.5.2)
rubyforge (2.0.4)
yard (0.5.4)
Hg's tip here is rev 480:46c53aca151a.
Sidenote: I'm not much of a ruby person, so I apologize if I've missed something large or done something quite stupid.
Comments and changes to this ticket
-
seydar June 30th, 2010 @ 07:12 PM
- State changed from “new” to “invalid”
- Assigned user set to “seydar”
I don't get this issue anymore. Try again?
ALSO: when running tests, make sure you've run rake prepare beforehand at some point.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Rethink Version Control.- http://amp.carboni.ca/
Amp aims to put control of version-control software in your hands as a developer. The entire system is written in Ruby (with C extensions to improve performance), and aims to implement all major VCS's in Ruby. Currently, Mercurial is implemented.
Other features:
Commands are first-class members of the system - drop in an "Ampfile" in your repository, and you can add commands to amp in the same manner you add commands to rake (only with far, far more power!)
Documentation is one of our biggest priorities. We require all methods to be documented - even comically simple ones.
Heavy testing.
Multiple "workflows" - use git's commands to power a mercurial repository.
Add hooks/callbacks in minutes.
Alex Miller