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 #403190,
regarding misdn-modules-2.6.18-3-686: Freezes SMP systems
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.)
--
403190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403190
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: misdn-modules-2.6.18-3-686
Severity: important
Any systems I have access to with more than one CPU(-core) immediately lock
up completely immediately after inserting mISDN_core. May or may not be
related to
<http://www.isdn4linux.de/pipermail/isdn4linux/2006-November/002641.html>.
The symptoms there sound very similar.
Note: Makes no difference whether I use the precompiled modules or rebuild
with module-assistant, same results.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
--- 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 ---
