From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Deniz Dogan Newsgroups: gmane.emacs.devel Subject: Re: 404 when trying to access some bug reports Date: Tue, 5 Jan 2010 23:34:32 +0100 Message-ID: <7b501d5c1001051434o2f8b9e77id00fff6cd68335bf@mail.gmail.com> References: <7b501d5c0912281331u3a68ef7fn39b76c1c7c33e03f@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: ger.gmane.org 1262738549 21014 80.91.229.12 (6 Jan 2010 00:42:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 6 Jan 2010 00:42:29 +0000 (UTC) Cc: Emacs-Devel devel To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 06 01:42:22 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NSJyd-0007Gf-F3 for ged-emacs-devel@m.gmane.org; Wed, 06 Jan 2010 01:42:19 +0100 Original-Received: from localhost ([127.0.0.1]:44359 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NSJyd-0008UQ-Sx for ged-emacs-devel@m.gmane.org; Tue, 05 Jan 2010 19:42:19 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NSHzS-0004lO-OK for emacs-devel@gnu.org; Tue, 05 Jan 2010 17:35:02 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NSHzO-0004hW-54 for emacs-devel@gnu.org; Tue, 05 Jan 2010 17:35:02 -0500 Original-Received: from [199.232.76.173] (port=34925 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NSHzN-0004hH-PK for emacs-devel@gnu.org; Tue, 05 Jan 2010 17:34:57 -0500 Original-Received: from mail-ew0-f224.google.com ([209.85.219.224]:59074) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NSHzL-00033v-E3; Tue, 05 Jan 2010 17:34:55 -0500 Original-Received: by ewy24 with SMTP id 24so19748740ewy.26 for ; Tue, 05 Jan 2010 14:34:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=HFaVVHslKZMGpBmCXFzUwhx429bXKmDWVOR24zBaRGs=; b=YaKwbgEj1o82ri4nSlLjZsM5nnp5Hcm7ZioZ+vYd2EN7DBIdNfcAHPXoy8Y4FYQdtT dve+tN+2D/a1wJNg4DpjMQLgOgn4xtaiGI+FQ33a5lL7tPe7cidnhU5piKuLZ9StkSQd g36JaBjUQjQtC5d4FoK1xBOeh0nfOsrmdbxVA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=NMRMJ0BKLwDGWt0NFwHqOp686sMpAa9Sp41lk5hbwMTlNdjDGn+xxmPjeg6sYAfWr0 wbw6Foy0sR5fGc0Ysnqs8UdQAY2NhaEGqpv4lHEaJovQN0PICoJEJfLtZwAHLw1pccej QKE3QXr7lbToxsrUko7mTu0V3PDodvRKDi9y0= Original-Received: by 10.213.99.81 with SMTP id t17mr4451207ebn.53.1262730892154; Tue, 05 Jan 2010 14:34:52 -0800 (PST) In-Reply-To: X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:119482 Archived-At: 2010/1/5 Glenn Morris : > Deniz Dogan wrote: > >> The full list of Emacs bugs: http://debbugs.gnu.org/db/pa/lemacs.html >> For example, bug 5128 is listed there, but >> http://debbugs.gnu.org/db/51/5128.html gives me 404. Looking for it in >> http://debbugs.gnu.org/db/51/ reveals that the file does not exist. > > I re-ran the relevant thing by hand, and the files seem to have > re-appeared now. > > There is some caching and time-stamping, and I am not sure how often > those pages are really updated. Maybe there was a transient glitch > that prevented the script completing. > > Whilst the static index is the best/only way to see _all_ bugs, I > think the dynamic pages are the best way to see individual reports. > I believe Chong posted something about the same issue (but not as a reply to this, for some reason) and that he eventually resolved it. -- Deniz Dogan