ImageMagick Error on commit (OSX) about lolcommits HOT 109 CLOSED

Hmm... does /Users/Burton/.lolcommits/skeleton/tmp_snapshot.jpg actually exist? If not, it's not saving the image properly for some reason. Could be a permissions issue?

from lolcommits.

Well, .lolcommits/skeleton exists, but there is no tmp_snapshot.jpg inside. Shouldn't it create it with the proper permissions when I run lolcommits --enabled?

from lolcommits.

It just does mkdir so I assume it would be normal user permissions. Do you have permission to write/read in that folder normally?

from lolcommits.

I recursively made the entire directory writable. I've always had
permission to create folders in that directory as well. I also created the
tmp_snapshot.jpg file but that didn't work either. Any thoughts?

Jason Burton

On Tue, Jun 5, 2012 at 7:30 AM, Adnan <
[email protected]

wrote:

It just does mkdir so I assume it would be normal user permissions. Do
you have permission to write/read in that folder normally?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Try installing imagesnap via homebrew and run imagesnap ~/.lolcommits/skeleton/tmp_snapshot.jpg. What output do you get?

from lolcommits.

It took a snapshot of me, and stored it in the lolcommits/skeleton/ folder.
I then tried doing lolcommits normally, still no go.

Jason Burton

On Tue, Jun 5, 2012 at 9:26 AM, Adnan <
[email protected]

wrote:

Try installing imagesnap via homebrew and run imagesnap ~/.lolcommits/skeleton/tmp_snapshot.jpg. What output do you get?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

I think the problem lies with rmagick then. What version of Ruby and rmagick are you using? Looks like you're using Ruby 1.8. Rmagick 2.0 doesn't support Ruby < 1.8.5.

from lolcommits.

Okay, what's the best way to update to the latest ruby? Can I use homebrew
to do that?

Jason Burton

On Tue, Jun 5, 2012 at 9:36 AM, Adnan <
[email protected]

wrote:

I think the problem lies with rmagick then. What version of Ruby and
rmagick are you using? Looks like you're using Ruby 1.8. Rmagick 2.0
doesn't support Ruby < 1.8.5.

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

I'm guessing you're using your system version of Ruby? In this case homebrew would be the simplest way to get 1.9 :). You will have to reinstall lolcommits once you've updated.

from lolcommits.

okay thanks. I will give it a try!
Jason Burton

On Tue, Jun 5, 2012 at 9:40 AM, Adnan <
[email protected]

wrote:

I'm guessing you're using your system version of Ruby? In this case
homebrew would be the simplest way to get 1.9 :). You will have to
reinstall lolcommits once you've updated.

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Is there any special way I should reinstall lolcommits? Or do I just go to
the site and follow the instructions all over again? Hehe

Jason Burton

On Tue, Jun 5, 2012 at 9:42 AM, Jason Burton [email protected] wrote:

okay thanks. I will give it a try!
Jason Burton

On Tue, Jun 5, 2012 at 9:40 AM, Adnan <
[email protected]

wrote:

I'm guessing you're using your system version of Ruby? In this case
homebrew would be the simplest way to get 1.9 :). You will have to
reinstall lolcommits once you've updated.

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

You should just be able to do gem install lolcommits since you have imagemagick installed already. This will reinstall rmagick and lolcommits for you.

from lolcommits.

When I run gem install lolcommits, it says I do not have permission to
write to Library/Ruby/Gems/1.8 etc But I cannot change those permissions?

Jason Burton

On Tue, Jun 5, 2012 at 9:45 AM, Adnan <
[email protected]

wrote:

You should just be able to do gem install lolcommits since you have
imagemagick installed already. This will reinstall rmagick and lolcommits
for you.

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

What's the output of echo $PATH?

from lolcommits.

/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/git/bin

Jason Burton

On Tue, Jun 5, 2012 at 10:09 AM, Adnan <
[email protected]

wrote:

What's the output of echo $PATH?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Hmm, did your homebrew installation go well? It should have added /usr/local/Cellar/ruby... to your path. Maybe try quitting terminal and reopening and running echo $PATH again?

from lolcommits.

Same thing. When I did the homebrew install, it kept getting me to install
different things. Then I ran brew doctor and it said everything was fine

Jason Burton

On Tue, Jun 5, 2012 at 10:11 AM, Adnan <
[email protected]

wrote:

Hmm, did your homebrew installation go well? It should have added
/usr/local/Cellar/ruby... to your path. Maybe try quitting terminal and
reopening and running echo $PATH again?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Does /usr/local/Cellar/ruby/1.9.3-p125/ exist? If it does add /usr/local/Cellar/ruby/1.9.3-p125/bin to the front of your path. If it doesn't reinstall ruby in homebrew.

from lolcommits.

1.9.3-p194 exists not 1.9.3-p125. Is that okay? Also, how do I add that bit
to my path? (Sorry, I'm a newb)

Jason Burton

On Tue, Jun 5, 2012 at 10:15 AM, Adnan <
[email protected]

wrote:

Does /usr/local/Cellar/ruby/1.9.3-p125/ exist? If it does add
/usr/local/Cellar/ruby/1.9.3-p125/bin to the front of your path. If it
doesn't reinstall ruby in homebrew.

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Yeah that's fine. You need to edit ~/.profile and add export PATH=/usr/local/Cellar/ruby/1.9.3-p194/bin:/usr/local/bin:$PATH. Then quit and reload terminal and run echo $PATH to see if it's been added. If it has you should be good to go!

from lolcommits.

Okay, so I did everything we talked about and I am still getting an error,
but! we are making progress.

*** Preserving this moment in history.
/Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:147:in
annotate': unable to read font /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/../fonts/Impact.ttf' @
error/annotate.c/RenderFreetype/1120: (null)' (Magick::ImageMagickError) from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:147:in capture'
from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:102:in
do_capture' from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:186 from /usr/bin/lolcommits:19:inload'
from /usr/bin/lolcommits:19

Jason Burton

On Tue, Jun 5, 2012 at 10:21 AM, Adnan <
[email protected]

wrote:

Yeah that's fine. You need to edit ~/.profile and add export PATH=/usr/local/Cellar/ruby/1.9.3-p194/bin:/usr/local/bin:$PATH. Then quit
and reload terminal and run echo $PATH to see if it's been added. If it
has you should be good to go!

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Okay that's really strange, it's still going back to your system version. What's in /usr/local/Cellar/ruby/1.9.3-p194/bin:/usr/local/bin?

from lolcommits.

There is no usr/local/bin inside that directory.
Jason Burton

On Tue, Jun 5, 2012 at 11:01 AM, Adnan <
[email protected]

wrote:

Okay that's really strange, it's still going back to your system version.
What's in /usr/local/Cellar/ruby/1.9.3-p194/bin:/usr/local/bin?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Sorry, my mistake I copied and pasted. I just realised that you shouldn't need to add the whole directory there as homebrew copies the stuff into /usr/local/bin. Can you try the following things?

Open up ~/.profile and remove the line we added earlier.

Navigate to /usr/local/Cellar/ruby/1.9.3-p194/bin and tell me what files are in there.

Run ruby -v and tell me the output.

from lolcommits.

After the first one can you quit and reopen terminal too to reset your path.

from lolcommits.

here are the directories that are in there: erb, irb, lolcommits, rdoc,
ruby, gem, launchy, rake, ri , testrb

ruby -v outputs : ruby 1.8.7 (2011-12-28 patchlevel 357)
[universal-darwin11.0]

Jason Burton

On Tue, Jun 5, 2012 at 11:09 AM, Adnan <
[email protected]

wrote:

After the first one can you quit and reopen terminal too to reset your
path.

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Okay and what's the output of which ruby?

from lolcommits.

/usr/bin/ruby

Jason Burton

On Tue, Jun 5, 2012 at 11:19 AM, Adnan <
[email protected]

wrote:

Okay and what's the output of which ruby?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Okay, we need to move /usr/local/bin to the front of the path. So open up ~/.profile again and add export PATH=/usr/local/bin:$PATH. Sorry about going in circles here! Then quit and reopen and tell me the output of ruby -v, which ruby and try lolcommits -c --test

from lolcommits.

ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin11.4.0]

/usr/local/bin/ruby

