Bug 186573 - Latest Update to bsd.ruby.mk Breaks `portsnap update`
Summary: Latest Update to bsd.ruby.mk Breaks `portsnap update`
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ruby (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-09 02:50 UTC by Ryan Frederick
Modified: 2014-02-09 14:52 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Frederick 2014-02-09 02:50:00 UTC 
The latest update to /usr/ports/Mk/bsd.ruby.mk breaks portsnap's ability to update the local ports tree with the following error:

"/usr/ports/Mk/bsd.ruby.mk", line 561: Unassociated shell command "${SETENV} ${MAKE_ENV} ${RUBY} ${RUBY_FLAGS} ${RUBY_SETUP} install --prefix=${STAGEDIR}"
"/usr/ports/Mk/bsd.port.mk", line 6613: if-less endif
make: fatal errors encountered -- cannot continue

===>>> Is /usr/ports/lang/ruby19/Makefile missing?
===>>> Aborting update
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2014-02-09 02:50:08 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->ruby

bsd.ruby.mk is ruby territory (via the GNATS Auto Assign Tool)
Comment 2 Ryan Frederick 2014-02-09 02:53:38 UTC 
Actually, it's `portmaster -a` that is broken by this, not `portsnap
update`. My apologies.
Comment 3 Ryan Frederick 2014-02-09 03:28:44 UTC 
This has been corrected by Colin Percival. The culprit ended up being a
trailing newline that broke INDEX.
Comment 4 Steve Wills freebsd_committer freebsd_triage 2014-02-09 14:52:37 UTC 
State Changed
From-To: open->closed

Fixed by r343421