Loading Profile...
Recent activity
Subscribe to this feed
Igal Koshevoy replied on September 28, 2009 18:28 to the question "My install is aborting with 4 more pending migrations. How do I proceed?" in Calagator:
The error is telling you that you have another process using this port.
When you run "rake solr:start", it starts the Solr process and runs it in the background.
If you started Solr and still have this process running, you don't need to start it again and will get this error if you try.
If you really do have another process running on that port that's not Calagator's Solr, then you should pull my latest changes and configure a custom port to use in "config/solr.yml".-
Igal Koshevoy replied on September 28, 2009 04:46 to the question "My install is aborting with 4 more pending migrations. How do I proceed?" in Calagator:
The github migration finished sooner than I'd thought. I've pushed my fixes to the official repository on github, please give them a try. -
Igal Koshevoy replied on September 28, 2009 01:05 to the question "My install is aborting with 4 more pending migrations. How do I proceed?" in Calagator:
Good news, I figured out what was going on.
Sorry, it turns that I broke the migrations (only affecting folks setting up a new database) while disabling the "acts_as_versioned" plugin.
Please pull the latest source code from "http://calagator.org/gitbackup/" with my fix. I publishing my change there because the official github.com repository is in the middle of being moved and can't be used. Or, you can wait for github to come back and for me to push the change there, which may take a day or two.
Does this work for you?
PS: Can you join the mailing list (pdx-tech-calendar) and tell us what you're planning to use Calagator for, where, etc? :) -
Igal Koshevoy replied on September 26, 2009 08:45 to the question "My install is aborting with 4 more pending migrations. How do I proceed?" in Calagator:
Thanks for the report.
I can't reproduce your error. If I delete my database and run "rake db:migrate", the process completes successfully.
The Event.create_versioned_table, it's not a built-in Rails command -- it's a special command provided by the "acts_as_versioned" plugin and has been correctly activated.
However, that method provides our old record versioning code, which I've obsoleted in a recent commit and replaced with another versioning system. So if none of the below items help, I'll try pointing you at a branch with the obsoleted "acts_as_versioned" stuff completely removed.
Are you sure you're running the current version out of git, if not try that?
Are you using Ruby 1.8.6, 1.8.7 or REE, if not try those?
Can you just delete your "db/development.sqlite3" file and try rerunning "rake db:migrate"?
If you're still having trouble, can you run "rake db:migrate --trace" and post the results?
