mimemagic | Mime type detection in ruby via file extension | Web Framework library

I'm aware of the recent mimemagic issues, which I managed to resolve on one of my Rails projects by bundle updating to 0.3.7 - but for some reason, I can't resolve it on the project below.

I have a Rails 6 project which I'm setting up for the first time on a new laptop. My laptop doesn't have the correct Ruby setup, so I've added a Dockerfile to my project like so:-

Dockerfile

Im running ruby version 2.6.1 with docker. Rake gem is version 13.0.1.
Whenever I tried docker-compose up, it always fails and throws this error everytime:
This error did not exist before.

I keep receiving this error Your bundle is locked to mimemagic (0.3.5) from rubygems repository when pushing to heroku.

I read the resolved issue on Github where the Rails team swapped the dependency on ActiveStorage from mimemagic to mini_mime. So I did what was recommended and upgraded my app from Rails 6.0.3 to 6.1.3.2. My Gemfile now has gem 'rails', '>=6.1.3.2'.

I ran bundle update which updated all the gems and I did a bundle uninstall mimemagic for good measure.

I verified in my Gemfile.lock that there is no longer a reference to mime_magic. Instead, I can see that activestorage has the updated dependency on mini_mime:

I'm upgrading rails from 4.2 to 5.0, and I'm getting some mean dependency issues. When I run bundle update i get the following output. The thing is that when i look through the messages, it looks like the gems should be able to install just fine when looking at the version requirements.

I also tried to delete my Gemfile.lock, that didn't help.

Any suggestions would be appreciated.

I am having trouble pushing to heroku, I've already tried others solutions related to Precompiling assets failed., like modifing application.rb to disable precompiled assets, running rake assets:precompile, and updating to rails 6.3.1 to prevent mimemagic recent error.

Taking a look at heroku logs, I noticed:

tmp/build_7857ebbd/vendor/bundle/ruby/3.0.0/gems/sassc-2.4.0/lib/sassc/engine.rb:43: [BUG] Segmentation fault at 0x0000000000000000 ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-linux]

Part of heroku's log

Today I tried to build a docker for my rails 6.1.0 with active storage, I got the following error:

I had a program that worked a few weeks ago and I wiped it out and had to re-install my ruby and rails enviornment and now I can not bundle install the same program because Paperclip requires Mimemagic and apparently the working versions of the gems no longer exist. Any versions of the gem that remain require this freedesktop.org.xml thing which I went to their site and downloaded but I do not understand on a windows machine how to install the freedesktop.org.xml package so that I can use Ruby on Rails again.

Does anyone know how to install the freedesktop.org.xml package/script/whatever it is so that rails will work properly again? If ANY of our apps break now we are going to be a HORRIBLE place due to this. I have been searching for hours and everything references a MAC or Linux, I am on a PC and I can find NOPLACE that has understandable instructions for how to do this on a Windows 10 PC.

Please HELP!

Thank You, Scott

Update: I tried the suggestion to add:

gem 'mimemagic', git: 'git@github.com:mimemagicrb/mimemagic.git', tag: "v#{[0.3.0]}"

into the gemfile and this is the results I get.

----UPDATE

I have cloned the repo in an other directory and went throw the all process again, this time though I noticed that the issue comes out only after using:

I recently upgraded a Rails 6.0.3.5 app to 6.1.3 after the mimemagic fiasco.

Now, I see this interesting issue that is happening after the view is rendered, which is strange. How do I debug this? The app is using Ruby 2.7.1

Here is the full stack trace