Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 May 2015 00:01:15 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 199107] Several rubygem CONFLICTS: Eg: archivers/rubygem-rubyzip & devel/rubygem-i18n causing security/metasploit build failure
Message-ID:  <bug-199107-13-2WJvCpLIbi@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-199107-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-199107-13@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 #7 from dewayne@heuristicsystems.com.au ---
(In reply to Sunpoet Po-Chuan Hsieh from comment #6)
Thank-you for looking into this issue.

I'm able to reproduce *a* problem simply by building the metasploit package on
a:
FreeBSD 10.1-STABLE FreeBSD 10.1-STABLE #0 r283313M: Sun May 24 06:48:51 AEST
2015 1001515 1001515
poudriere is not used.

I just updated /usr/ports via svnlite, and attempted to build metasploit with
this result
===>   Registering installation for rubygem-journey-1.0.4 as automatic
[b2.hs] Installing rubygem-journey-1.0.4...
pkg-static: rubygem-journey-1.0.4 conflicts with rubygem-erubis-2.7.0_1
(installs files into the same place).  Problematic file:
/usr/local/lib/ruby/gems/2.1/doc/erubis-2.7.0/rdoc/ActionController.html
*** Error code 70
Stop.
make[2]: stopped in /usr/ports/www/rubygem-journey
*** Error code 1
Stop.
make[1]: stopped in /usr/ports/www/rubygem-actionpack
*** Error code 1
Stop.
make: stopped in /usr/ports/security/metasploit

Out of frustration I've tried silly things like 
OPTIONS_UNSET=DOC RDOC DOCS RDOCS HTMLDOCS PORTDOCS APIDOCS RDOC 
and
pkg delete rubygem-rubyzip-1.1.7 rubygem-multi_json-1.11.0
rubygem-json_pure-1.8.2 rubygem-journey-1.0.4 rubygem-i18n-0.7.0,2
rubygem-erubis-2.7.0_1 rubygem-builder-3.0.4 rubygem-activesupport-3.2.21
rubygem-activemodel-3.2.21 ruby21-gems-2.4.7 ruby-2.1.6ruby-2.1.6,1 
which are all the ruby related packages.

So after applying the above, the problem is reproduced via:
cd /usr/ports/security/metasploit
make -DBATCH clean deinstall package

This is a one off test, as we don't incrementally build packages (historical
reasons) we blow everything away before a major rebuild and currently build
600+ packages successfully but only metasploit uses ruby and hence failing,
which appear to be due to doc or rdoc issues with different dependences over
time.
(blow away means: pkg delete -f -y -a; rm -R $WRKDIRPREFIX/* $STAGEDIR/* )

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199107-13-2WJvCpLIbi>