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

Cannot use no-style-please on Jekyll above 3.8.7 #12

Closed
jamiehowarth0 opened this issue Feb 1, 2021 · 8 comments · Fixed by #98
Closed

Cannot use no-style-please on Jekyll above 3.8.7 #12

jamiehowarth0 opened this issue Feb 1, 2021 · 8 comments · Fixed by #98

Comments

@jamiehowarth0
Copy link

All version of no-style-please on Rubygems except for 0.1.0 require Jekyll 3.8.7. As a result, 0.1.0 is installed on Jekyll 4 & above, which has a bug of a missing {{ content }} block in the home layout.

@riggraz
Copy link
Owner

riggraz commented Jun 14, 2021

I try to stay compatible with GitHub Pages (see here], so right now this theme is running Jekyll v3.9.0.

Hopefully GitHub Pages will support Jekyll 4 soon.

@bluebrown
Copy link

looks like its out of sync now. I am using 226 which seems to be the latest version of github-pages.

Bundler could not find compatible versions for gem "jekyll":
  In Gemfile:
    github-pages (~> 226) was resolved to 226, which depends on
      jekyll (= 3.9.2)

    no-style-please was resolved to 0.1.0, which depends on
      jekyll (~> 4.1)
Bundler could not find compatible versions for gem "jekyll-seo-tag":
  In Gemfile:
    github-pages (~> 226) was resolved to 226, which depends on
      jekyll-seo-tag (= 2.8.0)

    no-style-please was resolved to 0.4.7, which depends on
      jekyll-seo-tag (~> 2.7.1)

@f2l2pe
Copy link

f2l2pe commented Jul 16, 2023

looks like its out of sync now. I am using 226 which seems to be the latest version of github-pages.

Bundler could not find compatible versions for gem "jekyll":
  In Gemfile:
    github-pages (~> 226) was resolved to 226, which depends on
      jekyll (= 3.9.2)

    no-style-please was resolved to 0.1.0, which depends on
      jekyll (~> 4.1)
Bundler could not find compatible versions for gem "jekyll-seo-tag":
  In Gemfile:
    github-pages (~> 226) was resolved to 226, which depends on
      jekyll-seo-tag (= 2.8.0)

    no-style-please was resolved to 0.4.7, which depends on
      jekyll-seo-tag (~> 2.7.1)

Im having the same problem.

@materialvision
Copy link

same problem

@riggraz
Copy link
Owner

riggraz commented Jun 11, 2024

You're probably using version 0.1.0 of no-style-please. Try to use 0.4.7 instead, please :)

@sockbot
Copy link

sockbot commented Jul 19, 2024

You're probably using version 0.1.0 of no-style-please. Try to use 0.4.7 instead, please :)

There is a conflict between dependencies on jekyll-seo-tag versions:

Could not find compatible versions

Because no-style-please >= 0.4.5 depends on jekyll-seo-tag ~> 2.7.1
  and github-pages >= 224 depends on jekyll-seo-tag = 2.8.0,
  no-style-please >= 0.4.5 is incompatible with github-pages >= 224.
So, because Gemfile depends on github-pages ~> 231
  and Gemfile depends on no-style-please ~> 0.4.7,
  version solving has failed.

I'm confused-- reading this it looks like jekyll-seo-tag 2.8.0 should satisfy both no-style-please >= 0.4.5 and github-pages >= 224?

Current release of github-pages as of this date is 231.

@Sealatron
Copy link

Sealatron commented Dec 23, 2024

I'm getting the same issue as @sockbot, exact same conflict in versions. However I think the error is actually saying that no-style-please 0.4.7 is not compatible with jekyll-seo-tag 2.8.0, which is now required for github-pages as no-style-please only supports 2.7.X of jekyll-seo-tag.

@tanvincible
Copy link
Collaborator

As of now, this update hasn't been published to RubyGems. One workaround is to reference this theme in your Gemfile as:

gem 'no-style-please', git: 'https://github.com/riggraz/no-style-please', branch: 'master'

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

Successfully merging a pull request may close this issue.

8 participants