*** capturing in test mode
*** Preserving this moment in history.
/Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in read': unable to open image /Users/jasonburton/.lolcommits/test/tmp_snapshot.jpg': No such file or
directory @ error/blob.c/OpenBlob/2614 (Magick::ImageMagickError)
from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in
initialize' from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in each'
from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in
initialize' from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in new'
from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in
capture' from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:100:in do_capture'
from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:186
from /usr/bin/lolcommits:19:in `load'
from /usr/bin/lolcommits:19

Jason Burton

On Tue, Jun 5, 2012 at 11:25 AM, Adnan <
[email protected]

wrote:

Okay, we need to move /usr/local/bin to the front of the path. So open
up ~/.profile again and add export PATH=/usr/local/bin:$PATH. Sorry
about going in circles here! Then quit and reopen and tell me the output of
ruby -v, which ruby and try lolcommits -c --test

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Hmm, I don't understand why it's accessing the gem files from that directory. What's the output of gem environment?

from lolcommits.

RubyGems Environment:

• RUBYGEMS VERSION: 1.8.23
• RUBY VERSION: 1.9.3 (2012-04-20 patchlevel 194) [x86_64-darwin11.4.0]
• INSTALLATION DIRECTORY:
  /usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1
• RUBY EXECUTABLE: /usr/local/Cellar/ruby/1.9.3-p194/bin/ruby
• EXECUTABLE DIRECTORY: /usr/local/Cellar/ruby/1.9.3-p194/bin
• RUBYGEMS PLATFORMS:
  • ruby
  • x86_64-darwin-11
• GEM PATHS:
  • /usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1
  • /Users/jasonburton/.gem/ruby/1.9.1
• GEM CONFIGURATION:
  • :update_sources => true
  • :verbose => true
  • :benchmark => false
  • :backtrace => false
  • :bulk_threshold => 1000
• REMOTE SOURCES:
  • http://rubygems.org/

Jason Burton

On Tue, Jun 5, 2012 at 11:33 AM, Adnan <
[email protected]

wrote:

Hmm, I don't understand why it's accessing the gem files from that
directory. What's the output of gem environment?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Yeah it should be looking for the gems in /usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1 not in /Library/Ruby/Gems/1.8/gems/. I can't think why it's doing that. What's the output of which lolcommits?

from lolcommits.

/usr/bin/lolcommits

Jason Burton

On Tue, Jun 5, 2012 at 11:37 AM, Adnan <
[email protected]

wrote:

Yeah it should be looking for the gems in
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1 not in
/Library/Ruby/Gems/1.8/gems/. I can't think why it's doing that. What's
the output of which lolcommits?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Yeah that's not right. Try installing lolcommits again?

from lolcommits.

Okay, do I need to do anything to uninstall it? Or just go for a new install

Jason Burton

On Tue, Jun 5, 2012 at 11:40 AM, Adnan <
[email protected]

wrote:

Yeah that's not right. Try installing lolcommits again?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

I can only think that it's not actually installed in ruby 1.9, so it falls back to 1.8. You can verify this by seeing what's in /usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems.

from lolcommits.

Okay I will reinstall it and see what happens

Jason Burton

On Tue, Jun 5, 2012 at 11:47 AM, Adnan <
[email protected]

wrote:

I can only think that it's not actually installed in ruby 1.9, so it falls
back to 1.8. You can verify this by seeing what's in
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems.

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Here is what is in that directory :

addressable-2.2.8 launchy-2.1.0 rdoc-3.9.4
choice-0.1.6 lolcommits-0.1.4 rmagick-2.13.1
git-1.2.5 rake-0.9.2.2

Also I tried gem install lolcommits and it only ouputted this:

Successfully installed lolcommits-0.1.4
1 gem installed
Installing ri documentation for lolcommits-0.1.4...
Installing RDoc documentation for lolcommits-0.1.4...

Which Iam assuming worked, but I feel like their should have been more
output?

Jason Burton

On Tue, Jun 5, 2012 at 11:49 AM, Jason Burton [email protected]:

Okay I will reinstall it and see what happens

Jason Burton

On Tue, Jun 5, 2012 at 11:47 AM, Adnan <
[email protected]

wrote:

I can only think that it's not actually installed in ruby 1.9, so it
falls back to 1.8. You can verify this by seeing what's in
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems.

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Hmm, it probably just reinstalled lolcommits and didn't need to worry about the dependencies since they were already installed. What happens if you do which lolcommits now?

from lolcommits.

/usr/bin/lolcommits

Jason Burton

On Tue, Jun 5, 2012 at 11:54 AM, Adnan <
[email protected]

wrote:

Hmm, it probably just reinstalled lolcommits and didn't need to worry
about the dependencies since they were already installed. What happens if
you do which lolcommits now?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

That's really confusing. Just checked on my file system, I think I was probably wrong again, you do need to add /usr/local/Cellar/ruby/1.9.3-p194/bin/ to your path because that's where all the gems are. Sorry! Just replace the line in /.profile to export PATH=/usr/local/bin:/usr/local/Cellar/ruby/1.9.3-p194/bin/:$PATH.

We really are going in circles here it seems, though. However, we know that for some reason it's trying to access rmagick in your 1.8 installation instead of your new installation. Hopefully we'll get there though!

from lolcommits.

Now what do I do? lol.. (really, thanks so much for taking the time to help
me out here)
Jason Burton

On Tue, Jun 5, 2012 at 12:02 PM, Adnan <
[email protected]

wrote:

That's really confusing. Just checked on my file system, I think I was
probably wrong again, you do need to add
/usr/local/Cellar/ruby/1.9.3-p194/bin/ to your path because that's where
all the gems are. Sorry! Just replace the line in /.profile to export PATH=/usr/local/bin:/usr/local/Cellar/ruby/1.9.3-p194/bin/:$PATH.

We really are going in circles here it seems, though. However, we know
that for some reason it's trying to access rmagick in your 1.8 installation
instead of your new installation. Hopefully we'll get there though!

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Quit and reopen terminal and check the output of which lolcommits, if it's coming from /usr/local/Cellar/ruby/1.9.3-p194/bin/lolcommits what happens if you do lolcommits -c --test?

from lolcommits.

/usr/local/Cellar/ruby/1.9.3-p194/bin//lolcommits
Jason Burton

On Tue, Jun 5, 2012 at 12:09 PM, Adnan <
[email protected]

wrote:

Quit and reopen terminal and check the output of which lolcommits, if
it's coming from /usr/local/Cellar/ruby/1.9.3-p194/bin/lolcommits what
happens if you do lolcommits -c --test?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

is there a reason there's two slashes at the end of that?

Jason Burton

On Tue, Jun 5, 2012 at 12:11 PM, Jason Burton [email protected]:

/usr/local/Cellar/ruby/1.9.3-p194/bin//lolcommits
Jason Burton

On Tue, Jun 5, 2012 at 12:09 PM, Adnan <
[email protected]

wrote:

Quit and reopen terminal and check the output of which lolcommits, if
it's coming from /usr/local/Cellar/ruby/1.9.3-p194/bin/lolcommits what
happens if you do lolcommits -c --test?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Yeah that was my bad, in your .profile there's a slash before the last semicolon which isn't supposed to be there. Nevertheless it should work, but take it out if you want. What happens if you do lolcommits -c --test now?

from lolcommits.

It worked! Thanks so much!

There's no way I would have been able to get this working without you.
Thanks!

Jason Burton

On Tue, Jun 5, 2012 at 12:13 PM, Adnan <
[email protected]

wrote:

Yeah that was my bad, in your .profile there's a slash before the last
semicolon which isn't supposed to be there. Nevertheless it should work,
but take it out if you want. What happens if you do lolcommits -c --test
now?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Brilliant :D! No problem. Will need to add a note in the readme to say it doesn't work with Ruby 1.8. Have fun :).

from lolcommits.

Nice! I'm gonna be setting this up for the whole office.
Jason Burton

On Tue, Jun 5, 2012 at 12:20 PM, Adnan <
[email protected]

wrote:

Brilliant :D! No problem. Will need to add a note in the readme to say it
doesn't work with Ruby 1.8. Have fun :).

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Wait a second here...

I'm still getting an error? Only the test works...

*** Preserving this moment in history.
/Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in read': unable to open image /Users/jasonburton/.lolcommits/journeyman/tmp_snapshot.jpg': No such file
or directory @ error/blob.c/OpenBlob/2614 (Magick::ImageMagickError)
from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in
initialize' from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in each'
from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in
initialize' from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in new'
from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in
capture' from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:102:in do_capture'
from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:186
from /usr/bin/lolcommits:19:in `load'
from /usr/bin/lolcommits:19

Jason Burton

On Tue, Jun 5, 2012 at 1:02 PM, Jason Burton [email protected] wrote:

Nice! I'm gonna be setting this up for the whole office.
Jason Burton

On Tue, Jun 5, 2012 at 12:20 PM, Adnan <
[email protected]

wrote:

Brilliant :D! No problem. Will need to add a note in the readme to say it
doesn't work with Ruby 1.8. Have fun :).

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Ah damn we're back to square one... it seems to be going for the rmagick installation in 1.8 again. Try these steps:

export PATH=/usr/bin:$PATH (in command line NOT .profile)
ruby -v and make sure it's ruby 1.8
gem uninstall lolcommits
gem uninstall rmagick

Then quit and reopen terminal and try lolcommiting again?

from lolcommits.

I got this far and got this:

gem uninstall lolcommits
Remove executables:
lolcommits

in addition to the gem? [Yn] Y
ERROR: While executing gem ... (Gem::FilePermissionError)
You don't have write permissions into the /usr/bin directory.

Jason Burton

On Tue, Jun 5, 2012 at 1:24 PM, Adnan <
[email protected]

wrote:

Ah damn we're back to square one... it seems to be going for the rmagick
installation in 1.8 again. Try these steps:

export PATH=/usr/bin:$PATH (in command line NOT .profile)
ruby -v and make sure it's ruby 1.8
gem uninstall lolcommits
gem uninstall rmagick

Then quit and reopen terminal and try lolcommiting again?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Should I have just said n?
Jason Burton

On Tue, Jun 5, 2012 at 1:47 PM, Jason Burton [email protected] wrote:

I got this far and got this:

gem uninstall lolcommits
Remove executables:
lolcommits

in addition to the gem? [Yn] Y
ERROR: While executing gem ... (Gem::FilePermissionError)
You don't have write permissions into the /usr/bin directory.

Jason Burton

On Tue, Jun 5, 2012 at 1:24 PM, Adnan <
[email protected]

wrote:

Ah damn we're back to square one... it seems to be going for the rmagick
installation in 1.8 again. Try these steps:

export PATH=/usr/bin:$PATH (in command line NOT .profile)
ruby -v and make sure it's ruby 1.8
gem uninstall lolcommits
gem uninstall rmagick

Then quit and reopen terminal and try lolcommiting again?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Add sudo to the front of those commands i.e. sudo gem uninstall lolcommits.

from lolcommits.

IT WORKED! Okay...I have one final question lol....

I am going to be putting this on all the computers in the office, so...what
would be the list of commands I need to run in order to get this working? I
know we went around in circles a few times so I"m not sure if there's a
good order in which to run these commands?

Jason Burton

On Tue, Jun 5, 2012 at 1:51 PM, Adnan <
[email protected]

wrote:

Add sudo to the front of those commands i.e. sudo gem uninstall lolcommits.

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Awesome. Well what seems to have caused the problem in the first place is installing lolcommits in 1.8 to start with. So you'd want to avoid that. If its already been done just uninstall using the steps above.

