Your message dated Wed, 4 Jul 2012 13:19:04 +0100
with message-id
<CAPQ4b8kH0+w8OfoKoA5=pyhmqu8k5fvkkztoi3cipw7k_az...@mail.gmail.com>
and subject line Closing orphan/obsolete bugs (misdn-related packages)
has caused the Debian Bug report #453270,
regarding Please package libsuppserv-dev
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
453270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453270
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: misdn-user
Version: 1.1.6-1
Severity: minor
--- Please enter the report below this line. ---
Hi!
Please, package suppserv header files as they are required to compile
chan_misdn module for Asterisk.
Thanks for your wonderful work!
Pau.
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.22-2-686
Debian Release: lenny/sid
990 testing www.debian-multimedia.org
990 testing snapshot.debian.net
990 testing ftp.es.debian.org
500 unstable ftp.es.debian.org
500 stable ftp.es.debian.org
1 experimental ftp.debian.org
--- Package information. ---
Depends (Version) | Installed
=======================-+-===========
|
--- End Message ---
--- Begin Message ---
Hello,
Thanks for your interest in improving Debian, and sorry that the bugs
were not fully resolved in due time.
misdn packages have been recently removed from experimental [1], they
had been removed from unstable a few years ago [2].
[1] http://packages.qa.debian.org/m/misdn-kernel/news/20120627T165811Z.html
[2] http://packages.qa.debian.org/m/misdn-kernel/news/20071201T181403Z.html
The bugs are now orphan (without maintainer assigned) so they probably
will not be noticed/modified further. So I think that the best
solution is to close them now, doing it. Please comment if you want
to handle the reports in some other way (reassigned to other packages,
etc.).
Cheers.
--- End Message ---
