Bug 196350 - mail/exmh2: Error running Env_Init: invalid command name "Env_Init"
Summary: mail/exmh2: Error running Env_Init: invalid command name "Env_Init"
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Cy Schubert
Keywords: needs-qa
Depends on:
Reported: 2014-12-29 10:19 UTC by Greg Becker
Modified: 2015-01-14 20:58 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Greg Becker 2014-12-29 10:19:25 UTC
Running exmh after installing it with pkg reports:

$ exmh
Error running Env_Init: invalid command name "Env_Init"
This usually means exmh isn't installed right
Check the main exmh script for the CONFIGURATION section
and make sure exmh(library) is a valid absolute pathname

It appears this is due to lack of search permission on the exmh directory:

$ ls -ld /usr/local/lib/exmh-2.8.0
dr--r--r--  4 bin  bin  154 Dec 25 07:41 /usr/local/lib/exmh-2.8.0/

Enabling search permissions to the exmh directory allows it to work as expected:

$ sudo chmod +x /usr/local/lib/exmh-2.8.0 

You can repeat this by deinstalling then reinstalling exmh.

$ pkg version |grep exmh
exmh-2.8.0                         =

FWIW, happens on both 9.3-STABLE and 10.1-STABLE:

FreeBSD gromit.codeconcepts.com 9.3-STABLE FreeBSD 9.3-STABLE #2 r276299: Sat Dec 27 10:03:47 CST 2014     greg@gromit.codeconcepts.com:/usr/obj/usr/src/sys/GROMIT  amd64
Comment 1 commit-hook freebsd_committer 2015-01-14 20:58:17 UTC
A commit references this bug:

Author: cy
Date: Wed Jan 14 20:57:56 UTC 2015
New revision: 377043
URL: https://svnweb.freebsd.org/changeset/ports/377043

  Fix packaging permissions.

  PR:		196350

Comment 2 Cy Schubert freebsd_committer 2015-01-14 20:58:59 UTC