Bug 190713

Summary: editors/emacs is missing libxml2 dependency
Product: Ports & Packages Reporter: David Chisnall <theraven>
Component: Individual Port(s)Assignee: Ashish SHUKLA <ashish>
Status: Closed Unable to Reproduce    
Severity: Affects Many People CC: marino
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   

Description David Chisnall freebsd_committer freebsd_triage 2014-06-06 14:11:58 UTC 
Trying to run emacs after installing the emacs package gives this error:

$ emacs
Shared object "libxml2.so.2" not found, required by "emacs"

The libxml2 port installs libxml2.so.5, so I've no idea where libxml2.so.2 comes from.  Creating a symlink to the one installed by the libxml2 package allows emacs to launch, but I've no idea if it breaks some XML-related functionality.
Comment 1 John Marino freebsd_committer freebsd_triage 2014-06-11 15:54:13 UTC 
maybe it's just a failure of incremental building.
In other words, if all existing packages were deleted before building emacs, then it would be packaged correctly.

Which would imply something needed bumping that didn't get bumped.
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2014-06-13 03:16:37 UTC 
Over to maintainer.
Comment 3 Ashish SHUKLA freebsd_committer freebsd_triage 2014-06-13 16:44:56 UTC 
(In reply to David Chisnall from comment #0)
> Trying to run emacs after installing the emacs package gives this error:
> 
> $ emacs
> Shared object "libxml2.so.2" not found, required by "emacs"
> 
> The libxml2 port installs libxml2.so.5, so I've no idea where libxml2.so.2
> comes from.

I think it's from UPDATING entry 20140416, and most likely binary package is built with it as well.

> Creating a symlink to the one installed by the libxml2 package
> allows emacs to launch, but I've no idea if it breaks some XML-related
> functionality.

I think you should reinstall libxml2 as per the UPDATING entry.

HTH
Comment 4 David Chisnall freebsd_committer freebsd_triage 2014-06-14 10:50:06 UTC 
This appears to have been caused, on my system at least, by pkg finding the head and quarterly package repositories and mixing up the packages.  It would be nice to have a warning when that happened, but it's a separate bug.