Your message dated Fri, 17 Jun 2005 11:09:05 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#313654: debian-el: 'reportbug' child may require
first-time interaction
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 maintonly) by bugs.debian.org; 14 Jun 2005 20:50:08 +0000
>From [EMAIL PROTECTED] Tue Jun 14 13:50:08 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 209-204-169-32.dsl.static.sonic.net (luther.lothar.com)
[209.204.169.32]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1DiIMJ-0004Zw-00; Tue, 14 Jun 2005 13:50:08 -0700
Received: (qmail 10354 invoked from network); 14 Jun 2005 20:50:07 -0000
Received: from unknown (HELO localhost) (127.0.0.1)
by localhost.lan with SMTP; 14 Jun 2005 20:50:07 -0000
Date: Tue, 14 Jun 2005 13:50:07 -0700 (PDT)
Message-Id: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: debian-el: 'reportbug' child may require first-time interaction
X-Debbugs-CC: [EMAIL PROTECTED]
X-Mailer: Mew version 4.2 on Emacs 21.4 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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=-9.4 required=4.0 tests=BAYES_00,HAS_PACKAGE,
NO_REAL_NAME,X_DEBBUGS_CC autolearn=ham
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: debian-el
Version: 24.10-1
Severity: minor
I used M-x debian-bug for the first time in a few months today, and when it
went to spawn 'reportbug' (to gather information for the bug report email),
reportbug started complaining about how the editor I was using was not
recommended for novice users, and how I should probably change it, finishing
with an interactive query about launching update-alternatives now (Y|n|?).
debian-bug didn't like this.
It turned out that reportbug felt that it had never been run before. Running
it directly gave it an opportunity to ask me some configuration questions
(novice/expert/etc, what name/email to use on bugs). I assume that this is
new reportbug behavior.. I've filed bugs (via debian-bug) in the past without
problems, and I believe it's been using reportbug for a long time.
It would appear that when debian-el invokes a new reportbug installation (one
which has not yet had a chance to ask these questions), reportbug behaves
interactively, breaking debian-el. I suspect this is a problem in reportbug,
some --batch flag being ignored in the unconfigured case (I do not know how
reportbug is invoked), but since the only time you might be using reportbug
without actually running it by hand is when debian-bug invokes it, it seemed
better to file this bug against debian-el.
thanks,
-Brian
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages debian-el depends on:
ii binutils 2.15-6 The GNU assembler, linker and bina
ii emacs21 [emacsen] 21.4a-1warner0 The GNU Emacs editor
ii reportbug 3.12 reports bugs in the Debian distrib
-- no debconf information
---------------------------------------
Received: (at 313654-close) by bugs.debian.org; 17 Jun 2005 15:09:41 +0000
>From [EMAIL PROTECTED] Fri Jun 17 08:09:40 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp1.globetrotter.net [142.169.1.151]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DjITU-0004at-00; Fri, 17 Jun 2005 08:09:40 -0700
Received: from (192.168.250.8) by avas6.globetrotter.net via smtp
id 5e4d_8a918624_df42_11d9_9942_0002b3ee5772;
Fri, 17 Jun 2005 11:14:47 -0400
Received: from mixed.dyndns.org
(c207.134.112-144.clta.globetrotter.net [207.134.112.144])
by smtp1.globetrotter.net (iPlanet Messaging Server 5.2)
with ESMTP id <0II8003NJI36RX@"TELUS Quebec"> for
[EMAIL PROTECTED]; Fri, 17 Jun 2005 11:09:07 -0400 (EDT)
Received: from (207.134.112.144) by avas6.globetrotter.net via smtp id
5e4b_782c20fc_df42_11d9_8ab4_0002b3ee5772; Fri, 17 Jun 2005 11:14:16 -0400
Received: by mixed.dyndns.org (Postfix, from userid 1000) id E0C3583B2;
Fri,
17 Jun 2005 11:09:06 -0400 (EDT)
Received: from mixed (localhost [127.0.0.1]) by mixed.dyndns.org (Postfix)
with ESMTP id DD79A1674DF; Fri, 17 Jun 2005 11:09:06 -0400 (EDT)
Date: Fri, 17 Jun 2005 11:09:05 -0400
From: Peter S Galbraith <[EMAIL PROTECTED]>
Subject: Re: Bug#313654: debian-el: 'reportbug' child may require first-time
interaction
In-reply-to: <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
To: Brian Warner <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Message-id: <[EMAIL PROTECTED]>
Organization: Debian GNU/Linux - www.debian.org
X-Mailer: MH-E 7.84+cvs; nmh 1.1; GNU Emacs 21.3.50.1
Content-transfer-encoding: 7BIT
X-Image-URL: http://people.debian.org/~psg/face.png
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Comments: In-reply-to Brian Warner <[EMAIL PROTECTED]> message dated
"Thu, 16 Jun 2005 18:25:06 -0700."
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:
Brian Warner <[EMAIL PROTECTED]> wrote:
> > Can you try again using reportbug 3.13, which was uploaded only minutes
> > before you filled this bug report? It addresses the "vi' issue, but
> > perhaps there are still other questions?
>
> Yup, that takes care of it. Removing .reportbugrc and generating a new report
> with debian-bug behaves correctly (and doesn't bother creating a .reportbugrc
> either). Sorry about the noise, I should have checked the upload queue before
> sending the bug report.
No problem at all. Don't worry about it...
Peter
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
