Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Jun 2015 07:03:08 +0000
From:      bugzilla-noreply@freebsd.org
To:        ruby@FreeBSD.org
Subject:   [Bug 199107] Several rubygem CONFLICTS: Eg: archivers/rubygem-rubyzip & devel/rubygem-i18n causing security/metasploit build failure
Message-ID:  <bug-199107-21402-6GPMabUxRX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-199107-21402@https.bugs.freebsd.org/bugzilla/>
References:  <bug-199107-21402@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199107

--- Comment #8 from dewayne@heuristicsystems.com.au ---
(In reply to dewayne from comment #7)
When I removed STAGEDIR=/usr/staging from make.conf, the conflicts amoung the
various rubygem ports ceased being a barrier.  So that is where the problem
lay.

On the way to this discovery, I'd introduced 
NOPORTDOCS and DISABLE_CONFLICTS into make.conf, which unfortunately moved the
doc and rdoc conflicts to other areas. Eg
pkg-static: rubygem-network_interface-0.0.1 conflicts with
rubygem-msgpack-0.5.5 (installs files into the same place).  Problematic file:
/usr/local/lib/ruby/gems/2.1/extensions/amd64-freebsd-10/2.1/msgpack-0.5.5/gem.build_complete

-- 
You are receiving this mail because:
You are on the CC list for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199107-21402-6GPMabUxRX>