Your message dated Wed, 21 Sep 2005 16:00:46 -0600
with message-id <[EMAIL PROTECTED]>
and subject line WNPP bug closing
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 26 Jan 2004 03:28:26 +0000
>From [EMAIL PROTECTED] Sun Jan 25 19:28:26 2004
Return-path: <[EMAIL PROTECTED]>
Received: from floyd.blarg.net (mail.blarg.net) [206.124.128.8]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AkxQI-0002jQ-00; Sun, 25 Jan 2004 19:28:26 -0800
Received: from 192.168.129.100 (vp155.atm01.sea.blarg.net [206.124.138.155])
by mail.blarg.net (Postfix) with ESMTP id 5F81C38796
for <[EMAIL PROTECTED]>; Sun, 25 Jan 2004 19:28:06 -0800 (PST)
From: Ian Eure <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: jackd: Requires unpackaged kernel patch to operate
Date: Sun, 25 Jan 2004 19:10:38 -0800
User-Agent: KMail/1.5.4
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_01_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no
version=2.60-bugs.debian.org_2004_01_25
X-Spam-Level:
Package: jackd
Version: 0.021123-1
Severity: normal
*** Please type your report below this line ***
When I try to start jack (with 'jackstart' as root) I get this error:
jackstart: cannot get realtime capabilities, current capabilities are:
=ep cap_setpcap-ep
probably running under a kernel with capabilities disabled,
a suitable kernel would have printed something like "=eip"
According to the jack site, a two-line kernel patch is required for jack
to operate. This patch does not appear to be packaged, and no direct
mention of it is mentioned in the README.Debian.
I believe that the patch should be packaged, or included with the jackd
package, and a mention of it should be placed in README.Debian.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux hadron 2.4.24-hadron #1 Mon Jan 19 03:48:00 PST 2004 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages jackd depends on:
ii libasound2 0.9.8-2 Advanced Linux Sound Architecture
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries
an
ii libcap1 1:1.10-13 support for getting/setting
POSIX.
ii libjack0 0.021123-1 JACK Audio Connection Kit
(librari
-- no debconf information
---------------------------------------
Received: (at 229709-done) by bugs.debian.org; 21 Sep 2005 22:00:47 +0000
>From [EMAIL PROTECTED] Wed Sep 21 15:00:47 2005
Return-path: <[EMAIL PROTECTED]>
Received: from merkel.debian.org [192.25.206.16] (mail)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EICdz-00056H-00; Wed, 21 Sep 2005 15:00:47 -0700
Received: from damog by merkel.debian.org with local (Exim 3.36 1 (Debian))
id 1EICdy-0004PO-00; Wed, 21 Sep 2005 16:00:46 -0600
To: [EMAIL PROTECTED]
Subject: WNPP bug closing
Message-Id: <[EMAIL PROTECTED]>
From: David Moreno Garza <[EMAIL PROTECTED]>
Date: Wed, 21 Sep 2005 16:00:46 -0600
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,VALID_BTS_CONTROL
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Hello,
This is an automatic mail sent to close the RFP you have reported or
are involved with.
Your RFP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 450 days.
- It hasn't had any activity recently.
As this an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not
intended by owners and submitters (like you) to be closed, for
example if the RFP is still of your interest, or there has been
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).
To re-open it, you simply have to mail [EMAIL PROTECTED]
with a body text like this:
reopen 229709
thanks bts
Further comments on the work done in the bug sent to
[EMAIL PROTECTED] would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <[EMAIL PROTECTED]>.
This is the second massive wnpp closing that is being done. The next close
will be done on inactive RFPs older than 365 days and finally, an automatic
script will close, by default, *inactive* RFPs when they reach one year of
inactivity.
A similar process is being applied to other kind of wnpp bugs.
Thanks for your cooperation,
-- David Moreno Garza <[EMAIL PROTECTED]> Wed, 20 Sep 2005 17:06:42 -0500
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
