Oddity ... possible env issue?



Hey guys, working on gems still & getting this oddity …

bundle exec rake release    
    Pushing gem to https://github.com/Mirv/hihi...
    Cookies must be enabled to use GitHub.

I scoured the github doc, rails guides & edgeguides.

I got a close hit, but it’s kind of complicated for what I’m looking at right now … https://github.com/GPGTools/GPGTools_Core/commit/4d98d5b87b08afdb72665022cbcf28e55cbe754c

Does anyone have suggestions for how to get around the cookies issue or adapt this fix code to get it so I can submit my own gems?


Apparently, I had several entangled issues …

The Github thing is a behavior I’ve noticed but never thought about … if you create the repo on github.com & then connect to upload several times, github will automatically drop a cookie to remember. So, the fix is just pushing 3 times, for that part.

The other part that snagged me & I’m not sure what the best fix is on it - as it’s some sort of security measure …

mirv:~/workspace/hihi (master) $ gem push hihi-0.1.0
ERROR:  While executing gem ... (Gem::Package::FormatError)
    No such file or directory @ rb_sysopen - hihi-0.1.0
mirv:~/workspace/hihi (master) $ gem -v

Which was worked around by commenting out the …

  # Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'
  # to allow pushing to a single host or delete this section to allow pushing to any host.
  # if spec.respond_to?(:metadata)
  #   spec.metadata['allowed_push_host'] = "https://github.com/Mirv/hihi"
  # else
  #   raise "RubyGems 2.0 or newer is required to protect against " \
  #     "public gem pushes."
  # end