Opened 13 years ago
Closed 13 years ago
#31154 closed defect (worksforme)
clamav 0.97.2 build fails on lion 10.7.1, due to missing clamav user
Reported by: | felix.buenemann@… | Owned by: | danielluke (Daniel J. Luke) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.2 |
Keywords: | lion | Cc: | |
Port: | clamav |
Description
Build of clamav 0.97.2 fails on my 10.7.1 system, because the configure check for the clamav user fails:
:info:configure checking for clamav in /etc/passwd... checking for clamav using dscl... no :info:configure configure: error: User clamav (and/or group clamav) doesn't exist. Please read the documentation !
_clamav user and group are present in /etc/passwd and /etc/group, however _clamav user is not listed by dscl: /etc/passwd:_clamav:*:82:82:ClamAV Daemon:/var/virusmails:/usr/bin/false /etc/group:_clamav:*:82: /usr/bin/dscl . -list /Groups|grep clamav _clamav /usr/bin/dscl . -list /Users|grep clamav
Btw. I'm using macports-2.0.3 (not selectable yet in bug wizard)
Attachments (1)
Change History (4)
Changed 13 years ago by felix.buenemann@…
comment:1 Changed 13 years ago by felix.buenemann@…
Here is the grep/dscl output again, with whitespace preserved:
$ grep clamav /etc/passwd /etc/group /etc/passwd:_clamav:*:82:82:ClamAV Daemon:/var/virusmails:/usr/bin/false /etc/group:_clamav:*:82: $ /usr/bin/dscl . -list /Groups|grep clamav _clamav $ /usr/bin/dscl . -list /Users|grep clamav $
comment:2 Changed 13 years ago by danielluke (Daniel J. Luke)
Owner: | changed from macports-tickets@… to dluke@… |
---|---|
Status: | new → assigned |
That's interesting (that you have the clamav group but no clamav user). I'll have to get my 10.7 machine up and verify that it's gone there (and then update the portfile to create one on 10.7, I guess).
comment:3 Changed 13 years ago by danielluke (Daniel J. Luke)
Resolution: | → worksforme |
---|---|
Status: | assigned → closed |
I just installed lion on a second machine to check, and I have a _clamav user there, so I believe the problem is unique to your system.
build log