1. brew install ruby
2. brew install imagemagick --from-source
3. Open up ~/.profile and add this line: export PATH=/usr/local/bin:/usr/local/Cellar/ruby/1.9.3-p194/bin/:$PATH (at this point run ruby -v and convert --version to check if ruby and imagemagick installations are ok.
4. gem install lolcommits

And you should be good to go!

from lolcommits.

Okay, I tried executing those commands on a friends computer and I was
getting this again:

*** Preserving this moment in history.

/Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in read': unable to open image /Users/nicktassone/.lolcommits/Southwest/tmp_snapshot.jpg': No such file
or directory @ error/blob.c/OpenBlob/2614 (Magick::ImageMagickError)

from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in
`initialize'

from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in
`each'

from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in
`initialize'

from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in
`new'

from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in
`capture'

from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:102:in
`do_capture'

from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:186

from /usr/bin/lolcommits:19:in `load'

from /usr/bin/lolcommits:19

[master 00a1660] hello its me nick

7 files changed, 558 insertions(+), 39 deletions(-)

create mode 100644
motherhouse/wp-content/themes/motherhouse/img/slideshow-arrows.png

rewrite motherhouse/wp-content/themes/motherhouse/index.php (63%)

He has homebrew installed, and tried those commands.
Jason Burton

On Tue, Jun 5, 2012 at 2:02 PM, Adnan <
[email protected]

wrote:

Awesome. Well what seems to have caused the problem in the first place is
installing lolcommits in 1.8 to start with. So you'd want to avoid that. If
its already been done just uninstall using the steps above.

1. brew install ruby
2. brew install imagemagick --from-source
3. Open up ~/.profile and add this line: export PATH=/usr/local/bin:/usr/local/Cellar/ruby/1.9.3-p194/bin/:$PATH (at this
   point run ruby -v and convert --version to check if ruby and
   imagemagick installations are ok.
4. gem install lolcommits

And you should be good to go!

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Looks like he's installed it in 1.8 again. He needs to uninstall it in 1.8 using these commands #53 (comment) and then ensure he's on 1.9 then reinstall.

from lolcommits.

Okay now he's getting this:

*** Preserving this moment in history.

/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in
read': unable to open image /Users/nicktassone/.lolcommits/Southwest/tmp_snapshot.jpg': No such file
or directory @ error/blob.c/OpenBlob/2614 (Magick::ImageMagickError)

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in
`block in initialize'

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in
`each'

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in
`initialize'

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in
`new'

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in
`capture'

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/lolcommits-0.1.4/bin/lolcommits:102:in
`do_capture'

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/lolcommits-0.1.4/bin/lolcommits:186:in
`<top (required)>'

from /usr/local/Cellar/ruby/1.9.3-p194/bin/lolcommits:23:in `load'

from /usr/local/Cellar/ruby/1.9.3-p194/bin/lolcommits:23:in `

[master cc6bccd] lol i'm committin'

1 files changed, 1 insertions(+), 1 deletions(-)

I can feel we're close on this one!
Jason Burton

On Tue, Jun 5, 2012 at 2:25 PM, Adnan <
[email protected]

wrote:

Looks like he's installed it in 1.8 again. He needs to uninstall it in 1.8
using these commands
#53 (comment) and
then ensure he's on 1.9 then reinstall.

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

He uninstalled lolcommits and rmagick, then he installed lolcommits again.

Jason Burton

On Tue, Jun 5, 2012 at 2:41 PM, Jason Burton [email protected] wrote:

Okay now he's getting this:

*** Preserving this moment in history.

/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in
read': unable to open image /Users/nicktassone/.lolcommits/Southwest/tmp_snapshot.jpg': No such file
or directory @ error/blob.c/OpenBlob/2614 (Magick::ImageMagickError)

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in
`block in initialize'

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in
`each'

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in
`initialize'

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in
`new'

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in
`capture'

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/lolcommits-0.1.4/bin/lolcommits:102:in
`do_capture'

from
/usr/local/Cellar/ruby/1.9.3-p194/lib/ruby/gems/1.9.1/gems/lolcommits-0.1.4/bin/lolcommits:186:in
`<top (required)>'

from /usr/local/Cellar/ruby/1.9.3-p194/bin/lolcommits:23:in `load'

from /usr/local/Cellar/ruby/1.9.3-p194/bin/lolcommits:23:in `

'

[master cc6bccd] lol i'm committin'

1 files changed, 1 insertions(+), 1 deletions(-)

I can feel we're close on this one!
Jason Burton

On Tue, Jun 5, 2012 at 2:25 PM, Adnan <
[email protected]

wrote:

Looks like he's installed it in 1.8 again. He needs to uninstall it in
1.8 using these commands
#53 (comment) and
then ensure he's on 1.9 then reinstall.

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Stuck on this one I'm afraid! Does lolcommits -c --test work?

from lolcommits.

He gets the same error.

Jason Burton

On Tue, Jun 5, 2012 at 2:44 PM, Adnan <
[email protected]

wrote:

Stuck on this one I'm afraid! Does lolcommits -c --test work?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Hmm... I really have no idea here... Does the directory exist, is it writeable etc?

from lolcommits.

Perhaps he needs to make it writable like I did way back...let me try...

Jason Burton

On Tue, Jun 5, 2012 at 2:51 PM, Adnan <
[email protected]

wrote:

Hmm... I really have no idea here... Does the directory exist, is it
writeable etc?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Okay, so we changed permissions and now the error is the same thing except
it says "empty input file" and its referring to tmp_snapshot.jpg
so we gem unistall lolcommits and then reinstall it and same error: Empty
input file

Jason Burton

On Tue, Jun 5, 2012 at 2:53 PM, Jason Burton [email protected] wrote:

Perhaps he needs to make it writable like I did way back...let me try...

Jason Burton

On Tue, Jun 5, 2012 at 2:51 PM, Adnan <
[email protected]

wrote:

Hmm... I really have no idea here... Does the directory exist, is it
writeable etc?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

If there is a tmp_snapshot.jpg in the folder, delete it and try again?

On Tuesday, 5 June 2012 at 18:58, Jason Burton wrote:

Okay, so we changed permissions and now the error is the same thing except
it says "empty input file" and its referring to tmp_snapshot.jpg
so we gem unistall lolcommits and then reinstall it and same error: Empty
input file

Jason Burton

On Tue, Jun 5, 2012 at 2:53 PM, Jason Burton <[email protected] (mailto:[email protected])> wrote:

Perhaps he needs to make it writable like I did way back...let me try...

Jason Burton

On Tue, Jun 5, 2012 at 2:51 PM, Adnan <
[email protected] (mailto:[email protected])

wrote:

Hmm... I really have no idea here... Does the directory exist, is it
writeable etc?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

He deleted it and it came up with the same old "Unable to open file" file
or directory doesn't exist, etc.

Jason Burton

On Tue, Jun 5, 2012 at 2:59 PM, Adnan <
[email protected]

wrote:

If there is a tmp_snapshot.jpg in the folder, delete it and try again?

On Tuesday, 5 June 2012 at 18:58, Jason Burton wrote:

Okay, so we changed permissions and now the error is the same thing
except
it says "empty input file" and its referring to tmp_snapshot.jpg
so we gem unistall lolcommits and then reinstall it and same error: Empty
input file

Jason Burton

On Tue, Jun 5, 2012 at 2:53 PM, Jason Burton <[email protected](mailto:
[email protected])> wrote:

Perhaps he needs to make it writable like I did way back...let me
try...

Jason Burton

On Tue, Jun 5, 2012 at 2:51 PM, Adnan <
[email protected] (mailto:[email protected])

wrote:

Hmm... I really have no idea here... Does the directory exist, is it
writeable etc?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Maybe imagesnap isn't saving the image properly. Try installing imagesnap with homebrew and see if it saves in that directory properly?

On Tuesday, 5 June 2012 at 19:02, Jason Burton wrote:

He deleted it and it came up with the same old "Unable to open file" file
or directory doesn't exist, etc.

Jason Burton

On Tue, Jun 5, 2012 at 2:59 PM, Adnan <
[email protected] (mailto:[email protected])

wrote:

If there is a tmp_snapshot.jpg in the folder, delete it and try again?

On Tuesday, 5 June 2012 at 18:58, Jason Burton wrote:

Okay, so we changed permissions and now the error is the same thing
except
it says "empty input file" and its referring to tmp_snapshot.jpg
so we gem unistall lolcommits and then reinstall it and same error: Empty
input file

Jason Burton

On Tue, Jun 5, 2012 at 2:53 PM, Jason Burton <[email protected] (mailto:[email protected])(mailto:
[email protected] (mailto:[email protected]))> wrote:

Perhaps he needs to make it writable like I did way back...let me
try...

Jason Burton

On Tue, Jun 5, 2012 at 2:51 PM, Adnan <
[email protected] (mailto:[email protected])

wrote:

Hmm... I really have no idea here... Does the directory exist, is it
writeable etc?

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Okay, we're going to imagesnap route, but we just found out homebrew is not
ready. He needs the latest xcode first. so that might be awhile. Wish us
luck! Thanks for all the help too!
Jason Burton

On Tue, Jun 5, 2012 at 3:04 PM, Adnan <
[email protected]

wrote:

Maybe imagesnap isn't saving the image properly. Try installing imagesnap
with homebrew and see if it saves in that directory properly?

On Tuesday, 5 June 2012 at 19:02, Jason Burton wrote:

He deleted it and it came up with the same old "Unable to open file" file
or directory doesn't exist, etc.

Jason Burton

On Tue, Jun 5, 2012 at 2:59 PM, Adnan <
[email protected] (mailto:[email protected])

wrote:

If there is a tmp_snapshot.jpg in the folder, delete it and try again?

On Tuesday, 5 June 2012 at 18:58, Jason Burton wrote:

Okay, so we changed permissions and now the error is the same thing
except
it says "empty input file" and its referring to tmp_snapshot.jpg
so we gem unistall lolcommits and then reinstall it and same error:
Empty
input file

Jason Burton

On Tue, Jun 5, 2012 at 2:53 PM, Jason Burton <[email protected](mailto:
[email protected])(mailto:
[email protected] (mailto:[email protected]))> wrote:

Perhaps he needs to make it writable like I did way back...let me
try...

Jason Burton

On Tue, Jun 5, 2012 at 2:51 PM, Adnan <
[email protected] (mailto:[email protected])

wrote:

Hmm... I really have no idea here... Does the directory exist,
is it
writeable etc?

---

Reply to this email directly or view it on GitHub:

#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Haha, good luck, and no probs!

On Tuesday, 5 June 2012 at 19:10, Jason Burton wrote:

Okay, we're going to imagesnap route, but we just found out homebrew is not
ready. He needs the latest xcode first. so that might be awhile. Wish us
luck! Thanks for all the help too!
Jason Burton

On Tue, Jun 5, 2012 at 3:04 PM, Adnan <
[email protected] (mailto:[email protected])

wrote:

Maybe imagesnap isn't saving the image properly. Try installing imagesnap
with homebrew and see if it saves in that directory properly?

On Tuesday, 5 June 2012 at 19:02, Jason Burton wrote:

He deleted it and it came up with the same old "Unable to open file" file
or directory doesn't exist, etc.

Jason Burton

On Tue, Jun 5, 2012 at 2:59 PM, Adnan <
[email protected] (mailto:[email protected])

wrote:

If there is a tmp_snapshot.jpg in the folder, delete it and try again?

On Tuesday, 5 June 2012 at 18:58, Jason Burton wrote:

Okay, so we changed permissions and now the error is the same thing
except
it says "empty input file" and its referring to tmp_snapshot.jpg
so we gem unistall lolcommits and then reinstall it and same error:

Empty

input file

Jason Burton

On Tue, Jun 5, 2012 at 2:53 PM, Jason Burton <[email protected] (mailto:[email protected])(mailto:
[email protected] (mailto:[email protected]))(mailto:
[email protected] (mailto:[email protected]))> wrote:

Perhaps he needs to make it writable like I did way back...let me
try...

Jason Burton

On Tue, Jun 5, 2012 at 2:51 PM, Adnan <
[email protected] (mailto:[email protected])

wrote:

Hmm... I really have no idea here... Does the directory exist,
is it
writeable etc?

---

Reply to this email directly or view it on GitHub:

#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

i had the same problem, first i only had ruby 1.8.7, the after installing ruby 1.93 it still didn't used the new one, and after that, it still used the old gems (from 1.8)

i solved it, by completely removing all
and reinstalling everything.

first uninstall:

brew uninstall imagemagick
gem uninstall lolcommits

then check your ruby version
ruby -v
if it prints something minor to 1.9.x

you should reinstall ruby and make it default (tested under mac os)
curl -L get.rvm.io | bash -s stable
source ~/.rvm/scripts/'rvm'
rvm install 1.9.3
rvm use ruby-1.9.3 --default
rvm get head

ruby -v
should now list 1.9.3 as default

now install
brew install imagemagick --from-source
gem install lolcommits

and everything should be working now! lol :-)

from lolcommits.

Yeah, just make sure all of what you install is in Ruby 1.9. No need to use rvm here, can just use homebrew to install ruby 1.9.

On Tuesday, 5 June 2012 at 19:18, Flori wrote:

i had the same problem, first i only had ruby 1.8.7, the after installing ruby 1.93 it still didn't used the new one, and after that, it still used the old gems (from 1.8)

i solved it, by completely removing all
and reinstalling everything.

first uninstall:

brew uninstall imagemagick
gem uninstall lolcommits

then check your ruby version
ruby -v
if it prints something minor to 1.9.x

you should reinstall ruby and make it default (tested under mac os)
curl -L get.rvm.io (http://get.rvm.io) | bash -s stable
source ~/.rvm/scripts/'rvm'
rvm install 1.9.3
rvm use ruby-1.9.3 --default
rvm get head

ruby -v
should now list 1.9.3 as default

now install
brew install imagemagick --from-source
gem install lolcommits

and everything should be working now! lol :-)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

i'm a total ruby noob and i didn't found an other way to change the default ruby version. first i installed it homebrew, but i didn't know how to change the default ruby version (and the default gem folder to use).
but maybe you can write the magic lines to achieve the same effect without rvm, please :-)

from lolcommits.

You just need to ensure you add all ruby 1.9 stuff before /usr/bin in your path since /usr/bin is where the system ruby 1.8 is located. So just make sure /usr/local/bin is at the top of your path, then run gem environment and add the installation path to the top of your path too. I guess it's more manual work than rvm to do this though.

On Tuesday, 5 June 2012 at 19:24, Flori wrote:

i'm a total ruby noob and i didn't found an other way to change the default ruby version. first i installed it homebrew, but i didn't know how to changed the default ruby version, and the default gem folder to use.
but maybe you can write the magic lines to achieve the same effect without rvm, please :-)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Question: when we do ruby -v we keep getting 1.8. how do we get it to 1.9
again?
Jason Burton

On Tue, Jun 5, 2012 at 3:28 PM, Adnan <
[email protected]

wrote:

You just need to ensure you add all ruby 1.9 stuff before /usr/bin in your
path since /usr/bin is where the system ruby 1.8 is located. So just make
sure /usr/local/bin is at the top of your path, then run gem environment
and add the installation path to the top of your path too. I guess it's
more manual work than rvm to do this though.

On Tuesday, 5 June 2012 at 19:24, Flori wrote:

i'm a total ruby noob and i didn't found an other way to change the
default ruby version. first i installed it homebrew, but i didn't know how
to changed the default ruby version, and the default gem folder to use.
but maybe you can write the magic lines to achieve the same effect
without rvm, please :-)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

You need to add the stuff we've discussed above to the top of your path (check your machine as it probably has the right path with echo $PATH). You'll also need to quit and reopen terminal when you edit your path for changes to take effect.

On Tuesday, 5 June 2012 at 19:44, Jason Burton wrote:

Question: when we do ruby -v we keep getting 1.8. how do we get it to 1.9
again?
Jason Burton

On Tue, Jun 5, 2012 at 3:28 PM, Adnan <
[email protected] (mailto:[email protected])

wrote:

You just need to ensure you add all ruby 1.9 stuff before /usr/bin in your
path since /usr/bin is where the system ruby 1.8 is located. So just make
sure /usr/local/bin is at the top of your path, then run gem environment
and add the installation path to the top of your path too. I guess it's
more manual work than rvm to do this though.

On Tuesday, 5 June 2012 at 19:24, Flori wrote:

i'm a total ruby noob and i didn't found an other way to change the
default ruby version. first i installed it homebrew, but i didn't know how
to changed the default ruby version, and the default gem folder to use.
but maybe you can write the magic lines to achieve the same effect

without rvm, please :-)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

Got it. It was the restarting of terminal that was the problem
Jason Burton

On Tue, Jun 5, 2012 at 3:47 PM, Adnan <
[email protected]

wrote:

You need to add the stuff we've discussed above to the top of your path
(check your machine as it probably has the right path with echo $PATH).
You'll also need to quit and reopen terminal when you edit your path for
changes to take effect.

On Tuesday, 5 June 2012 at 19:44, Jason Burton wrote:

Question: when we do ruby -v we keep getting 1.8. how do we get it to 1.9
again?
Jason Burton

On Tue, Jun 5, 2012 at 3:28 PM, Adnan <
[email protected] (mailto:[email protected])

wrote:

You just need to ensure you add all ruby 1.9 stuff before /usr/bin in
your
path since /usr/bin is where the system ruby 1.8 is located. So just
make
sure /usr/local/bin is at the top of your path, then run gem environment
and add the installation path to the top of your path too. I guess it's
more manual work than rvm to do this though.

On Tuesday, 5 June 2012 at 19:24, Flori wrote:

i'm a total ruby noob and i didn't found an other way to change the
default ruby version. first i installed it homebrew, but i didn't know
how
to changed the default ruby version, and the default gem folder to use.
but maybe you can write the magic lines to achieve the same effect

without rvm, please :-)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

yeah same problem here =/

from lolcommits.

I had the same problem and followed the instructions until I had the test working, but when I do an actual commit I get this error:

nicktassone$ git commit -m "fake message"
/Users/nicktassone/.rvm/gems/ruby-1.9.3-p194/gems/rmagick-2.13.1/lib/RMagick2.bundle:
[BUG] Segmentation fault
ruby 1.8.7 (2011-12-28 patchlevel 357) [universal-darwin11.0]


from lolcommits.

I think you might be missing /usr/local/bin from your path because your gems are calling from 1.9 but your ruby version seems is 1.8.7?

On Wednesday, 6 June 2012 at 15:34, Nick Tassone wrote:

I had the same problem and followed the instructions until I had the test working, but when I do an actual commit I get this error:

nicktassone$ git commit -m "fake message"
/Users/nicktassone/.rvm/gems/ruby-1.9.3-p194/gems/rmagick-2.13.1/lib/RMagick2.bundle: [BUG] Segmentation fault
ruby 1.8.7 (2011-12-28 patchlevel 357) [universal-darwin11.0]


---

Reply to this email directly or view it on GitHub:
#53 (comment)

from lolcommits.

My path in .profile reads export PATH=/usr/local/bin:/usr/local/Cellar/ruby/1.9.3-p194/bin/:$PATH. When I do ruby -v it says i'm on 1.9.3, but when I commit, it reads 1.8.7?

from lolcommits.

I really have no idea, to be honest. One thing you could do is remove your ruby 1.8.7 binaries from /usr/bin and see what happens (you won't need them unless you plan on going back to 1.8.7).

Another idea is to remove your homebrew installation of ruby 1.9 and use RVM instead (https://rvm.io/). This might be easier.

from lolcommits.

I also have this issue. on ruby 1.9. It works fine on my other Lion iMac but not on my new Lion iMac (the other Lion iMac is a three year old, where as the new Lion iMac is literally outta the box)

*** Preserving this moment in history.
/opt/local/lib/ruby1.9/gems/1.9.1/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in read': unable to open image/Users/barrycarlyon/.lolcommits/ym-custom-work/tmp_snapshot.jpg': No such file or directory @ error/blob.c/OpenBlob/2617 (Magick::ImageMagickError)
from /opt/local/lib/ruby1.9/gems/1.9.1/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in block in initialize' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/rmagick-2.13.1/lib/RMagick.rb:1634:ineach'
from /opt/local/lib/ruby1.9/gems/1.9.1/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in initialize' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:innew'
from /opt/local/lib/ruby1.9/gems/1.9.1/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in capture' from /opt/local/lib/ruby1.9/gems/1.9.1/gems/lolcommits-0.1.4/bin/lolcommits:102:indo_capture'
from /opt/local/lib/ruby1.9/gems/1.9.1/gems/lolcommits-0.1.4/bin/lolcommits:186:in <top (required)>' from /opt/local/bin/lolcommits:23:inload'
from /opt/local/bin/lolcommits:23:in `

I've got imagicmagick from mac ports.
Same setup on my Snow Leopard MacBook Pro.
Just no joy on brand spanking new iMac.
The directory exists tho as it auto created.

from lolcommits.

I'm now encountering the error on my used to work iMac, after reinstalling rmagick, as imagemagick had been updating from 6.7.6 to 6.7.7-2.
I reinstalled the gems rmagick and lolcommits after it initially complained, rmagick had been build to use 6.7.6

Now this error occurs. (The read tmp-snapshot.jpg)

from lolcommits.

Hmm, I updated the 6.7.7-6 just now to try and reproduce this error... and reinstalled rmagick and lolcommits and it worked fine. Maybe it's a problem with 6.7.7-2? Try 6.7.7-6?

from lolcommits.

I'll see if -6 is available in mac ports...... waits for iMac to chunder

Edit: I only have -2 in Mac Ports. I'll wait till its available.

from lolcommits.

Hmm. Does mac ports build it from source? If not I think it should be (as it says in the instructions). There might be an option for mac ports to build imagemagick from source like there is for one in homebrew.

from lolcommits.

the read': unable to open image/Users/Burton/.lolcommits/skeleton/tmp_snapshot.jpg': No such file or directory is due to an error of permission.
line 90 of lib/lolcommits.rb :
system("#{imagesnap_bin} -q #{snapshot_loc} -w #{capture_delay} #{capture_device}")
will try to execute the binary imagesnap but with user privilege though imagesnap can be executed by root only

this is a workaround :

modify the code and re-install lolcommits
git clone https://github.com/mroth/lolcommits.git
change line 89, it becomes imagesnap_bin = "imagesnap"
verify that you have imagesnap -> which imagesnap should return a path
then gem build lolcommits.gemspec
and sudo gem install lolcommits-0.1.4.gem

I don't actually understand how it could works for some people since it should fail for everyone. If anyone has an idea why it works on "old macs" I am quite interested ;-)

from lolcommits.

Thanks @matsumonkie, this was VERY helpful!

I'm using a Mac and changed permissions on /usr/local/lib/ruby/gems/1.9.1/gems/lolcommits-0.1.4/ext/imagesnap and worked fine now.

from lolcommits.

Glad it helped ;-)

