Bug 192446 - net-im/prosody port pulls in conflicting lua versions, can't run
Summary: net-im/prosody port pulls in conflicting lua versions, can't run
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: David Thiel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-06 16:14 UTC by phoffman
Modified: 2014-08-11 22:43 UTC (History)
1 user (show)

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 phoffman 2014-08-06 16:14:20 UTC 
When installing net-im/prosody from pkg or ports:

New packages to be INSTALLED:
	prosody: 0.9.4_1
	lua51-luaexpat: 1.3.0
	lua51-luasec: 0.5
	lua51-luasocket: 3.0r1
	lua51: 5.1.5_7
	lua52-luafilesystem: 1.6.2
	lua52: 5.2.3_2

All of those install just fine. But: note the two different versions of lua. This ends up causing you to not be able to use some of the prosody utilities:

# prosodyctl

**************************
Prosody was unable to find luafilesystem
This package can be obtained in the following ways:

	Source:           http://www.keplerproject.org/luafilesystem/
	Debian/Ubuntu:    sudo apt-get install liblua5.1-filesystem0
	luarocks:         luarocks install luafilesystem

luafilesystem is required for Prosody to run, so we will now exit.
More help can be found on our website, at http://prosody.im/doc/depends
**************************
Comment 1 John Marino freebsd_committer freebsd_triage 2014-08-06 21:04:42 UTC 
Over to maintainer
Comment 2 phoffman 2014-08-11 20:34:58 UTC 
If someone comes across this before the bug gets fixed: a workaround for the port bug is to install lua51-luafilesystem first, then do the install of prosody. At least, this works on FreeBSD 10.0.
Comment 3 phoffman 2014-08-11 22:43:18 UTC 
This appears to be a bad side-effect of a bug in "pkg update". When I was instructed to run "pkg update -f" for a different problem I was experiencing, the problem listed in this bug went away. I'm going to close the bug, but if others find this, maybe they can re-open it.