search

guard / rb-inotify

A thorough inotify wrapper for Ruby using FFI.
MIT License
312 stars 64 forks source link

Version 0.9.7 can't be downloaded from rubygems.org #52

Closed ehirsch closed 7 years ago

ehirsch commented 8 years ago

I don't know, if you can do anything about that. But wanted to let you know.

I get the following error: 

Could not find rb-inotify.gem (rubygems:rb-inotify:0.9.6).
     Searched in the following locations:
         http://rubygems-proxy.torquebox.org/releases/rubygems/rb-inotify/0.9.6/rb-inotify-0.9.6.gem
jonnyasmar commented 8 years ago

^ Having the same issue here.

jpete commented 8 years ago

^ Same issue

matthew-lang commented 8 years ago

^ Same here The following bandaid helped me -- http://stackoverflow.com/a/35274249

nex3 commented 8 years ago

I've pushed a new patch version, and it looks like it works. I guess something went awry with the upload process last time.

ericrrath commented 8 years ago

I think the gem can be downloaded from rubygems.org. But the torquebox URL -- http://rubygems-proxy.torquebox.org/releases/rubygems/rb-inotify/0.9.6/rb-inotify-0.9.6.gem -- produces a response with status 403 and a body that appears to be generated by AWS.

johnnyshields commented 8 years ago

See this for explanation from rubygems: https://github.com/rubygems/rubygems.org/issues/1192

ehirsch commented 8 years ago

Thanks for the quick response! but while there is no 403 error any more it is now 404. The Problem remains I am afraid. @ericrrath is right: The file is downloadable from rubygems.org but not from the proxy

nex3 commented 8 years ago

I have indeed yanked 0.9.6 because it was broken—0.9.7 is identical except for its version number. It looks like it's still not downloadable from torquebox, though, which at this point seems like a rubygems.org issue. I don't want to upload yet another version unless I know it'll fix the problem, so I'd appreciate it if someone contacted the rubygems.org folks and figured out what's going on on their end.

jpete commented 8 years ago

I contacted them on 2/8, just before I posted the bump here. I have not heard anything back, and it is still down so maybe they have not gotten to it yet.

ioquatix commented 7 years ago

We are now on release 0.9.8 and I don't seem to be able to reproduce this issue. Thanks for your input and attention everyone and let me know if this is still an issue that requires investigation.