[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#653738: marked as done (Configuration routine not run if a package specified on first run)

Your message dated Wed, 26 Dec 2018 15:59:45 -0500
with message-id <CAB4XWXy7_1AW1ceR73DgbZKennou0p7GcD_gyXCghiJKReEcUw@mail.gmail.com>
and subject line Re: [Reportbug-maint] Bug#653738: Configuration routine not run if a package specified on first run
has caused the Debian Bug report #653738,
regarding Configuration routine not run if a package specified on first run
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 owner@bugs.debian.org
immediately.)


-- 
653738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653738
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: reportbug
Version: 6.3.1
Severity: normal

Hiya,

If the user specifies a package when first running reportbug, novice
mode is assumed and no further configuration questions are asked. This
might be troublesome in particular if the user does not have a working
local mail setup. Perhaps reportbug could offer to run the confuguration
routine in this case? Or just warn that this assumption is being made
and that they should abort and run with --configure if they want to
change it.

Cheers,


-- Package-specific info:
** Environment settings:
EDITOR="vim"
DEBEMAIL="iain@orangesquash.org.uk"
EMAIL="iain@orangesquash.org.uk"
DEBFULLNAME="Iain Lane"
NAME="Iain Lane"
INTERFACE="text"

** /home/laney/.reportbugrc:
reportbug_version "3.48ubuntu1"
mode expert
ui text
no-cc
header "X-Debbugs-CC: laney@debian.org"
bts debian
email laney@debian.org
mutt

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages reportbug depends on:
ii  apt               0.8.15.9
ii  python            2.7.2-9
ii  python-reportbug  6.3.1

reportbug recommends no packages.

Versions of packages reportbug suggests:
ii  debconf-utils                 1.5.41
ii  debsums                       <none>
ii  dlocate                       1.02
ii  emacs23-bin-common            23.3+1-4
ii  file                          5.09-2
ii  gnupg                         1.4.11-3
ii  python-gtk2                   2.24.0-2
ii  python-gtkspell               <none>
ii  python-urwid                  <none>
ii  python-vte                    1:0.28.2-4
ii  ssmtp [mail-transport-agent]  2.64-5
ii  xdg-utils                     1.1.0~rc1+git20111210-4

Versions of packages python-reportbug depends on:
ii  apt               0.8.15.9
ii  python            2.7.2-9
ii  python-debian     0.1.21
ii  python-debianbts  1.10
ii  python-support    1.0.14

python-reportbug suggests no packages.

-- no debconf information

-- 
Iain Lane                                  [ iain@orangesquash.org.uk ]
Debian Developer                                   [ laney@debian.org ]
Ubuntu Developer                                   [ laney@ubuntu.com ]
PhD student                                       [ ial@cs.nott.ac.uk ]

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
> If the user specifies a package when first running reportbug, novice
> mode is assumed and no further configuration questions are asked. This
> might be troublesome in particular if the user does not have a working
> local mail setup. Perhaps reportbug could offer to run the confuguration
> routine in this case? Or just warn that this assumption is being made
> and that they should abort and run with --configure if they want to
> change it.

I agree with Kay that you either follow up on the warning displayed or
just continue with the default configuration. thru the years i dont
recall many situations where people complained about this behaviour
much, so i'm going ahead and close this.

Thanks,

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

--- End Message ---
Reply to: