On 27 September 2012 13:13, <John.Florian(a)dart.biz> wrote:
> From: Adam Williamson <awilliam(a)redhat.com>
> Bugzilla goes by .src.rpm name not binary rpm
> name. rpm -qi can tell you the .src.rpm from which any binary package
> was built.
I used to get tripped up on this too and I've been doing Linux since the RHL
4.0 days. In some cases it's entirely unobvious (e.g,.
python-imgcreate-*.rpm originates from livecd-tools-*.src.rpm). Once you
realize what's going on, you can usually see the connection, but I suspect
some/many a would-be-bug-reporters give up when they simply cannot find the
binary rpm listed in BZ.
Perhaps the mouse-over and click-through help text of BZ's Component field
could better explain this. It might also be good to note how easy it is to
grock the src.rpm name from a "suspect" file using rpm -qif
/some/suspect/filename.
This might be worthwhile. I had no idea it worked this way, though in
hindsight it's obvious why. A hint somewhere in the UI might work
(maybe a "Can't find your component?" link). It is noted in the guided
bug report form, but I doubt many people use that after their first
couple of reports.
--
imalone
http://ibmalone.blogspot.co.uk