Your message dated Sun, 3 Mar 2019 20:35:55 +0100 with message-id <7b603213-96c5-8056-b6d3-7b2c7a62a7f6@debian.org> and subject line close release-notes bugs for releases before stretch has caused the Debian Bug report #706610, regarding no migration from isdn4linux to mISDN possible: there is no userland 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 owner@bugs.debian.org immediately.) -- 706610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706610 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Cc: isdn4linux@listserv.isdn4linux.de
- Subject: Migration guide from isdn4linux to mISDN
- From: Andrey Gursky <andrey.gursky@e-mail.ua>
- Date: Thu, 2 May 2013 13:18:53 +0200
- Message-id: <CABg52Hn1wmR_-_c_-=hvympo-8Pp0suHB1rV2NG5gHq0s5J3Yw@mail.gmail.com>
Package: release-notes Severity: normal Tags: wheezy help Release notes don't mention for now, that the ISDN subsystem in new kernel series has been switched from isdn4linux to mISDN. E.g. using isdn4linux with hisax (HFC 2BDS0), one needs isdnutils-base and ipppd packages. In /etc/isdn/device.ippp0 and /etc/isdn/ipppd.ippp0 remotemsn and remotename should be set. The ordinary user can connect to ISP with /usr/sbin/isdnctrl dial ippp0, disconnect with /usr/sbin/isdnctrl hangup ippp0. The current state can be checked with /usr/sbin/isdnctrl status ippp0. I suppose, release notes should contain the information, whether all cards/chips supported by isdn4linux are of course also supported by mISDN, or if not, what would be the best workaround. And how the setup of connection to ISP, described above, could be achieved with mISDN. Thanks, Andrey
--- End Message ---
--- Begin Message ---
- To: 706610-done@bugs.debian.org, 762026-done@bugs.debian.org, 783232-done@bugs.debian.org, 783235-done@bugs.debian.org, 803356-done@bugs.debian.org, 683698-done@bugs.debian.org, 699754-done@bugs.debian.org, 706217-done@bugs.debian.org, 769388-done@bugs.debian.org, 774563-done@bugs.debian.org, 706131-done@bugs.debian.org, 617982-done@bugs.debian.org, 708135-done@bugs.debian.org, 610194-done@bugs.debian.org, 713914-done@bugs.debian.org, 770533-done@bugs.debian.org
- Subject: close release-notes bugs for releases before stretch
- From: Paul Gevers <elbrus@debian.org>
- Date: Sun, 3 Mar 2019 20:35:55 +0100
- Message-id: <7b603213-96c5-8056-b6d3-7b2c7a62a7f6@debian.org>
Hi, We are sorry that we were not able to handle your contribution or suggestion for changes to the release-notes. I am going over old bugs and I am closing all the items that were suggested for the release-notes of Debian releases before stretch. On the good side, some even appear to have been applied, without the bug being closed. Please don't hesitate to open a new bug if you think your suggestion is still valuable for the release-notes of buster. If you do that, we'd appreciate it when you try to summarize the issue properly when the closed bug was more than a couple of messages. PaulAttachment: signature.asc
Description: OpenPGP digital signature
--- End Message ---