Your message dated Sun, 6 Nov 2011 16:52:55 +0100
with message-id
<capdtaj1oor0upvqajz6st5edtxvj+yaq-tvqqesgwsgrdy1...@mail.gmail.com>
and subject line Re: Bug#560369: reportbug thinks message isn't sent when mutt
postpones
has caused the Debian Bug report #560369,
regarding reportbug thinks message isn't sent when mutt postpones
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.)
--
560369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560369
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 4.8
Severity: minor
Hi!
First of all, sorry if this is a duplicate. Though, that is the reason
why I just postponed the bugreport in the first place instead of sending
it along. reportbug seems to think that it hasn't been sent and gives
this message:
#v+
Mutt users should be aware it is mandatory to edit the draft before sending.
Report has not been sent yet; what do you want to do now? [E|q|?]? ?
E - (default) Edit the message.
q - Quit reportbug; will save the draft for future use.
? - Display this help.
Report has not been sent yet; what do you want to do now? [E|q|?]? q
#v-
Not sure what exit status mutt gives on postponing a message but I
guess it should be taken as a positive response too. I'm also not sure
if mutt is actually producing different return codes - and if it is
proper to return 1 on postponed messages; maybe reassigning it to mutt
is the correct thing to do here.
So long!
Rhonda
-- Package-specific info:
** Environment settings:
DEBEMAIL="[email protected]"
DEBFULLNAME="Gerfried Fuchs"
** /home/rhonda/.reportbugrc:
submit
mutt
query-bts
no-cc
config-files
compress
verify
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.30-2-powerpc
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages reportbug depends on:
ii apt 0.7.23.1 Advanced front-end for dpkg
ii python 2.5.4-2 An interactive high-level object-o
ii python-reportbug 4.8 Python modules for interacting wit
reportbug recommends no packages.
Versions of packages reportbug suggests:
ii debconf-utils 1.5.28 debconf utilities
ii debsums 2.0.47 tool for verification of installed
ii dlocate 1.02 fast alternative to dpkg -L and dp
ii exim4 4.69-11 metapackage to ease Exim MTA (v4)
ii exim4-daemon-heavy [mail-tran 4.69-11+b1 Exim MTA (v4) daemon with extended
ii file 5.03-3 Determines file type using "magic"
ii gnupg 1.4.10-2 GNU privacy guard - a free PGP rep
ii python-gtk2 2.16.0-1 Python bindings for the GTK+ widge
ii python-gtkspell 2.25.3-2 Python bindings for the GtkSpell l
ii python-urwid 0.9.8.4-1 curses-based UI/widget library for
pn python-vte <none> (no description available)
ii xdg-utils 1.0.2-6.1 desktop integration utilities from
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Apr 5, 2010 at 15:58, Sandro Tosi <[email protected]> wrote:
> Hi Gerfried,
>
> On Wed, Jan 6, 2010 at 01:02, Sandro Tosi <[email protected]> wrote:
>> Hi Gerfried,
>>
>> On Thu, Dec 10, 2009 at 22:12, Sandro Tosi <[email protected]> wrote:
>>> On Thu, Dec 10, 2009 at 19:57, Gerfried Fuchs <[email protected]> wrote:
>>>> I'm also not sure
>>>> if mutt is actually producing different return codes - and if it is
>>>> proper to return 1 on postponed messages; maybe reassigning it to mutt
>>>> is the correct thing to do here.
>>>
>>> What you should do is file a bug against mutt asking for
>>> clarifications and then block this bug with the one on mutt.
>>>
>>> We can't lead this task, but we'd be welcome to adjust reportbug
>>> behavior once there are some more info.
>>
>> Were you able to follow up with mutt maintainers? If so, please block
>> this bug with the one filed against mutt, else please report the bug
>> and GOTO "if so" :)
>
> Any news about it? could you please follow-up on what I wrote? if you
> can't (or if I won't see any change in some time) I'm afraid I'm going
> to close this report.
Closing due to inactivity. Please feel free to reopen it if you are
willing to fulfill what I've asked above.
Thanks & Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
