Hello,
a bugzilla ticket [1] requiring a better Bugzilla summary field text produced by abrt has been filed. Before I start changing the bug summary format I'd like to do a little survey:
What would you like see in the bug summaries produced by abrt?
Regards Jakub
On Fri, 13 Sep 2013 17:35:20 +0200 Jakub Filak jfilak@redhat.com wrote:
Hello,
a bugzilla ticket [1] requiring a better Bugzilla summary field text produced by abrt has been filed. Before I start changing the bug summary format I'd like to do a little survey:
What would you like see in the bug summaries produced by abrt?
I actually disagree with the reporter of the bug.
I prefer to have the component name in the subject of the bug. It's true that you can look this up by going to the bug on the web and that it's in the initial email, but after that the context of update emails is not there, so it's harder for me to know _which_ of the many abrt bugs this is.
My thought would be:
Current:
[abrt] util-linux-2.23.2-2.fc19: recount_geometry: Process /usr/sbin/fdisk was killed by signal 8 (SIGFPE)
New: [abrt] util-linux: fdisk:recount_geometry() killed by SIGFPE
kevin
On Fri, Sep 13, 2013 at 10:38:41AM -0600, Kevin Fenzi wrote:
On Fri, 13 Sep 2013 17:35:20 +0200 Jakub Filak jfilak@redhat.com wrote:
Hello,
a bugzilla ticket [1] requiring a better Bugzilla summary field text produced by abrt has been filed. Before I start changing the bug summary format I'd like to do a little survey:
What would you like see in the bug summaries produced by abrt?
I actually disagree with the reporter of the bug.
I prefer to have the component name in the subject of the bug. It's true that you can look this up by going to the bug on the web and that it's in the initial email, but after that the context of update emails is not there, so it's harder for me to know _which_ of the many abrt bugs this is.
Please, fix/improve your email client UI. All bugzilla emails contain all necessary information in email header:
for example:
X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Classification: Fedora X-Bugzilla-Product: Fedora X-Bugzilla-Component: util-linux <----- ! X-Bugzilla-Version: 20 X-Bugzilla-Keywords: X-Bugzilla-Severity: unspecified X-Bugzilla-Who: rolf@rolffokkens.nl X-Bugzilla-Status: NEW X-Bugzilla-Priority: unspecified X-Bugzilla-Assigned-To:
X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: bug_id X-Bugzilla-Comment: public X-BeenThere: bugzilla@redhat.com X-Bugzilla-Reporter: X-Bugzilla-URL: https://bugzilla.redhat.com/
For example if you use mutt then all you need is to add
unignore X-Bugzilla-Product X-Bugzilla-Component
to your .muttrc.
It's pretty common that we don't have component name in BZ summary...
Karel
On Mon, Sep 16, 2013 at 10:36:41AM +0200, Karel Zak wrote:
On Fri, Sep 13, 2013 at 10:38:41AM -0600, Kevin Fenzi wrote:
On Fri, 13 Sep 2013 17:35:20 +0200 Jakub Filak jfilak@redhat.com wrote:
a bugzilla ticket [1] requiring a better Bugzilla summary field text produced by abrt has been filed. Before I start changing the bug summary format I'd like to do a little survey:
What would you like see in the bug summaries produced by abrt?
I actually disagree with the reporter of the bug.
I prefer to have the component name in the subject of the bug. It's true that you can look this up by going to the bug on the web and that it's in the initial email, but after that the context of update emails is not there, so it's harder for me to know _which_ of the many abrt bugs this is.
Please, fix/improve your email client UI. All bugzilla emails contain all necessary information in email header:
Because opening email headers is indeed so convenient.
for example:
X-Bugzilla-Reporter: X-Bugzilla-URL: https://bugzilla.redhat.com/For example if you use mutt then all you need is to add
unignore X-Bugzilla-Product X-Bugzilla-Component
This is nice and handy, but I actually don't know many client offering this opeiton. /me gonna add this option to his muttrc (lucky that I do use mutt here and there).
It's pretty common that we don't have component name in BZ summary...
Which does not make it less annoying.
Pierre
On Mon, 2013-09-16 at 10:58 +0200, Pierre-Yves Chibon wrote:
On Mon, Sep 16, 2013 at 10:36:41AM +0200, Karel Zak wrote:
On Fri, Sep 13, 2013 at 10:38:41AM -0600, Kevin Fenzi wrote:
On Fri, 13 Sep 2013 17:35:20 +0200 Jakub Filak jfilak@redhat.com wrote:
a bugzilla ticket [1] requiring a better Bugzilla summary field text produced by abrt has been filed. Before I start changing the bug summary format I'd like to do a little survey:
What would you like see in the bug summaries produced by abrt?
I actually disagree with the reporter of the bug.
I prefer to have the component name in the subject of the bug. It's true that you can look this up by going to the bug on the web and that it's in the initial email, but after that the context of update emails is not there, so it's harder for me to know _which_ of the many abrt bugs this is.
Please, fix/improve your email client UI. All bugzilla emails contain all necessary information in email header:
Because opening email headers is indeed so convenient.
for example:
X-Bugzilla-Reporter: X-Bugzilla-URL: https://bugzilla.redhat.com/For example if you use mutt then all you need is to add
unignore X-Bugzilla-Product X-Bugzilla-ComponentThis is nice and handy, but I actually don't know many client offering this opeiton. /me gonna add this option to his muttrc (lucky that I do use mutt here and there).
Mutt you pointed it out, evolution seems to also support it: Edit -> Preferences -> Mail Preferences -> Headers Don't know about claws-mail but that's already more client than I thought :)
Still feels hacky to me (and I would prefer the topic as proposed by Kevin) but ok, that's one option.
Pierre
On Mon, Sep 16, 2013 at 10:58:47AM +0200, Pierre-Yves Chibon wrote:
It's pretty common that we don't have component name in BZ summary...
Which does not make it less annoying.
Well, then we have more generic problem rather than abrt specific one :-)
Karel
On Mon, Sep 16, 2013 at 10:36:41AM +0200, Karel Zak wrote:
For example if you use mutt then all you need is to add
unignore X-Bugzilla-Product X-Bugzilla-Componentto your .muttrc.
It's pretty common that we don't have component name in BZ summary...
But this does not show the component in the "index" view, or can this be changed as well? I always add the component to the summary for Bugs I report to get this information before I need to open the mail itself.
Regards Till
On Mon, Sep 16, 2013 at 12:34:50PM +0200, Till Maas wrote:
On Mon, Sep 16, 2013 at 10:36:41AM +0200, Karel Zak wrote:
For example if you use mutt then all you need is to add
unignore X-Bugzilla-Product X-Bugzilla-Componentto your .muttrc.
It's pretty common that we don't have component name in BZ summary...
But this does not show the component in the "index" view, or can this be changed as well? I always add the component to the summary for Bugs I report to get this information before I need to open the mail itself.
"Change Columns" link in the search output.
On Mon, Sep 16, 2013 at 01:26:55PM +0200, Karel Zak wrote:
On Mon, Sep 16, 2013 at 12:34:50PM +0200, Till Maas wrote:
On Mon, Sep 16, 2013 at 10:36:41AM +0200, Karel Zak wrote:
For example if you use mutt then all you need is to add
unignore X-Bugzilla-Product X-Bugzilla-Componentto your .muttrc.
It's pretty common that we don't have component name in BZ summary...
But this does not show the component in the "index" view, or can this be changed as well? I always add the component to the summary for Bugs I report to get this information before I need to open the mail itself.
"Change Columns" link in the search output.
I meant the index view in mutt, i.e. the list of messages.
Regards Till
On Mon, Sep 16, 2013 at 06:11:24PM +0200, Till Maas wrote:
On Mon, Sep 16, 2013 at 01:26:55PM +0200, Karel Zak wrote:
On Mon, Sep 16, 2013 at 12:34:50PM +0200, Till Maas wrote:
On Mon, Sep 16, 2013 at 10:36:41AM +0200, Karel Zak wrote:
For example if you use mutt then all you need is to add
unignore X-Bugzilla-Product X-Bugzilla-Componentto your .muttrc.
It's pretty common that we don't have component name in BZ summary...
But this does not show the component in the "index" view, or can this be changed as well? I always add the component to the summary for Bugs I report to get this information before I need to open the mail itself.
"Change Columns" link in the search output.
I meant the index view in mutt, i.e. the list of messages.
Ah, it's not possible, but it would be nice to have some extension to the mutt index_format, something like %x{headername}.
Karel
On Mon, 16 Sep 2013 10:36:41 +0200 Karel Zak kzak@redhat.com wrote:
Please, fix/improve your email client UI. All bugzilla emails contain all necessary information in email header:
...snip...
For example if you use mutt then all you need is to add
unignore X-Bugzilla-Product X-Bugzilla-Componentto your .muttrc.
Cool. That allows me to easily see it if I am viewing that email... doesn't however easily let me see if it I have a list of 10 new bugzilla emails coming that I haven't read yet.
It's pretty common that we don't have component name in BZ summary...
yeah, which is kinda sad, IMHO.
I wonder if someday it would make sense to customize this per user? Possibly too much complexity...
kevin
I wonder if someday it would make sense to customize this per user? Possibly too much complexity...
kevin
ABRT provides per component customization.
https://github.com/abrt/abrt/wiki/FAQ#component-specific-bugzilla-bug-format...
On Mon, 16 Sep 2013 11:08:02 -0400 (EDT) Jakub Filak jfilak@redhat.com wrote:
I wonder if someday it would make sense to customize this per user? Possibly too much complexity...
kevin
ABRT provides per component customization.
https://github.com/abrt/abrt/wiki/FAQ#component-specific-bugzilla-bug-format...
Excellent. Given that almost no packages are shipping these, is there any guideline or guidance how to do so? Just add them to our packages? Anything we need to require?
Might be nice to work with FPC/packaging list and come up with a clear guideline for these.
kevin
On 09/16/2013 11:47 PM, Kevin Fenzi wrote:
On Mon, 16 Sep 2013 11:08:02 -0400 (EDT) Jakub Filak jfilak@redhat.com wrote:
I wonder if someday it would make sense to customize this per user? Possibly too much complexity...
kevin
ABRT provides per component customization.
https://github.com/abrt/abrt/wiki/FAQ#component-specific-bugzilla-bug-format...
Excellent. Given that almost no packages are shipping these, is there any guideline or guidance how to do so? Just add them to our packages? Anything we need to require?
Might be nice to work with FPC/packaging list and come up with a clear guideline for these.
- your package needs to require libreport-filesystem
--Jirka
kevin
ABRT provides per component customization.
https://github.com/abrt/abrt/wiki/FAQ#component-specific-bugzilla-bug-format...
Excellent. Given that almost no packages are shipping these, is there any guideline or guidance how to do so? Just add them to our packages? Anything we need to require?
Just add the files to your package as described on the FAQ page.
According to the packaging guidelines you have to add "Requires: libreport-filesystem" line because /etc/libreport/plugins/ directory is owned by that package.
Might be nice to work with FPC/packaging list and come up with a clear guideline for these.
kevin
Good idea. I will take care of it. Thanks!
Jakub
Le lundi 16 septembre 2013 à 08:51 -0600, Kevin Fenzi a écrit :
On Mon, 16 Sep 2013 10:36:41 +0200 Karel Zak kzak@redhat.com wrote:
Please, fix/improve your email client UI. All bugzilla emails contain all necessary information in email header:
...snip...
For example if you use mutt then all you need is to add
unignore X-Bugzilla-Product X-Bugzilla-Componentto your .muttrc.
Cool. That allows me to easily see it if I am viewing that email... doesn't however easily let me see if it I have a list of 10 new bugzilla emails coming that I haven't read yet.
It's pretty common that we don't have component name in BZ summary...
yeah, which is kinda sad, IMHO.
I wonder if someday it would make sense to customize this per user? Possibly too much complexity...
Assuming you filter your mail using something like maildrop that can filter the email and rewrite the Subject. If spamassassin can do it, why not do the same :)
( I use that to remove the [ml name] of some list, to reorder the subject for easier visual matching, etc, etc )
On 09/13/2013 05:35 PM, Jakub Filak wrote: 1: https://bugzilla.redhat.com/show_bug.cgi?id=1005762
Perhaps you can drop the "Process" word but it's a good idea to keep the NVR in the summary (the VR part isn't reflected in the component field).
Ales
Thank you for all your ideas!
I am going to change the default template to:
[abrt] <component>: <function>(): <executable> killed by SIG<num|name>
Conclusion: - do not drop <component> because some email clients cannot display custom headers in "index"
- drop VR from <component> because Ales Kozumplik is the only one who wants it (VR is always available in comment #0)
- drop "Process", "/full/path/to/executable" and "signal"
- <function> must be prefix of '<executable> killed by SIG<num|name>' because 'killed by' message is generated while coredumping and unfortunately <function> is not known at that time
devel@lists.stg.fedoraproject.org
-
Ales Kozumplik -
Jakub Filak -
Jiri Moskovcak -
Karel Zak -
Kevin Fenzi -
Michael Scherer -
Pierre-Yves Chibon -
Till Maas