If you are a Rails 6.1+ user, you probably have noticed something is up in the past couple days.
Good morning everyone! If you have a Rails app ...
For further actions, you may consider blocking this person and/or reporting abuse
Please install shared-mime-info and add FREEDESKTOP_MIME_TYPES_PATH in your environment.
if you use windows or linux, please download from gitlab.freedesktop.org/xdg/shared-... and extract it
This package has no
freedesktop.org.xml, justfreedesktop.org.xml.inI renamed the file to
freedesktop.org.xmland it worked for me.Regarding: github.com/rails/rails/issues/4175...
Maybe I miss a piece, but in't it allowed to ship GPL code alongside your code as long as it stays packaged and its license it kept? Or does this only apply to compiled code?
That header is my favorite meme of the week 😂
😂😂😂
Awesome, thanks for the update with the latest Rails version for the fix! I had no idea what was going on until I found your post. Thanks so much!!
Welcome! It was great to see Rails get out a fix so quick on this.
Christine thanks for the write-up. I had a momentary panic attack this morning running bundle install and this showed up right away!
Glad the write-up helped!I found it interesting tracking down the why on this one, and thought others in the community might enjoy the read.
Any update on this? I still can't bundle install.
Install
shared-mime-infomanually, then runbundle updateOS X:
brew install shared-mime-infoLinux (debian-based distro):
apt-get install shared-mime-info(I think, I didn't test this)Thanks for sharing a workaround, but this could potentially have copyright impacts if you start using pulling in shared-mime-info because I believe it is GNU GPL v2 licensed.
An alternative could also be github.com/rails/rails/issues/4175...
Yes, this workaround wasn't in that thread when I posted this.
Absolutely the better option, by far.
Thanks for this great summary!
This write-up is great, thanks for sharing it. Am I missing something, or is there no communication of this sort from official Rails channels? (Have checked their Twitter, website, and forum and haven't found an announcement of the issue and how it's being addressed.) All I can find are threads in GitHub issues.
This seems crazy given how big an issue this is.
Looks like Rails just released an update that discusses this a bit, but I agree it did feel like it was kind of radio silence on this issue: weblog.rubyonrails.org/2021/3/26/m...
Great, updating Rails, I did can build my docker container again, because the command "build install" was failing