Your message dated Thu, 26 May 2005 19:02:26 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#310575: fixed in kernel-patch-relayfs 2.6.9-2
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; 24 May 2005 12:22:36 +0000
>From [EMAIL PROTECTED] Tue May 24 05:22:36 2005
Return-path: <[EMAIL PROTECTED]>
Received: from egg.area.ba.cnr.it [150.145.80.53]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DaYQd-0004IV-00; Tue, 24 May 2005 05:22:36 -0700
Received: from localhost (localhost [127.0.0.1])
by egg.area.ba.cnr.it (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id
j4OCMXl8014464
for <[EMAIL PROTECTED]>; Tue, 24 May 2005 14:22:33 +0200
Received: from klecker (klecker.ba.issia.cnr.it [150.145.84.32])
by egg.area.ba.cnr.it (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id
j4OCLtqm014435
for <[EMAIL PROTECTED]>; Tue, 24 May 2005 14:21:55 +0200
Received: from [150.145.84.201] (helo=localhost.localdomain)
by klecker with esmtpa (Exim 4.50)
id 1DaYPz-0005m7-Ac
for [EMAIL PROTECTED]; Tue, 24 May 2005 14:21:55 +0200
Received: from frankie by localhost.localdomain with local (Exim 4.50)
id 1DaYQL-0002bd-DM
for [EMAIL PROTECTED]; Tue, 24 May 2005 14:22:17 +0200
From: Francesco Paolo Lovergine <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: 'kernel-patch-relayfs' does not apply to any current sarge kernel
X-Mailer: debmassmailer(0.2)
Message-Id: <[EMAIL PROTECTED]>
Date: Tue, 24 May 2005 14:22:17 +0200
X-Virus-Scanned: by amavisd-new-20041102+Sophos at egg.area.ba.cnr.it
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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: kernel-patch-relayfs
Version: 2.6.9-1
Severity: grave
Dear Yann Dirson
As reported in http://people.debian.org/~frankie/kernel-patches-checks.txt,
kernel-patch-relayfs does not
apply clean to a current kernel-source. If you think this package is anyway
useful at least with
an up-to-date vanilla kernel and sure that it applies properly, feel free to
document this in the
package and reduce the severity of this report, else this kernel-patch will be
hinted for
removing in sarge.
See also this ML thread about the issue:
http://lists.debian.org/debian-release/2005/05/msg01325.html
--
Francesco P. Lovergine
---------------------------------------
Received: (at 310575-close) by bugs.debian.org; 26 May 2005 23:08:02 +0000
>From [EMAIL PROTECTED] Thu May 26 16:08:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DbRSM-0004mx-00; Thu, 26 May 2005 16:08:02 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DbRMw-000534-00; Thu, 26 May 2005 19:02:26 -0400
From: Yann Dirson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#310575: fixed in kernel-patch-relayfs 2.6.9-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 26 May 2005 19:02:26 -0400
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-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Source: kernel-patch-relayfs
Source-Version: 2.6.9-2
We believe that the bug you reported is fixed in the latest version of
kernel-patch-relayfs, which is due to be installed in the Debian FTP archive:
kernel-patch-relayfs_2.6.9-2.dsc
to pool/main/k/kernel-patch-relayfs/kernel-patch-relayfs_2.6.9-2.dsc
kernel-patch-relayfs_2.6.9-2.tar.gz
to pool/main/k/kernel-patch-relayfs/kernel-patch-relayfs_2.6.9-2.tar.gz
kernel-patch-relayfs_2.6.9-2_all.deb
to pool/main/k/kernel-patch-relayfs/kernel-patch-relayfs_2.6.9-2_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yann Dirson <[EMAIL PROTECTED]> (supplier of updated kernel-patch-relayfs
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 27 May 2005 01:00:53 +0200
Source: kernel-patch-relayfs
Binary: kernel-patch-relayfs
Architecture: source all
Version: 2.6.9-2
Distribution: unstable
Urgency: high
Maintainer: Yann Dirson <[EMAIL PROTECTED]>
Changed-By: Yann Dirson <[EMAIL PROTECTED]>
Description:
kernel-patch-relayfs - High-Speed Data Relay Filesystem
Closes: 310575
Changes:
kernel-patch-relayfs (2.6.9-2) unstable; urgency=high
.
* Urgency high to fix trivial RC bug in sarge.
* Declared that the 2.6.9 patch also applies to 2.6.8, both vanilla and
debian 2.6.8-16 (Closes: #310575).
Files:
e2b441f301f828d09f7d62aa030dda70 559 devel extra
kernel-patch-relayfs_2.6.9-2.dsc
aaffbf02e416a9f5f79b30206844234b 142033 devel extra
kernel-patch-relayfs_2.6.9-2.tar.gz
21d55d459ddce5b3b2f93bfd6eade22e 160290 devel extra
kernel-patch-relayfs_2.6.9-2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCllVyV1uVslwzwbgRAktJAKCQ8QkeaPWWzJXa86aMX6IplHXCbQCfU/t9
/S96bIzJYuqsqPqofrO767w=
=bdaA
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
