Your message dated Tue, 28 Apr 2009 17:54:37 +0200
with message-id <[email protected]>
and subject line Re: Bug#468256: Unreproducible
has caused the Debian Bug report #468256,
regarding doesn't configure on first use
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
468256: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468256
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 3.39
Severity: normal
reportbug doesn't ask to configure it when using it for the first time on this
machine.
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /home/chealer/.reportbugrc:
reportbug_version "3.39"
mode expert
ui text
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages reportbug depends on:
ii apt 0.7.11 Advanced front-end for dpkg
ii python 2.4.4-6 An interactive high-level object-o
ii python-central 0.5.15-0.1 register and build utility for Pyt
reportbug recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Apr 20, 2009 at 21:10, chaica <[email protected]> wrote:
> Configuration at the first use works for me on 3.39 and latest versions.
> Could you provide more information on what command-line or anything else
> you have been typing to launch reportbug ?
If the configuration file is absent, the configuration process starts,
so there was something "broken" on the user's machine.
$ ls ~/.reportbugrc
ls: cannot access /home/morph/.reportbugrc: No such file or directory
$ reportbug
Welcome to reportbug! Since it looks like this is the first time you
have used reportbug, we are configuring its behavior. These settings
will be saved to
the file "/home/morph/.reportbugrc", which you will be free to edit further.
Please choose the default operating mode for reportbug.
1 novice Offer simple prompts, bypassing technical questions.
2 standard Offer more extensive prompts, including asking about
things that a moderately sophisticated user would be expected to know
about Debian.
3 advanced Like standard, but assumes you know a bit more about
Debian, including "incoming".
4 expert Bypass most handholding measures and preliminary triage
routines. This mode should not be used by people unfamiliar with
Debian's policies and
operating procedures.
Select mode: [novice]
reportbug: exiting due to user interrupt.
$ reportbug --version
reportbug 4.1
Hence, I'm closing this bug.
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
