jekyll-sass-converter | A Sass converter for Jekyll | Theme library

The root problem is that you cannot install one of jekyl's dependancies - specifically the ffi gem. Knowing that will better help you workout a fix.

You can see that this is the error by reading your bundle output. Learn how to read these so you can better help yourself in the future; If you were searching for "install ffi on macOS" you might have found more information available to you.

Give that you've just installed Catalina, it's likely that GCC isn't on your machine, or is outdated, or is unlinked.

Try running xcode-select --install to (re)install the Xcode command line tools.

At the very top of your bundle output is a warning that you shouldn't use sudo when installing gems. It's good advice to follow!

Even better advice would be to use rbenv or rvm to create gem sets or environments for each ruby application you're working with. But, if you don't go all the way down that path, ** at least, stop using sudo**

After a so many attempts to fix the tests, i finnaly find a solution, thanks you @fredrik*

Here is my workflow file:

Your project directory structure looks a little odd, since you use the unconventional organisation within the src folder.

I see 2 simple solutions:

That is the expected structure and you don't run into further configuration issues. It will just work because everything is where it is supposed to be.

In your _config.yml add the following sections:

There may be one culprit gem here but you will run into this problem again and again unless you fix your underlying approach.

Look at your gems environment; all gems are installed into one folder, regardless of the project you’re working on. So, if you have two projects with conflicting dependencies you will get this problem again.

There are tools, like RVM, which let you create environments for each project. So, each project has its own separate collection of gems and even distinct versions of Ruby if you need 2.7 in one project and 2.5 for another.

See "Easy way to setting Ruby Version Manager (RVM) on projects" for how to use RVM and create a gemset for each project.

If another bundle install didn't work, delete Gemfile.lock then try specifying the version for public_suffix in Gemfile like so:

An alternative would be to "use Jekyll in Windows with Docker" (from James Sturtevant)

That would take advantage of the Docker image jekyll/jekyll (see its README).

Installing Mac OS X again was the only solution. Now Jekyll is running again...

In your Gemfile, uncomment #gem "jekyll-theme-basically-basic" to read gem "jekyll-theme-basically-basic".

For some reasons, in your .gitlab-ci.yml, all the gem install ... are useless, and it's the bundle install that does the required job.

The root of the problem seems to be bundler. What operating system and Ruby version are you using? It may be a problem with old OpenSSL library, so you can not install bundler and everything after it.

If you are using jRuby (your gem list output tells so), your problem seems to be the same as described in link. And there is a solution as well.

Maybe you forgot to set 2.1.2 version of ruby as global? (rbenv set global 2.1.2)