Your message dated Sat, 31 Jul 2010 15:20:31 +0200
with message-id <[email protected]>
and subject line Re: Bug#579201: reportbug doesn't offer information on marking 
a bug  as forwarded upstream
has caused the Debian Bug report #579201,
regarding reportbug doesn't offer information on marking a bug as forwarded 
upstream
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.)


-- 
579201: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579201
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 4.12.1
Severity: wishlist


At present reportbug offers no information (unless in a package-specific
script) on reporting a bug upstream, and in those situations, it should
be possible to use reportbug to mark the bug as forwarded upstream, or
at least provide a suggestion to mark the bug as forwarded upstream,
along with a link to instructions such as those found at
http://www.debian.org/Bugs/server-control


-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /home/amarsh04/.reportbugrc:
reportbug_version "3.5"
mode standard
ui text
realname "Arthur Marsh"
email "[email protected]"

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.33 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages reportbug depends on:
ii  apt                           0.7.25.3   Advanced front-end for dpkg
ii  python                        2.5.4-9    An interactive high-level object-o
ii  python-reportbug              4.12.1     Python modules for interacting wit

reportbug recommends no packages.

Versions of packages reportbug suggests:
ii  debconf-utils        1.5.32              debconf utilities
pn  debsums              <none>              (no description available)
pn  dlocate              <none>              (no description available)
ii  emacs22-bin-common   22.3+1-1.2          The GNU Emacs editor's shared, arc
ii  exim4                4.71-4              metapackage to ease Exim MTA (v4) 
ii  exim4-daemon-light [ 4.71-4              lightweight Exim MTA (v4) daemon
ii  file                 5.04-2              Determines file type using "magic"
ii  gnupg                1.4.10-3            GNU privacy guard - a free PGP rep
ii  python-gtk2          2.17.0-2            Python bindings for the GTK+ widge
pn  python-gtkspell      <none>              (no description available)
pn  python-urwid         <none>              (no description available)
ii  python-vte           1:0.24.0-3          Python bindings for the VTE widget
ii  xdg-utils            1.0.2+cvs20100307-1 desktop integration utilities from

-- debconf-show failed



--- End Message ---
--- Begin Message ---
Hello,

On Mon, Apr 26, 2010 at 10:02, Arthur Marsh
<[email protected]> wrote:
> Package: reportbug
> Version: 4.12.1
> Severity: wishlist
>
>
> At present reportbug offers no information (unless in a package-specific
> script) on reporting a bug upstream,

simply because there is no standard way to do that.

> and in those situations, it should
> be possible to use reportbug to mark the bug as forwarded upstream, or
> at least provide a suggestion to mark the bug as forwarded upstream,
> along with a link to instructions such as those found at
> http://www.debian.org/Bugs/server-control

Because I don't think it's purpose of reportbug to copy all the BTS
documentation; you can find that from [1] you can come to [2] that
explains Forwarded is the pseudo-header to be used to forward a bug
upstream at submit time. In reportbug, we have README.Users explain
how to add pseudo-headers. That's all I think we have to do.

[1] http://www.debian.org/Bugs/Reporting
[2] http://www.debian.org/Bugs/Reporting#additionalpseudoheaders

That's said, I'm closing this report.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


--- End Message ---
_______________________________________________
Reportbug-maint mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/reportbug-maint

Reply via email to