upgrade issue with configured asterisk

[Jeff Waugh]

If asterisk configuration changes are made that include configuration file deletion, asterisk cannot be upgraded.

Setting up asterisk-classic (1.2.7.1.dfsg-2ubuntu3.1) ...
chown: cannot access `/etc/asterisk/voicemail.conf': No such file or directory
dpkg: error processing asterisk-classic (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of asterisk:

[Jeff Waugh (jdub)]

This effects the recent security update on dapper.

[Lionel Porcheron (lionel.porcheron)]

In fact, the only file concerns is voicemail.conf. The asterisk-classic.postinst script assumes that voicemail.conf exists.

This script in the edgy version has been rewritten and the problem is not present anymore.

[Lionel Porcheron (lionel.porcheron)]

Here is a quick patch that solves the problem. I am not sure that we should apply this, it only concers people who removed / rename voicemail.conf and the bug is not present anymore on Edgy.

[Martin Pitt (pitti)]

Patch looks fine for dapper-updates. Can be applied when the *-updates embargo is lifted again.

[Chris Rose (chris-vault5)]

William, why was this marked as Fix Released? The fix has not yet been published.

With yesterdays security update to Asterisk I suspect a few people will hit this bug soon. It is common practice to remove the asterisk configs that you do not use, so I don't see any reason to not publish this fix in dapper.

[William Grant (wgrant)]

Firstly, please don't assign to MOTU. That takes it off the unassigned list, and puts it on a list that few check. Secondly, the fix HAS been released, in the development version. I attempted to add a Dapper task some time ago, but was restricted by the new release management system. A core-dev needs to add the Dapper task now.

[Chris Rose (chris-vault5)]

OK, thanks. I will try and find someone from the core team to get the update into dapper.