tags 543687 unreproducible
thanks
Hello Edward,
thanks for your bug report
On Wed, Aug 26, 2009 at 15:10, Edward Welbourne <e...@opera.com> wrote:
> Package: reportbug
> Version: 4.6
> Severity: normal
>
>
> I have
> export EDITOR=emacsclient
> set in my environment.
>
> Today I installed emacs23 and immediately hit a bug (can't use rmail),
> so fired up reportbug. When it came time for me to edit the bug
> e-mail, I just got error messages in reportbug's virtual console;
> emacsclient wasn't answering :-(
>
> So I opted (I think the command letter was "c") to change editor
> command; I used vi, which was duly started up, but on an empty buffer,
> instead of on the familiar buffer I expected to see, with package
> details in it.
could you please try with reportbug v4.8 ? I just test it and it works fine:
mo...@zion:~$ export EDITOR=emacsclient
mo...@zion:~$ reportbug -O --debug checkgmail
Unrecognized token: ldap
*** Welcome to reportbug. Use ? for help at prompts. ***
Detected character set: UTF-8
Please change your locale if this is incorrect.
Using 'Sandro Tosi <mo...@debian.org>' as your from address.
Getting status for checkgmail...
Verifying package integrity...
Will send report to Debian (per lsb_release).
Maintainer for checkgmail is 'Sandro Tosi <mo...@debian.org>'.
Looking up dependencies of checkgmail...
Please briefly describe your problem (max. 100 characters allowed; you
can elaborate in a moment; an
empty response will stop reportbug). This will be the bug email
subject, so write a concise summary of
what is wrong with the package, for example, "fails to send email" or
"does not start with -q option
specified" (enter Ctrl+c to exit).
> dagf
Enter any additional addresses this report should be sent to; press
ENTER after each address. Press
ENTER on a blank line to continue.
>
How would you rate the severity of this problem or report?
1 critical makes unrelated software on the system (or the whole
system) break, or causes
serious data loss, or introduces a security hole on
systems where you install the
package.
2 grave makes the package in question unusable by most or
all users, or causes data loss, or
introduces a security hole allowing access to the
accounts of users who use the
package.
3 serious is a severe violation of Debian policy (that is, the
problem is a violation of a
'must' or 'required' directive); may or may not
affect the usability of the package.
Note that non-severe policy violations may be
'normal,' 'minor,' or 'wishlist' bugs.
(Package maintainers may also designate other bugs
as 'serious' and thus release-
critical; however, end users should not do so.)
4 important a bug which has a major effect on the usability of a
package, without rendering it
completely unusable to everyone.
5 does-not-build a bug that stops the package from being built from
source. (This is a 'virtual
severity'.)
6 normal a bug that does not undermine the usability of the
whole package; for example, a
problem with a particular option or menu item.
7 minor things like spelling mistakes and other minor
cosmetic errors that do not affect the
core functionality of the package.
8 wishlist suggestions and requests for new features.
Please select a severity level: [normal]
Do any of the following apply to this report?
1 l10n This bug reports a localization/internationalization issue.
2 patch You are including a patch to fix this problem.
3 none
Please select tags: (one at a time) [none]
Spawning emacsclient...
emacsclient: can't find socket; have you started the server?
To start the server in Emacs, type "M-x server-start".
emacsclient: No socket or alternate editor. Please use:
--socket-name
--server-file (or environment variable EMACS_SERVER_FILE)
--alternate-editor (or environment variable ALTERNATE_EDITOR)
Warning: possible error exit from emacsclient: 256
No changes were made in the editor.
Report will be sent to Sandro Tosi <mo...@debian.org>
Submit this report on checkgmail (e to edit) [y|n|a|c|E|i|l|m|p|q|d|t|?]? ?
y - Submit the bug report via email.
n - Don't submit the bug report; instead, save it in a temporary file
(exits reportbug).
a - Attach a file.
c - Change editor and re-edit.
E - (default) Re-edit the bug report.
i - Include a text file.
l - Pipe the message through the pager.
m - Choose a mailer to edit the report.
p - print message to stdout.
q - Save it in a temporary file and quit.
d - Detach an attachment file.
t - Add tags.
? - Display this help.
Submit this report on checkgmail (e to edit) [y|n|a|c|E|i|l|m|p|q|d|t|?]? c
Choose editor: vim
Spawning vim...
Report will be sent to Sandro Tosi <mo...@debian.org>
Submit this report on checkgmail (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|?]? y
Sending message via /usr/sbin/sendmail...
Bug report submitted to: Sandro Tosi <mo...@debian.org>
If you want to provide additional information, please wait to receive
the bug tracking number via
email; you may then send any extra information to n...@bugs.debian.org
(e.g. 999...@bugs.debian.org),
where n is the bug number. Normally you will receive an
acknowledgement via email including the bug
report number within an hour.
and vim was spawn with the correct text in it and so on.
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
