Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 132348 - Zaptel 1.2.5 ebuild Doesn't add asterisk user to dialout group
Summary: Zaptel 1.2.5 ebuild Doesn't add asterisk user to dialout group
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: voip herd (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-05 06:57 UTC by Bill Lewis
Modified: 2006-10-30 16:04 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
asterisk-1.2.9_p1.ebuild.patch (asterisk-1.2.9_p1.ebuild.patch,359 bytes, patch)
2006-07-14 00:57 UTC, Daniel Black (RETIRED)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Bill Lewis 2006-05-05 06:57:22 UTC
Essentially, when emerging zaptel 1.2.5 the hardware is not accessible from asterisk.  The problem was clearly a permissions issue with the devices (udev).  I added the user "asterisk" to the "dialout" group and problem solved - should be fixed in the ebuild I would imagine.

Here's my system basics:

Portage 2203-svn (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.3.6-r3, 2.6.16-gentoo-r3 i686)
=================================================================
System uname: 2.6.16-gentoo-r3 i686 Pentium III (Coppermine)
Gentoo Base System version 1.6.14
dev-lang/python:     2.4.2
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
Comment 1 Daniel Black (RETIRED) gentoo-dev 2006-07-14 00:57:27 UTC
Created attachment 91688 [details, diff]
asterisk-1.2.9_p1.ebuild.patch
Comment 2 Piotr Jaroszyński (RETIRED) gentoo-dev 2006-10-30 16:04:21 UTC
1.2.5 is no longer in the tree and the error seems to be solved in newer versions.