[Bug 541807] New: Review Request: rubygem-ParseTree - Extracts the parse tree for a class/method and returns an s-expression

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: Review Request: rubygem-ParseTree - Extracts the parse tree for a class/method and returns an s-expression

https://bugzilla.redhat.com/show_bug.cgi?id=541807

           Summary: Review Request: rubygem-ParseTree - Extracts the parse
                    tree for a class/method and returns an s-expression
           Product: Fedora
           Version: rawhide
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: medium
         Component: Package Review
        AssignedTo: nobody at fedoraproject.org
        ReportedBy: mkent at magoazul.com
         QAContact: extras-qa at fedoraproject.org
                CC: notting at redhat.com, fedora-package-review at redhat.com
   Estimated Hours: 0.0
    Classification: Fedora


Spec URL: http://magoazul.com/wip/SPECS/rubygem-ParseTree.spec
SRPM URL: http://magoazul.com/wip/SRPMS/rubygem-ParseTree-3.0.4-1.fc13.src.rpm
Description: ParseTree is a C extension (using RubyInline) that extracts the
parse tree for an entire class or a specific method and returns it as a
s-expression (aka sexp) using ruby's arrays, strings, symbols, and integers.

mkent at fedora-devel-chef:~/rpmbuild/SPECS$ rpmlint rubygem-ParseTree.spec
/var/tmp/results/rubygem-ParseTree-*
rubygem-ParseTree-doc.noarch: W: no-documentation
rubygem-ParseTree-doc.noarch: W: hidden-file-or-dir
/usr/lib/ruby/gems/1.8/gems/ParseTree-3.0.4/.autotest
rubygem-ParseTree-doc.noarch: W: misspelled-macro
/usr/lib/ruby/gems/1.8/doc/ParseTree-3.0.4/ri/ParseTreeGauntlet/should_skip%3f-i.yaml
%3f
3 packages and 1 specfiles checked; 0 errors, 3 warnings

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.