reopen 422085
thanks
Hi!
I just tried using reportbug-ng to report bugs against packages like texlive-
doc-base, xserver-xorg and mdadm. (what's common for these 3 packages is that
thay have bug scripts)
And the result is:
I see a terminal pop up briefly with a lot of text scrolling over and a
On Mon, Jul 21, 2008 at 09:00:04 +, Debian Bug Tracking System wrote:
This is not a bug of rng and not related to 422085:
err. yes it is.
* calling /usr/share/bug/texlive-doc-base 31 aborts with an error
(getkey: command not found) when called in the console.
That's one of the
Julien Cristau wrote:
On Mon, Jul 21, 2008 at 09:00:04 +, Debian Bug Tracking System wrote:
* calling /usr/share/bug/texlive-doc-base 31 aborts with an error
(getkey: command not found) when called in the console.
That's one of the documented functions such a script can rely on.
Where
On Mon, Jul 21, 2008 at 17:15:10 +0200, Bastian Venthur wrote:
Julien Cristau wrote:
On Mon, Jul 21, 2008 at 09:00:04 +, Debian Bug Tracking System wrote:
* calling /usr/share/bug/texlive-doc-base 31 aborts with an error
(getkey: command not found) when called in the console.
Julien Cristau wrote:
On Mon, Jul 21, 2008 at 17:15:10 +0200, Bastian Venthur wrote:
Julien Cristau wrote:
That's one of the documented functions such a script can rely on.
Where is that documented? And where does getkey come from? Haven't found
a package providing this command.
This one time, at band camp, Bastian Venthur said:
And please keep in mind that this only happens when the output of a
script is *very* large -- to large for the shell to handle -- like the
one from xserver-xorg, for the most other packages, everything should
work fine automatically and
On Mon, Jul 21, 2008 at 18:00:12 +0200, Bastian Venthur wrote:
The output of /usr/share/bug/xserver-xorg/script 31 is ~65K big.
Calling the mua like: mua --body $OUTPUT ... does not work, at least
Calling the mua like that doesn't make any sense. Just give it a
filename or something on stdin,
Stephen Gran wrote:
This one time, at band camp, Bastian Venthur said:
And please keep in mind that this only happens when the output of a
script is *very* large -- to large for the shell to handle -- like the
one from xserver-xorg, for the most other packages, everything should
work fine
Julien Cristau wrote:
On Mon, Jul 21, 2008 at 18:00:12 +0200, Bastian Venthur wrote:
The output of /usr/share/bug/xserver-xorg/script 31 is ~65K big.
Calling the mua like: mua --body $OUTPUT ... does not work, at least
Calling the mua like that doesn't make any sense. Just give it a
On Mon, Jul 21, 2008 at 18:16:39 +0200, Bastian Venthur wrote:
Please give me a concrete example, so I can implement your idea. Please
test if it works with xdg-email and icedove. It also has to work
combined with python's command.getoutput or at least from within Python.
*sigh*
Julien Cristau wrote:
On Mon, Jul 21, 2008 at 18:16:39 +0200, Bastian Venthur wrote:
Please give me a concrete example, so I can implement your idea. Please
test if it works with xdg-email and icedove. It also has to work
combined with python's command.getoutput or at least from within
On Mon, Jul 21, 2008 at 18:46:16 +0200, Bastian Venthur wrote:
- A few mails ago, I already explained (and provided a bugnumber), that
the --attach parameter of xdg-email doesn't work and that not every
MUA supports attaching a file from the command line.
- You said, then the MUAs are
Julien Cristau wrote:
On Mon, Jul 21, 2008 at 18:46:16 +0200, Bastian Venthur wrote:
- A few mails ago, I already explained (and provided a bugnumber), that
the --attach parameter of xdg-email doesn't work and that not every
MUA supports attaching a file from the command line.
- You
13 matches
Mail list logo
