Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Could not find a valid gem 'sketch' (~> 0.4) in any repository #8

Open
younata opened this issue Jul 7, 2016 · 3 comments
Open

Comments

@younata
Copy link

younata commented Jul 7, 2016

Hey friend,

Trying to install this, and it seems like you missed a zero when you updated the dependency on sketch, because the latest version for sketch (according to https://rubygems.org/gems/sketch, and the source at https://github.com/mustmodify/sketch/releases), the latest is 0.0.4, yet the gemspec wants 0.4.

Did I mess something up? Looks like Sketch hasn't been updated in years, yet you depend upon a nonexistent version.

@bfoz
Copy link
Owner

bfoz commented Jul 8, 2016

Actually, I'm not using the Sketch gem that's hosted on rubygems (it's ancient, unmaintained, and doesn't actually do sketching). I'm using my own gem: https://github.com/bfoz/sketch

Bundler should do the right thing though. Can you tell me exactly what happened?

@younata
Copy link
Author

younata commented Oct 20, 2016

(3 months later)

I'm using it as a dependency in a rails app.

So, my Gemfile contains gem 'dxf', github: 'bfoz/dxf-ruby', and when I run bundle, I get:

Fetching git://github.com/bfoz/dxf-ruby.git
Fetching gem metadata from https://rubygems.org/...........
Fetching version metadata from https://rubygems.org/..
Fetching dependency metadata from https://rubygems.org/.
Resolving dependencies...
Bundler could not find compatible versions for gem "sketch":
  In Gemfile:
    dxf was resolved to 0.3.1, which depends on
      sketch (~> 0.4)

Could not find gem 'sketch (~> 0.4)', which is required by gem 'dxf', in any of the sources.

We got around this for ages by just forking the project and deleting the unparser feature (which we didn't depend upon), but now that we want to contribute some of our improvements back, we're running into this issue again.

@bfoz
Copy link
Owner

bfoz commented Oct 22, 2016

Off the top of my head, I don't know exactly how to fix this, and I may not have time to look at it this weekend. I have a fuzzy memory that, once upon a time, bundler didn't respect the Gemfiles of nested dependencies. I thought that had been fixed, but maybe not. I'll look into this when I get a chance. Thanks for the info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants