Bug#253106: marked as done (netcfg: Please say what happens if DHCP not retried)
Your message dated Tue, 22 Jun 2004 08:09:54 +1000
with message-id <1087855794.866.101.camel@aurich.ostfriesland>
and subject line (forw) Bug#253106: Fixed?
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; 7 Jun 2004 09:14:08 +0000
>From christian.perrier@onera.fr Mon Jun 07 02:14:08 2004
Return-path: <christian.perrier@onera.fr>
Received: from onera.onera.fr [144.204.65.4]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BXGCm-0001Xo-00; Mon, 07 Jun 2004 02:14:08 -0700
Received: from cc-mykerinos.onera (localhost [127.0.0.1])
by onera.onera.fr with ESMTP id i579E6vZ000181;
Mon, 7 Jun 2004 11:14:06 +0200 (MEST)
Received: from localhost (mykerinos.onera [127.0.0.1])
by cc-mykerinos.onera (Postfix) with ESMTP id 5279723281;
Mon, 7 Jun 2004 11:14:06 +0200 (CEST)
Received: from cc-mykerinos.onera ([127.0.0.1])
by localhost (mykerinos [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 21847-03; Mon, 7 Jun 2004 11:13:46 +0200 (CEST)
Received: by cc-mykerinos.onera (Postfix, from userid 7426)
id 9150B23279; Mon, 7 Jun 2004 11:13:46 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Christian Perrier <bubulle@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: netcfg: Please be more specific about what happens when not retrying HDCP
X-Mailer: reportbug 2.61
Date: Mon, 07 Jun 2004 11:13:46 +0200
Message-Id: <[🔎] 20040607091346.9150B23279@cc-mykerinos.onera>
X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at mykerinos
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(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_2004_03_25
X-Spam-Level:
Package: netcfg
Severity: normal
Reported initally by Andree Leidenfrost:
Dear all
The DHCP retry screen in d-i implies that there is a DHCP server
available in the user's network and offers to retry. It fails to mention
what to do if there is no DHCP server available in the first place which
should not be uncommon.
And indeed, d-i takes perfect care of situations where there is no DHCP
to be found by asking the user to specify the network configuration
manually. Unfortunately, the DHCP retry screen completely fails to
mention this fact which may potentially confuse users.
Andree suggested adding something like this to this template.
"If you do not choose this option, you will be prompted to configure
the network manually."
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.6-1-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (ignored: LC_ALL set to fr_FR.UTF-8)
---------------------------------------
Received: (at 253106-done) by bugs.debian.org; 21 Jun 2004 22:17:06 +0000
>From aleidenf@bigpond.net.au Mon Jun 21 15:17:06 2004
Return-path: <aleidenf@bigpond.net.au>
Received: from gizmo01bw.bigpond.com [144.140.70.11]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1BcX69-00012G-00; Mon, 21 Jun 2004 15:17:06 -0700
Received: (qmail 15989 invoked from network); 21 Jun 2004 22:00:49 -0000
Received: from unknown (HELO bwmam07.bigpond.com) (144.135.24.87)
by gizmo01bw.bigpond.com with SMTP; 21 Jun 2004 22:00:49 -0000
Received: from cpe-138-130-32-93.nsw.bigpond.net.au ([138.130.32.93]) by bwmam07.bigpond.com(MAM REL_3_4_2a 56/32995928) with SMTP id 32995928; Tue, 22 Jun 2004 08:09:54 +1000
Subject: Re: (forw) Bug#253106: Fixed?
From: Andree Leidenfrost <aleidenf@bigpond.net.au>
To: 253106-done@bugs.debian.org
Cc: jdthood@aglu.demon.nl, Christian Perrier <bubulle@kheops.frmug.org>
In-Reply-To: <20040621162131.GC31857@mykerinos.kheops.frmug.org>
References: <20040621162131.GC31857@mykerinos.kheops.frmug.org>
Content-Type: text/plain
Organization: private
Message-Id: <1087855794.866.101.camel@aurich.ostfriesland>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6
Date: Tue, 22 Jun 2004 08:09:54 +1000
Content-Transfer-Encoding: 7bit
Delivered-To: 253106-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(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_2004_03_25
X-Spam-Level:
Excellent! Thanks a lot Christian & Thomas!
Cheers
Andree
On Tue, 2004-06-22 at 02:21, Christian Perrier wrote:
> Andree, you're the real original bug reporter. I am the submitter but
> just acted here as a relay.
>
> DO you consider the following template solves the issue reported in 253106?
>
> If you consider this fixed, just answer to 253106-done@bugs.debian.org
>
> On my side, I consider this is OK.
>
> ----- Forwarded message from Thomas Hood <jdthood@aglu.demon.nl> -----
>
> Subject: Bug#253106: Fixed?
> Reply-To: Thomas Hood <jdthood@aglu.demon.nl>, 253106-quiet@bugs.debian.org
> From: Thomas Hood <jdthood@aglu.demon.nl>
> To: 253106-submitter@bugs.debian.org
> X-Mailer: Ximian Evolution 1.4.6
> Date: Mon, 21 Jun 2004 12:26:08 +0200
>
> Has this been fixed? The current text is: // Thomas Hood
>
> Template: netcfg/dhcp_retry
> Type: select
> __Choices: Retry network autoconfiguration, Retry network
> autoconfiguration with a DHCP hostname, Configure network manually,
> ${wifireconf}, Do not configure the network at this time
> Default: Configure network manually
> _Description: Network configuration method:
> Network autoconfiguration failed. This may be due to a slow DHCP
> server on the network, so you may want to retry. If your network does
> not use DHCP for autoconfiguration, you can instead configure it
> manually. Also, some DHCP servers need a specific DHCP hostname, so
> you can choose to enter such a hostname before retrying DHCP.
>
>
>
> ----- End forwarded message -----
--
Andree Leidenfrost
Sydney - Australia
Reply to: