ruby-hacking-guide / ruby-hacking-guide.github.com

Ruby Hacking Guide Translation
http://ruby-hacking-guide.github.io/
318 stars 50 forks source link

ruby script/publish generate epub error #27

Closed zhufenggood closed 11 years ago

zhufenggood commented 11 years ago
➜  ruby-hacking-guide.github.com-master  ruby script/publish
Configuration file: /Users/zhufenggood/Downloads/ruby-hacking-guide.github.com-master/_config.yml
            Source: /Users/zhufenggood/Downloads/ruby-hacking-guide.github.com-master
       Destination: /Users/zhufenggood/Downloads/ruby-hacking-guide.github.com-master/_site
      Generating... done.
fatal: Not a git repository (or any of the parent directories): .git
/Users/zhufenggood/.rvm/gems/ruby-1.9.3-p362@jekll/gems/zip-2.0.2/lib/zip/zip.rb:959:in `put_next_entry': wrong number of arguments (5 for 2) (ArgumentError)
    from /Users/zhufenggood/.rvm/gems/ruby-1.9.3-p362@jekll/gems/eeepub-0.8.0/lib/eeepub/ocf.rb:96:in `block (2 levels) in save'
    from /Users/zhufenggood/.rvm/gems/ruby-1.9.3-p362@jekll/gems/zip-2.0.2/lib/zip/zip.rb:942:in `open'
    from /Users/zhufenggood/.rvm/gems/ruby-1.9.3-p362@jekll/gems/eeepub-0.8.0/lib/eeepub/ocf.rb:95:in `block in save'
    from /Users/zhufenggood/.rvm/gems/ruby-1.9.3-p362@jekll/gems/eeepub-0.8.0/lib/eeepub/ocf.rb:126:in `block in create_epub'
    from /Users/zhufenggood/.rvm/rubies/ruby-1.9.3-p362/lib/ruby/1.9.1/fileutils.rb:125:in `chdir'
    from /Users/zhufenggood/.rvm/rubies/ruby-1.9.3-p362/lib/ruby/1.9.1/fileutils.rb:125:in `cd'
    from /Users/zhufenggood/.rvm/gems/ruby-1.9.3-p362@jekll/gems/eeepub-0.8.0/lib/eeepub/ocf.rb:121:in `create_epub'
    from /Users/zhufenggood/.rvm/gems/ruby-1.9.3-p362@jekll/gems/eeepub-0.8.0/lib/eeepub/ocf.rb:94:in `save'
    from /Users/zhufenggood/.rvm/gems/ruby-1.9.3-p362@jekll/gems/eeepub-0.8.0/lib/eeepub/maker.rb:83:in `save'
    from script/publish:109:in `<main>'

try

gem uninstall rubyzip
gem install rubyzip -v 0.9.9

Solve the problem and successful generate epub file.

markburns commented 11 years ago

I'm going to close this as (I think?) you are saying you found the solution to your issue and are reporting it for anyone else encountering this issue.

Please correct me if I'm wrong.