266033 - contrib/cmdline/buglist - great shell script, needs some work. (bugs + enhancements)

Status: NEW

(Bugzilla :: Bugzilla-General, enhancement)

Description

[Matthew Hall]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616


1. From my using this script, it seems that it requires GNU compatible tools
(expr, test) - This script fails miserably on Solaris until I point the PATH to
the /usr/ucb. A quick test for compatible test/expr would be nice. 

2. All HTML output from bugzilla seems to have Relative links, and not Absolute.
I verified that my baseurl was set correctly - this makes the HTML output fairly
useless as a reference, because I cannot click/follow any of the links - unless
I put the output file into the Bugzilla top-level directory. This makes for
automated email of reports / stats not useful to the (possibly clueless)
recipient. The link rel href= in the output does not seem to induce the desired
behaviour in IE6/Mozilla 1.7/lynx. 

3. Given how the shell script parses the arguments, there doesn't seem to be any
way to pass in a Product with spaces/multiple words. "--product=FooBar
Appliance" fails, and "--product=FooBar%20Appliance" (HTML encoded space)
doesn't seem to pass appropriately on to the Bugzilla query interface. Quotes
around the product also cause parsing to fail. 

Reproducible: Always
Steps to Reproduce:

Simple tests should verify my claims on Solaris, URL problems, and multi-word
Product names.

Comment 1

[Dave Miller [:justdave]]

This was contributed by Andreas Franke.  I'm not sure if he maintains it
anymore...  it's likely he doesn't.  If someone wants to attack it, go for it.

Comment 2

[Andreas Franke (gone)]

About the mentioned issues:

1. The solaris compatibility problem might be fixed in the new 2.18-compatible
version in attachment 171628 [details] in bug 278829.  Feel free to test. :-)

2. The base-url for bugzilla's html pages is pretty much an issue independent
from the cmdline tool.  The new version for 2.18 currently doesn't use html
output any more (but the comma-separated-values format instead); to get the html
version back it should be sufficient to replace ctype=csv with ctype=html in the
respective shell script (one occurrence).
Have you tried to solve the baseurl problem by prepending a <BASE href="...">
line at the beginning of the html file?  Of course this could be scripted, too.

3. With the new version, querying for a product with a space did work for me
when I tested it, using --product="foo bar" as you suggested.  I did not test
the old version, though.

Does this solve all your issues?  (Taking bug for now.)