You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS: SLES 15 SP4
ruby: ruby 2.5.9p229 (2021-04-05 revision 67939) [x86_64-linux-gnu] (from SLES distro)
digest gem version: 3.1.1 (latest avail at time of writing)
The actionmailer gem from v7.0.1, as well as the mail gem from v2.8.0 have new dependent gems net-imap, net.pop, net-smtp. Of these, net-imap has dependent gem digest. Thus from Rails 7.0.1 or if using mail 2.8.0 or higher, users are forced to use the digest gem.
As part of an app upgrade to Rails 6.1.7 I included mail 2.8.0, and found my application build breaking: all calls to bundler (in my case the first call is bundle exec rake assets:precompile) following bundle install fail with:
In my case I pre-compile gems first and push the compiles gems to a geminabox server. This is then accessed by the application build.
The problem appears to be that two loader files are not copied from the ext tree of the gem to the lib tree. When I copied the files manually the issue was resolved:
OS: SLES 15 SP4
ruby: ruby 2.5.9p229 (2021-04-05 revision 67939) [x86_64-linux-gnu] (from SLES distro)
digest gem version: 3.1.1 (latest avail at time of writing)
The
actionmailer
gem from v7.0.1, as well as themail
gem from v2.8.0 have new dependent gemsnet-imap
,net.pop
,net-smtp
. Of these,net-imap
has dependent gemdigest
. Thus from Rails 7.0.1 or if using mail 2.8.0 or higher, users are forced to use the digest gem.As part of an app upgrade to Rails 6.1.7 I included mail 2.8.0, and found my application build breaking: all calls to
bundler
(in my case the first call isbundle exec rake assets:precompile
) following bundle install fail with:In my case I pre-compile gems first and push the compiles gems to a geminabox server. This is then accessed by the application build.
The problem appears to be that two loader files are not copied from the ext tree of the gem to the lib tree. When I copied the files manually the issue was resolved:
This problem also appears to be discussed in github.com/rubygems/rubygems/issues/5619
Can the gem be corrected so that copying of the loader files is no longer required?
The text was updated successfully, but these errors were encountered: