Closed ManuelSchneid3r closed 7 years ago
Do you mean our activesupport dependency? https://github.com/jekyll/jemoji/blob/46a615347e0b110afc0eb7f657f78e950f3876ae/jemoji.gemspec#L14
@ManuelSchneid3r Hi, did you solve the problem? I've got the almost the same error except my json version is 2.0.2.
I'm hosting jekyll on private server. Here are my gems: LOCAL GEMS
activesupport (4.2.7.1) addressable (2.5.0) backports (3.6.8) bigdecimal (default: 1.3.0.pre.2) bundler (1.14.2) bundler-unload (1.0.2) colorator (1.1.0) did_you_mean (1.0.2) executable-hooks (1.3.2) ffi (1.9.17) forwardable-extended (2.6.0) gem-wrappers (1.2.7) gemoji (3.0.0) html-pipeline (2.5.0) i18n (0.8.0) io-console (default: 0.4.6) jekyll (3.3.1) jekyll-admin (0.3.0) jekyll-feed (0.8.0) jekyll-paginate (1.1.0) jekyll-sass-converter (1.5.0) jekyll-seo-tag (2.1.0) jekyll-watch (1.5.0) jemoji (0.8.0) json (default: 2.0.2, 1.8.6) kramdown (1.13.2) liquid (3.0.6) listen (3.0.8) mercenary (0.3.6) mini_portile2 (2.1.0) minima (2.1.0) minitest (5.10.1) multi_json (1.12.1) net-telnet (0.1.1) nokogiri (1.7.0.1) openssl (default: 2.0.1) pathutil (0.14.0) power_assert (0.4.1) psych (default: 2.2.1) public_suffix (2.0.5) rack (2.0.1, 1.6.5) rack-protection (1.5.3) rack-test (0.6.3) rake (12.0.0) rb-fsevent (0.9.8) rb-inotify (0.9.7) rdoc (default: 5.0.0) rouge (1.11.1) rubygems-bundler (1.4.4) rvm (1.11.3.9) safe_yaml (1.0.4) sass (3.4.23) sinatra (1.4.7) sinatra-contrib (1.4.7) test-unit (3.2.3) thread_safe (0.3.5) tilt (2.0.5) tzinfo (1.2.2) xmlrpc (0.1.1)
Do you mean our activesupport dependency?
yes. seems like its rather an issue with active supports dependencies.
Hi, did you solve the problem?
It's been a while, iirc I uninstalled all but JSON 1.7
activesupport 5.x no longer has the json dependency. However, jemoji has a dependency for an earlier version of activesupport which is causing dependency issues as I've noted in other issue opened.
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master
branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
@getChester is there a PR to upgrade the activesupport dependency?
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master
branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
@parkr Hello, I didn't notice that, but the PR #62 should resolve this issue, as well as the #57... We just need someone from the team clicking on the green button
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master
branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
Fixed by #62
Shouldnt you remove the pessimisitc constraint?