from lolcommits.

Hmm... would the best fix for this be to add sudo in front of imagesnap_bin, then it would execute regardless of permissions right?

from lolcommits.

Yeah but I guess you would have to type your root password whenever you want to commit :s

from lolcommits.

Yeah, only downside. Are you using 1.8 or 1.9?

from lolcommits.

I upgraded it to 1.9 since I thought the version was the problem

from lolcommits.

I got exaclty the same issue :

$ git ci -a
*** Preserving this moment in history.
/Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in `read': unable to open image `/Users/loranger/.lolcommits/tao/tmp_snapshot.jpg': No such file or directory @ error/blob.c/OpenBlob/2617 (Magick::ImageMagickError)
    from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in `initialize'
    from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in `each'
    from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in `initialize'
    from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in `new'
    from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in `capture'
    from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:102:in `do_capture'
    from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:186
    from /usr/bin/lolcommits:19:in `load'
    from /usr/bin/lolcommits:19

Lolcommits used to work perfectly, but not anymore and now I'm sad.

Imagemagick has been upgraded using homebrew, but upgrading ruby fails, so I'm stuck whith this issue.
Changing permissions for the imagesnap binary did not help neither.

Here is my lolcommit -c --test output, I don't know, it may help

$ lolcommits -c --test
*** capturing in test mode
*** Preserving this moment in history.
dyld: Library not loaded: /usr/local/lib/libtiff.3.dylib
  Referenced from: /usr/local/bin/gs
  Reason: image not found
dyld: Library not loaded: /usr/local/lib/libtiff.3.dylib
  Referenced from: /usr/local/bin/gs
  Reason: image not found
/Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:147:in `annotate': unable to read font `/Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/../fonts/Impact.ttf' @ error/annotate.c/RenderFreetype/1123: `(null)' (Magick::ImageMagickError)
    from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:147:in `capture'
    from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:100:in `do_capture'
    from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:186
    from /usr/bin/lolcommits:19:in `load'
    from /usr/bin/lolcommits:19

