Bug#383081: Inclusion of sample zaptel.conf breaks successful installation of zaptel

Tzafrir Cohen tzafrir.cohen at xorcom.com
Sun Feb 11 04:50:39 UTC 2007


On Tue, Aug 15, 2006 at 12:54:18AM +0200, neoXite wrote:
> Package: zaptel
> Version: 1.2.7.dfsg-4
> 
> dpkg installs zaptel and complains about missing zaptel modules, the 
> zaptel-module packages depend on zaptel though. Deleting the packaged 
> /etc/zaptel.conf file and running 'apt-get -f install' fixed the problem 
> for me. Is it possible to change dpkg's behavior so that zaptel's init.d 
> script is not being executed during install? Most likely zaptel.conf 
> would require manual customization anyway.
> 
> Here's the error:
> 
> neoxite at debian:~/devel/debs$ sudo dpkg -i zaptel_1.2.7.dfsg-4_i386.deb
> Selecting previously deselected package zaptel.
> (Reading database ... 43406 files and directories currently installed.)
> Unpacking zaptel (from zaptel_1.2.7.dfsg-4_i386.deb) ...
> Setting up zaptel (1.2.7.dfsg-4) ...
> Zaptel cards initial configuration: FATAL: Module ztdummy not found.
> Notice: Configuration file is /etc/zaptel.conf
> line 0: Unable to open master device '/dev/zap/ctl'
> 
> 1 error(s) detected
> 
> invoke-rc.d: initscript zaptel, action "start" failed.
> dpkg: error processing zaptel (--install):
> subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
> zaptel

Fine. /etc/zaptel.conf should be placed by the user when the system is
actually has zaptel hardware and zaptel drivers. Note that this is not
required for a ztdummy-only setup.

This can also be done automatically with genzaptelconf .

I'll commit this one and see how this works.

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com       
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir



More information about the Pkg-voip-maintainers mailing list