We are getting when migrating from ngcp-asterisk to stock asterisk on mr4.3
> dpkg: error processing archive /var/cache/apt/archives/asterisk-modules_1%3a11.13.1~dfsg-2+b1_amd64.deb (--unpack):
> trying to overwrite '/usr/lib/asterisk/modules/app_echo.so', which is also in package ngcp-asterisk 1.4.24.1+ngcp.9+0~mr4.3.0.0+0~20151216080251.270+jessie~1.gbp484dd0
Change-Id: Ie9b73444b2026b82892388299b25a1678551d516
(cherry picked from commit 22c336d76a)
Our ngcp-asterisk package ships files that are also shipped with
Debian's official asterik (related) packages like
asterisk-modules, so those packages can't be installed at the
same time.
Change-Id: Ia13608081fa0a74db8bbb1a18791378195341ca1
Otherwise it looks like a package with orig sources sitting in
a foreign tree to git-buildpackage:
| + git-buildpackage -nc --git-force-create --git-ignore-new -S -us -uc --git-verbose --git-builder=/bin/true --git-cleaner=/bin/true
| /bin/true [] []
| fatal: Not a valid object name upstream/1.4.24.1
| ngcp-asterisk_1.4.24.1.orig.tar.gz does not exist, creating from 'upstream'
Moving to this version number schema instead fixes the
build issue.
Closes: https://jenkins.mgm.sipwise.com/job/asterisk-source/81/
This makes reviews and diffs easier and helps in avoiding duplicate entries.
devscripts's wrap-and-sort ftw.
Closes: https://bugtracker.sipwise.com/view.php?id=1845
From: Michael Prokop <mprokop@sipwise.com>
Somehow looks like asterisk does not like a start
when it'sa already started. I never had any
issues but read about it. It's safe to check
status before running start.
Still need to work in asterisk restart upon
upgrades. And how to deal with monit for that.