from lolcommits.

same problem of permissions, it needs root permission to use the fonts.
there should be a font file : /usr/local/lib/ruby/gems/1.9.1/gems/lolcommits-0.1.4/fonts/Impact.ttf
try to chmod it and it should be ok ;-)

from lolcommits.

It fix the first error, but did not resolve the issue :

$ lolcommits -c --test
*** capturing in test mode
*** Preserving this moment in history.
/Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in `read': unable to open image `/Users/loranger/.lolcommits/test/tmp_snapshot.jpg': No such file or directory @ error/blob.c/OpenBlob/2617 (Magick::ImageMagickError)
    from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1635:in `initialize'
    from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in `each'
    from /Library/Ruby/Gems/1.8/gems/rmagick-2.13.1/lib/RMagick.rb:1634:in `initialize'
    from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in `new'
    from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/lib/lolcommits.rb:123:in `capture'
    from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:100:in `do_capture'
    from /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/bin/lolcommits:186
    from /usr/bin/lolcommits:19:in `load'
    from /usr/bin/lolcommits:19

It worked like a charm before ImageMagick was updated. How can it be, it's now such a mess ?

from lolcommits.

can you try to execute the binary imagesnap just so we see if it takes a picture ?

from lolcommits.

@loranger you need to chmod your imagesnap in /Library/Ruby/Gems/1.8/gems/lolcommits-0.1.4/ext/imagesnap.
On my machine the path was /usr/local/lib/ruby/gems/1.9.1/gems/lolcommits-0.1.4/ext/imagesnap (mac) and worked fine.

from lolcommits.