Bug#695220: reportbug stores empty bug reports in the ~/.reportbug directory

2015-12-30 Thread Vincent Lefevre
Control: reopen -1
Control: reassign -1 mutt
Control: retitle -1 mutt -H  should modify the draft , not create a 
copy

On 2015-12-30 19:14:10 +, Sandro Tosi wrote:
> On Wed, Dec 5, 2012 at 11:55 PM, Vincent Lefevre  wrote:
> > The man page says:
> >
> >--draftpath=DRAFTPATH
> >Save the draft (for example, when exiting and saving the report
> >without reporting it) into DRAFTPATH directory.
> >
> > but it seems that an empty bug report (by "empty", the file provided
> > to the mailer, i.e. with the default contents), whether the bug has
> 
> I verified and the --draftpath work fines if not using mutt.
> 
> > been reported or not. I've just done a test, ending with:
> >
> > [...]
> > Spawning mutt...
> > 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|?]? q
> > Draft saved into 
> > /home/vinc17/.reportbug/reportbug-reportbug-20121206-7695-DHs64D
> >
> > but /home/vinc17/.reportbug/reportbug-reportbug-20121206-7695-DHs64D
> > does not contain the text I've written in the bug report. This is an
> > obvious data loss.
> 
> this is simply how mutt works: we prepare the template, and then we
> sent it to mutt, where you edit it (using mutt functionalities) and
> then you send it with mutt. If you look closely, mutt will show you a
> different file "attached" to the mail about to be sent, where the text
> you entered is saved, but that is not fed back to reportbug, hence you
> think there is "loss of data" but it's a limitation of the
> reportbug-mutt channel.

Then that's quite clear that it is a bug in Mutt. In other MUA's,
when one edits a draft, the draft itself is modified (updated), until
the mail is sent or the draft is discarded. That's basically the
difference between a draft and file inclusion. So, I'm reassigning
the bug.

And that's what the --draftpath reportbug option expects, otherwise
this option wouldn't exist!

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#695220: reportbug stores empty bug reports in the ~/.reportbug directory

2012-12-05 Thread Vincent Lefevre
Package: reportbug
Version: 6.4.3
Severity: minor

reportbug stores empty bug reports in the ~/.reportbug directory.
I don't think this is useful. At least the behavior should be
documented in the reportbug(1) man page (there's nothing about
this directory).

-- Package-specific info:
** Environment settings:
EDITOR=emacs
VISUAL=emacs
EMAIL=vinc...@vinc17.net
INTERFACE=text

** /home/vlefevre/.reportbugrc:
reportbug_version 2.10
mode advanced
ui text
realname Vincent Lefevre
email vinc...@vinc17.net
mua mutt
cc

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages reportbug depends on:
ii  apt   0.9.7.6
ii  python2.7.3-3
ii  python-reportbug  6.4.3

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail none
pn  debconf-utils  none
ii  debsums2.0.52
ii  dlocate1.02
ii  emacs23-bin-common 23.4+1-4
ii  exim4  4.80-6
ii  exim4-daemon-light [mail-transport-agent]  4.80-6
ii  file   5.11-2
ii  gnupg  1.4.12-6
ii  python-gtk22.24.0-3
pn  python-gtkspellnone
pn  python-urwid   none
pn  python-vte none
ii  xdg-utils  1.1.0~rc1+git20111210-6

Versions of packages python-reportbug depends on:
ii  apt   0.9.7.6
ii  python2.7.3-3
ii  python-debian 0.1.21+nmu2
ii  python-debianbts  1.11
ii  python-support1.0.15

python-reportbug suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#695220: reportbug stores empty bug reports in the ~/.reportbug directory

2012-12-05 Thread Sandro Tosi
Hello Vincent,

On Wed, Dec 5, 2012 at 4:36 PM, Vincent Lefevre vinc...@vinc17.net wrote:
 reportbug stores empty bug reports in the ~/.reportbug directory.
 I don't think this is useful. At least the behavior should be
 documented in the reportbug(1) man page (there's nothing about
 this directory).

How old are those empty reports? from a quick grep, I can't find any
code writing to ~/.reportbug , so they were likely generated by some
old version of reportbug.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#695220: reportbug stores empty bug reports in the ~/.reportbug directory

2012-12-05 Thread Vincent Lefevre
severity 695220 important
retitle 695220 reportbug stores empty bug reports in the --draftpath directory, 
text is lost
thanks

(Severity raised to important due to data loss, see below.)

Hi,

On 2012-12-05 21:53:57 +0100, Sandro Tosi wrote:
 Hello Vincent,
 
 On Wed, Dec 5, 2012 at 4:36 PM, Vincent Lefevre vinc...@vinc17.net wrote:
  reportbug stores empty bug reports in the ~/.reportbug directory.
  I don't think this is useful. At least the behavior should be
  documented in the reportbug(1) man page (there's nothing about
  this directory).
 
 How old are those empty reports?

On one machine: 2012-11-28
On the other one: 2012-12-05

I've looked at my config files, and saw:

  alias reportbug=reportbug --draftpath=$HOME/.reportbug

The man page says:

   --draftpath=DRAFTPATH
   Save the draft (for example, when exiting and saving the report
   without reporting it) into DRAFTPATH directory.

but it seems that an empty bug report (by empty, the file provided
to the mailer, i.e. with the default contents), whether the bug has
been reported or not. I've just done a test, ending with:

[...]
Spawning mutt...
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|?]? q
Draft saved into 
/home/vinc17/.reportbug/reportbug-reportbug-20121206-7695-DHs64D

but /home/vinc17/.reportbug/reportbug-reportbug-20121206-7695-DHs64D
does not contain the text I've written in the bug report. This is an
obvious data loss.

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org