Closed GoogleCodeExporter closed 9 years ago
It seems like you have half-installed ruby2 which is not compatible with msf.
That's the reason of that message. We are trying to find a better way to deal
with such such cases.
Could you investigate how you end up with Rubygems 2.0 installed? Is it in your
~./gems directory?..
Please also post the following output:
eselect ruby list
Original comment by blshkv
on 23 Aug 2013 at 3:51
just before I forget, we need to mark that bug as a dup of issue #169.
Original comment by blshkv
on 23 Aug 2013 at 2:02
At first, I wasn't sure it was related, but believe you are probably correct.
As things stand, I think you should zap this bug, let me investigate my gem
environment, and I'll update the other bug as I make progress on that.
My goal is to have both Pentoo metasploit and a local dev copy cloned from git,
with both working and coexisting. If both cannot coexist, I'm not quite sure
what to do about that, other than simply ignore Pentoo's metasploit + data
model + gem and do as I've been doing all along.
Hoping to not have to do that...
Thanks.
Original comment by willard....@gmail.com
on 23 Aug 2013 at 2:36
Just for my own sake, why exactly do you want both installed? In my experience
the pentoo version is more capable, not less. Especially now that the bundler
support has been added. the only thing that appears to be breaking on your end
is having ruby2 installed and neither copy supports that.
Original comment by sidhayn
on 23 Aug 2013 at 4:55
The goal seems to have the "original" and pentoo (less trusted) installs.
That's kind of troublesome because you already have system ruby and all ruby
deps installed. The best you could try is to install msf locally (~.gems) first
and then pentoo's version. You should also update it in that order too.
I would suggest to have 2 slotted copies from Pentoo instead ;-)
We provide the stable metasploit:4.6 and the latest :9999.
It's very easy to switch between them using:
eselect metasploit list
Available metasploit symlink targets:
[1] metasploit4.6
[2] metasploit9999 *
Original comment by blshkv
on 23 Aug 2013 at 10:51
Original comment by sidhayn
on 25 Aug 2013 at 4:10
I just realised, the issue #169 (ruby2.0 problem) was also filed by you.
You are trying to break your system. We can't fix that.
Original comment by blshkv
on 25 Aug 2013 at 4:14
Original issue reported on code.google.com by
willard....@gmail.com
on 23 Aug 2013 at 2:05Attachments: