email@example.com. Full text available.
Received: (at submit) by bugs.devuan.org; 18 Dec 2017 23:00:02 +0000 Date: Mon, 18 Dec 2017 23:57:02 +0100 From: Gregor Schaffrath <firstname.lastname@example.org> To: email@example.com Subject: asterisk-dahdi: MeetMe app should be reincluded Package: asterisk-dahdi Version: 1:11.13.1~dfsg-2+deb8u4 Severity: important Dear Maintainer, I noticed that app_meetme.so , originally part of the asterisk package first got shifted to asterisk-dahdi and subsequently omitted, as the (very old, very basic) app got a 'deprecated' status from upstream in asterisk-10. (compare: https://launchpad.net/debian/+source/asterisk/+changelog) However, the asterisk community figured that ommission of the app broke functionality of non-deprecated asterisk parts and reinstated the app as 'extended support'. (compare: https://issues.asterisk.org/jira/browse/ASTERISK-20134) The app itself is alive and being actively modified. (compare: https://wiki.asterisk.org/wiki/display/AST/Upgrading+to+Asterisk+11 ) Unfortunately, while Debian followed the shift to deprecated, the maintainer failed to notice/follow this second shift (I guess that he didn't follow bug reports for 'deprecated' apps ;) ). I'd like to request a reinclusion of the app in the Devuan repository. As I said: It's a very old, very stable, very reliable (and to me: very dear ;) ) app. -- System Information: Distributor ID: Devuan Description: Devuan GNU/Linux jessie Release: jessie Codename: n/a Architecture: x86_64 Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages asterisk-dahdi depends on: ii asterisk 1:11.13.1~dfsg-2+deb8u4 ii dahdi 1:184.108.40.206-1 ii libc6 2.19-18+deb8u10 ii libopenr2-3 1.3.3-1 ii libpri1.4 1.4.15-1 ii libss7-1 1.0.2-5 ii libtonezone2.0 1:220.127.116.11-1 asterisk-dahdi recommends no packages. asterisk-dahdi suggests no packages. -- no debconf information
Gregor Schaffrath <firstname.lastname@example.org>:
Your message specified a Severity: in the pseudo-header, but the severity value important was not recognised. The default severity normal is being used instead. The recognised values are: critical, grave, normal, minor, wishlist.
Full text available.
asterisk-dahdi. Full text available.