BugZappers/CorrectComponent

From FedoraProject

< BugZappers(Difference between revisions)
Jump to: navigation, search
m (1 revision(s))
(rewrite for greater clarity and simplicity, and cover additional cases)
Line 1: Line 1:
= Determining Correct Component =
+
==Which program is it?==
  
Fedora bugzilla follows the convention of filing bugs against the source rpm for the compiled program or script which contains the bug.  Sometimes there is not an obvious mapping between the name of the program or script, installed (binary) rpm and source rpm. Hopefully the following suggestions will help you narrow it down.
+
If you started the program from the GNOME menu, you can usually find the name of the program by going to "Help -> About" in the program's internal menus. You can also go to "System -> Preferences -> Personal -> Sessions" on the GNOME menu.  Click on the "Current Session" tab to see a list of programs running on your desktop.
  
== You already know the installed rpm name ==
+
If you started the program from the command line, the name of the program is the first "word" of the command (everything before the first space, which might include dashes or underscores).
 +
 
 +
==Which file is it?==
 +
 
 +
If you know which command was run, but don't know the exact file name this corresponds to, try this on the command line:
  
 
<pre>
 
<pre>
$ rpm -qi <name>
+
which <command-name>
 
</pre>
 
</pre>
  
Look under the 'Source RPM' field that is bugzilla the ''component'' a bug should be filed against
+
or if you are running tcsh:
 
+
== All you know is the command or program name ==
+
 
+
Find the full path to the command:
+
  
 
<pre>
 
<pre>
$ which <command-name>
+
where <command-name>
 
</pre>
 
</pre>
  
Find the name of the rpm that provides the command
+
The first line in the results is the one you want.
  
 +
For example:
 
<pre>
 
<pre>
$ rpm -qif </full/path/to/command-name>
+
$ which ssh
 +
/usr/bin/ssh
 
</pre>
 
</pre>
  
Or another option is to use yum
+
==Which RPM is it?==
 +
 
 +
Once you have the name of a file or directory, you can determine which RPM owns it using "rpm -qf".  For example:
  
 
<pre>
 
<pre>
$ yum whatprovides <command-name>
+
$ rpm -qf /usr/bin/nautilus-file-management-properties
$ rpm -qi <name>
+
nautilus-2.25.91-2.fc11.x86_64
 
</pre>
 
</pre>
  
== We need more examples ==
+
==Which component is it?==
 +
 
 +
In Fedora, a given "source" RPM can produce multiple RPMs in the distribution.  Bugzilla groups bugs according to the "source" RPMs only.  Once you have the RPM name, you can get the "source" RPM name (which might be different) using "rpm -qi".  For example, run "rpm -qi glibc-common" and then look for the line that says "Source RPM:"  In this case, it's glibc-2.9.90-7.src.rpm, which means the component name to use in Bugzilla is "glibc" (everything before the dash before the version number).
  
'''FIXME''': add more complex examples?
+
Note that if the "Vendor:" line does not say "Fedora Project", you may need to report the bug to a different bugzilla.

Revision as of 18:15, 24 February 2009

Contents

Which program is it?

If you started the program from the GNOME menu, you can usually find the name of the program by going to "Help -> About" in the program's internal menus. You can also go to "System -> Preferences -> Personal -> Sessions" on the GNOME menu. Click on the "Current Session" tab to see a list of programs running on your desktop.

If you started the program from the command line, the name of the program is the first "word" of the command (everything before the first space, which might include dashes or underscores).

Which file is it?

If you know which command was run, but don't know the exact file name this corresponds to, try this on the command line:

 which <command-name>

or if you are running tcsh:

 where <command-name>

The first line in the results is the one you want.

For example:

 $ which ssh
 /usr/bin/ssh

Which RPM is it?

Once you have the name of a file or directory, you can determine which RPM owns it using "rpm -qf". For example:

 $ rpm -qf /usr/bin/nautilus-file-management-properties
 nautilus-2.25.91-2.fc11.x86_64

Which component is it?

In Fedora, a given "source" RPM can produce multiple RPMs in the distribution. Bugzilla groups bugs according to the "source" RPMs only. Once you have the RPM name, you can get the "source" RPM name (which might be different) using "rpm -qi". For example, run "rpm -qi glibc-common" and then look for the line that says "Source RPM:" In this case, it's glibc-2.9.90-7.src.rpm, which means the component name to use in Bugzilla is "glibc" (everything before the dash before the version number).

Note that if the "Vendor:" line does not say "Fedora Project", you may need to report the bug to a different bugzilla.