[Bug 482951] New: Review Request: sugar-playgo - Go for Sugar

[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: sugar-playgo - Go for Sugar

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

           Summary: Review Request: sugar-playgo - Go for Sugar
           Product: Fedora
           Version: rawhide
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: medium
         Component: Package Review
        AssignedTo: nobody at fedoraproject.org
        ReportedBy: fabian at bernewireless.net
         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://fab.fedorapeople.org/packages/XO/sugar-playgo.spec
SRPM URL: http://fab.fedorapeople.org/packages/XO/sugar-playgo-5-1.fc10.src.rpm

Project URL: http://wiki.laptop.org/go/PlayGo

Description:
The PlayGo activity implements Go a strategic board game for two players. Go 
originated in ancient China, centuries before its earliest known references
in 5th century BC writing. It is mostly popular in East Asia but has nowadays
gained some popularity in the rest of the world as well. Go is noted for being
rich in strategic complexity despite its simple rules. 

Koji scratch build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1089922

rpmlint output:
[fab at laptop24 noarch]$ rpmlint sugar-playgo-5-1.fc10.noarch.rpm 
sugar-playgo.noarch: W: non-standard-group Sugar/Activities
1 packages and 0 specfiles checked; 0 errors, 1 warnings.

[fab at laptop24 SRPMS]$ rpmlint sugar-playgo-5-1.fc10.src.rpm 
sugar-playgo.src: W: non-standard-group Sugar/Activities
1 packages and 0 specfiles checked; 0 errors, 1 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.