search

sup-heliotrope / sup

A curses threads-with-tags style email client (mailing list: supmua@googlegroups.com)
http://sup-heliotrope.github.io
GNU General Public License v2.0
900 stars 97 forks source link

Missing `mime/types` dependency in Debian Bullseye #611

Closed Tomaz-Vieira closed 2 years ago

Tomaz-Vieira commented 2 years ago

Running sup-mail in Debian Bullseye after installing via apt install sup-mail raises this error:

Ignoring executable-hooks-1.6.1 because its extensions are not built. Try: gem pristine executable-hooks --version 1.6.1
Ignoring gem-wrappers-1.4.0 because its extensions are not built. Try: gem pristine gem-wrappers --version 1.4.0
Traceback (most recent call last):
    8: from /usr/bin/sup-mail:8:in `<main>'
    7: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
    6: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
    5: from /usr/lib/ruby/vendor_ruby/sup/util/ncurses.rb:2:in `<top (required)>'
    4: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
    3: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
    2: from /usr/lib/ruby/vendor_ruby/sup/util.rb:5:in `<top (required)>'
    1: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': cannot load such file -- mime/types (LoadError)

I thought maybe installing ruby-mime-types and ruby-mime-types-data would solve it, but it wasn't the case

Tomaz-Vieira commented 2 years ago

I tried in a clean(er) debootstrapped container and it actually works there... It might be something on my machine

danc86 commented 2 years ago

Sup declares a dependency on the mime-types gem in sup.gemspec so I don't think there is any bug on the Sup side. I'm not too familiar with Debian packaging, I see that all the expected gems are declared as Build-Depends but not Depends: https://salsa.debian.org/ruby-team/sup-mail/-/blob/master/debian/control so that might be the problem?

Another common issue would be if you have accidentally done sudo gem install sup at some point and it has overwritten some parts of the regular sup-mail Debian package with its own copy that is looking in the wrong Ruby path, something like that.

If you can reproduce the issue I'd suggest to file a Debian bug. Please feel free to reopen this one if you find something wrong in Sup itself.