Metasploit-framework: [Bug]Can't install Metasploit in Termux

[RealGJ]

I'm not sure what is the problem but, Whenever I try to install metasploit in Termux (Android) following error popups:

Traceback (most recent call last):
1: from :1:in <internal:gem_prelude>' <internal:gem_prelude>:1:inrequire': cannot load such file -- rubygems.rb (LoadError)
dpkg: error processing package metasploit (--configure):
installed metasploit package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
metasploit
E: Sub-process /data/data/com.termux/files/usr/bin/dpkg returned an error code (1)

See screenshots: https://photos.app.goo.gl/RDP9srfmvhsWEN2h6

[whitedays2007]

Can't install metasploit in Termux?

[whitedays2007]

E: Sub-process /data/data/com.termux/files/usr/bin/dpkg returned an error code (1)

The solution is very simple

[whitedays2007]

Termux Solution: rm -rf $PREFIX/var/lib/dpkg/info/*
Then apt update is fine.

[RealGJ]

@whitedays2007 Thank you for Reply and Help. Now msfconsole Command isn't working!!

https://photos.app.goo.gl/VncSQpQRikQRMAfx8

[whitedays2007]

If you cannot use the metasploit installed in the unstable-repo repository, you can use the official project

Termux command：
update...
apt update && apt upgrade -y
requirements:
Some requirement libraries may not be written in, you can research by yourself what requirement libraries are still missing
apt install ruby postgresql clang python2 python git
Clone:
git clone https://github.com/rapid7/metasploit-framework
bundle:
cd metasploit-framework/
gem install bundle
gem install bundler
bundle install

start:
ruby msfconsole
If not, leave a message

[github-actions[bot]]

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.