Your message dated Sat, 17 Dec 2005 16:05:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#343429: www.debian.org: changelog for
kernel-image-2.6.8-2-k7 (2.6.8-16sarge1) not found
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; 15 Dec 2005 08:46:05 +0000
>From [EMAIL PROTECTED] Thu Dec 15 00:46:05 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp.dnainternet.net ([62.241.254.111])
by spohr.debian.org with esmtp (Exim 4.50)
id 1EmokX-0002zD-7G
for [EMAIL PROTECTED]; Thu, 15 Dec 2005 00:46:05 -0800
Received: from dsl-083-102-065-239.lohjanpuhelin.fi ([83.102.65.239]:37742
"EHLO localhost.localdomain" smtp-auth: <none> TLS-CIPHER: "DES-CBC3-SHA
keybits 168/168 version TLSv1/SSLv3" TLS-PEER-CN1: <none>)
by smtp2.dnainternet.net with ESMTPS id S1232130AbVLOIqB (ORCPT
<rfc822;[EMAIL PROTECTED]>); Thu, 15 Dec 2005 10:46:01 +0200
Received: from m by localhost.localdomain with local (Exim 4.50)
id 1EmokR-0001Yr-D5
for [EMAIL PROTECTED]; Thu, 15 Dec 2005 10:45:59 +0200
Date: Thu, 15 Dec 2005 10:45:59 +0200
From: Markus =?iso-8859-1?Q?J=E4rvinen?= <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: www.debian.org: changelog for kernel-image-2.6.8-2-k7 (2.6.8-16sarge1)
not found
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 3.8
User-Agent: Mutt/1.5.9i
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=-7.0 required=4.0 tests=BAYES_01,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: www.debian.org
Severity: normal
Result of clicking the "Debian changelog" link at
<http://packages.debian.org/stable/base/kernel-image-2.6.8-2-k7>:
Not Found
The requested URL
/changelogs/pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-16sarge1/changelog
was not found on this server.
---------------------------------------
Received: (at 343429-done) by bugs.debian.org; 17 Dec 2005 15:05:04 +0000
>From [EMAIL PROTECTED] Sat Dec 17 07:05:04 2005
Return-path: <[EMAIL PROTECTED]>
Received: from higgs.djpig.de ([213.133.98.126])
by spohr.debian.org with esmtp (Exim 4.50)
id 1EndcO-0001bf-By
for [EMAIL PROTECTED]; Sat, 17 Dec 2005 07:05:04 -0800
Received: from djpig by higgs.djpig.de with local (Exim 4.50)
id 1EndcK-0007pV-Vw
for [EMAIL PROTECTED]; Sat, 17 Dec 2005 16:05:01 +0100
Date: Sat, 17 Dec 2005 16:05:00 +0100
From: Frank Lichtenheld <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#343429: www.debian.org: changelog for kernel-image-2.6.8-2-k7
(2.6.8-16sarge1) not found
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.9i
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
On Thu, Dec 15, 2005 at 10:45:59AM +0200, Markus Järvinen wrote:
> Result of clicking the "Debian changelog" link at
> <http://packages.debian.org/stable/base/kernel-image-2.6.8-2-k7>:
>
> Not Found
> The requested URL
> /changelogs/pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-16sarge1/changelog
> was not found on this server.
Seems to have been a temporary issue, can happen with the current code
when a security update is uploaded in a certain timeframe. Fixing this
is more of a long term todo item so not leaving the bug open for it.
Gruesse,
--
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
