From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: RE: Bugs cannot be updated if they are archived? Date: Sun, 14 Dec 2008 17:00:31 +0900 Message-ID: <87bpvf89uo.fsf@xemacs.org> References: <007401c95d6b$107a1590$0200a8c0@us.oracle.com> <20081213230827.GQ24493@volo.donarmstrong.com> <008501c95d7e$932b4a00$0200a8c0@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1229241355 6304 80.91.229.12 (14 Dec 2008 07:55:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 14 Dec 2008 07:55:55 +0000 (UTC) Cc: control@emacsbugs.donarmstrong.com, 'Don Armstrong' , emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 14 08:57:00 2008 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 1LBlqV-0005Kj-F7 for ged-emacs-devel@m.gmane.org; Sun, 14 Dec 2008 08:56:59 +0100 Original-Received: from localhost ([127.0.0.1]:59562 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LBlpJ-0002uZ-Pd for ged-emacs-devel@m.gmane.org; Sun, 14 Dec 2008 02:55:45 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LBlpE-0002sd-49 for emacs-devel@gnu.org; Sun, 14 Dec 2008 02:55:40 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LBlpC-0002rv-0o for emacs-devel@gnu.org; Sun, 14 Dec 2008 02:55:39 -0500 Original-Received: from [199.232.76.173] (port=47079 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LBlpB-0002rs-NR for emacs-devel@gnu.org; Sun, 14 Dec 2008 02:55:37 -0500 Original-Received: from mx20.gnu.org ([199.232.41.8]:12962) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LBlpB-0005RY-4s for emacs-devel@gnu.org; Sun, 14 Dec 2008 02:55:37 -0500 Original-Received: from mtps02.sk.tsukuba.ac.jp ([130.158.97.224]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LBlp9-0002Rd-MU for emacs-devel@gnu.org; Sun, 14 Dec 2008 02:55:35 -0500 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mtps02.sk.tsukuba.ac.jp (Postfix) with ESMTP id D3CE5820D; Sun, 14 Dec 2008 16:55:26 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 679B81388F7; Sun, 14 Dec 2008 17:00:31 +0900 (JST) In-Reply-To: <008501c95d7e$932b4a00$0200a8c0@us.oracle.com> X-Mailer: VM 8.0.12-devo-585 under 21.5 (beta28) "fuki" 83e35df20028+ XEmacs Lucid (x86_64-unknown-linux) X-detected-kernel: by mx20.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:106905 Archived-At: Drew Adams writes: > I see. I thought that any followup email, especially from the bug > filer, would be sufficient to keep a bug open (or reopen it). Some systems do work that way. Some don't. "He who does the work makes the decisions." > I clicked that URL link in my mail client and got this message from my Web > browser: > > "Internet Explorer cannot download server-control from > emacsbugs.donarmstrong.com. Internet Explorer was not able > to open this Internet site. The requested site is either > unavailable or cannot be found. Please try again later." > > Where can I find the instructions for reopening etc. bugs? Is there > another URL, which I might be able to get to? That URL works fine with any browser, including IE I'm sure. That message is highly unlikely to indicate a *browser* problem; it usually means that the DNS lookup failed. This regularly happens to me on Mac as well as Windows (with hosts that are provably up, simply by routing around the Mac- or Windows-induced failures). My guess is that their resolvers cache failures aggressively and apparently assume that if you miss the first time and try again, it's user brain damage rather than a temporary network glitch, so they don't bother to try the DNS. > Oh - I see - that the URL works in Google Chrome. So your site > appears to be limited to particular browsers (and excludes the most > commonly used browser). There's nothing Don can do about a nameservice failure in your system, so I don't see any justification for your tone.