Calagator mini-code sprints: Wednesday, April 2nd, noon, Backspace && Thursday, April 3rd, 7pm, CubeSpace
Igal Koshevoy
Content-Transfer-Encoding: 7bit
Calagator is an all-volunteer, open-source project to develop a calendar
aggregation system for the Portland technical community. We're making
lots of progress, so please join us in the effort. For further details
about the project, see calagator.org
We've got two mini code sprints coming up, you can come to one or both.
We plan to fix minor bugs, add quick features, manage the ticket queue, etc:
(1) Daywatch crew: Wednesday, April 2nd, noon, Backspace, 115 NW 5th Ave
(2) Nightwatch crew: Thursday, April 3rd, 7pm, CubeSpace, 622 SE Grand
Ave (we'll meet in the conference room behind the front desk)
Everyone is welcome to participate, even if you haven't attended a code
sprint before. Experience with Ruby on Rails and agile development is
helpful, but you're welcome to come even if you're new to these because
this is a great way to learn. You do not have to come to the entire
event, so swing by if you have time.
See you at the code sprint(s)!
-igal
Kevin Scaldeferri
Unfortunately, the last couple weeks have been very busy and I haven't
had any time to spend digging into the code since the last sprint. I
just tried now to get a development instance running on my laptop, but
I'm running into this issue:
% ruby script/server
Missing the Rails gem. Please `gem install -v= rails`, update your
RAILS_GEM_VERSION setting in config/environment.rb for the Rails
version you do have installed, or comment out RAILS_GEM_VERSION to use
the latest version installed.
However, I just 'gem install'ed rails, and have version 2.0.2, which
is what the config file seems to expect.
Maybe someone can help me get this up and running at noon?
-kevin
Igal Koshevoy
Did this error get resolved at the last sprint? And if so, how? And if not, does anyone have any ideas?
I vaguely recall Bryan Stearns mentioning that when he ran "gem update", that it decided to upgrade his copy of Rails from 2.0.2 to some experimental version that wouldn't start. I seem to recall he resolved this by remove the bad packages, and reinstalling the good ones that 2.0.2 includes.
-igal
Kevin Scaldeferri
On Apr 9, 2008, at 2:04 AM, Igal Koshevoy wrote:
> Kevin,
>
> Did this error get resolved at the last sprint? And if so, how? And
> if not, does anyone have any ideas?
>
> I vaguely recall Bryan Stearns mentioning that when he ran "gem
> update", that it decided to upgrade his copy of Rails from 2.0.2 to
> some experimental version that wouldn't start. I seem to recall he
> resolved this by remove the bad packages, and reinstalling the good
> ones that 2.0.2 includes.
>
Yeah, I don't know exactly what happened, but went I tried a second
time with 'gem install -v=2.0.2 rails' it reinstalled a bunch of stuff
and things started working.
-kevin
Bryan Stearns
Glad you got it working again... for what it's worth, the problem I had
was with a rails gem with the version "2.0.2.9029" (or something like
that) - it had that 4-digit subversion revision number on the end, which
confused the snapshot of active_scaffold we have in our vendor/plugins
directory. It looks like someone got rid of that version of the rails
gem, which is probably why no one else is seeing the problem I saw.
...Bryan