The upstream initscript is an unholy mess that tries to support multiple
distributions, so I plan to create a stripped-down RH/FC-only version, but
otherwise, the package is ready for review.

Okay, new -2 build pushed up, contains a much cleaner initscript and also
properly sets up log directories and log rotation.

http://wilsonet.com/packages/conman/conman-0.1.9.1-2.src.rpm

Review for this package:-
MUST Items:
     - MUST: rpmlint shows no error 
     - MUST: The package is named according to the Package Naming Guidelines.
     - MUST: The spec file name matching the base package conman, in the format
conman.spec
      - MUST: This package meets the Packaging Guidelines.
      - MUST: The package is licensed with an open-source compatible license GPL.
      - MUST: The License field in the package conman.spec file is included in
tarball as COPYING.
      - MUST: The sources used to build the package matches the upstream source,
as provided in the spec URL. md5sum is correct.
      - MUST: This package owns all directories that it creates. 
      - MUST: This package did not contain any duplicate files in the %files
listing.
      - MUST: This package  have a %clean section, which contains %{__rm} -rf
%{buildroot}.
      - MUST: This package used macros.
      - MUST: Document files are NOT included like README.
     Package installed correctly the conman service

SHOULD items:-
        Upstream package should add README file

Above is Not an official review as I'm not yet sponsored

You don't have to be sponsored to do package reviews, being sponsored is only
necessary to submit and maintain your own packages in extras. Doing reviews
*before* getting sponsored is actually encouraged, as it helps potential
sponsors better evaluate your understanding of packaging.

As for the review, the only issue I see brought up is that there's no README,
which isn't an acceptance blocker. I'm a little unclear as to whether you're
saying that's the only thing missing or if you didn't see any documentation, but
all documentation included in the upstream tarball is included in the rpm
(except the INSTALL doc, which is irrelevant for an rpm).

So basically, as I understand it, you don't see any problems with the package
outside of the lack of an upstream README, and you actually *do* have the power
to approve the package. :)

you are right. Actually i thought some README file should be there that helps
end user to understand what package provides and is that require any dependency
to be installed prior.
Else package is Good.

(In reply to comment #5)
> So basically, as I understand it, you don't see any problems with the package
> outside of the lack of an upstream README, and you actually *do* have the power
> to approve the package. :)

The Package Review Guidelines say:

  The primary Reviewer can be any current package owner, unless the Contributor
  is a first timer.

Somebody that is not sponsored cannot be a current package onwer, hence they
cannot be the *primary* reviewer, hence they cannot approve packages.

Parag is of course encouraged to review packages as part of the process of
getting sponsored, but formally reviewing and approving packages must be done by
an existing package owner.

(In reply to comment #7)
> The Package Review Guidelines say:
> 
>   The primary Reviewer can be any current package owner, unless the Contributor
>   is a first timer.
> 
> Somebody that is not sponsored cannot be a current package onwer, hence they
> cannot be the *primary* reviewer, hence they cannot approve packages.
> 
> Parag is of course encouraged to review packages as part of the process of
> getting sponsored, but formally reviewing and approving packages must be done by
> an existing package owner.


Ah, okay, thank you for the clarification, mistakenly made the leap from being
encouraged to review to being able to approve.

- rpmlint output clean
- Package is named according to Package Naming Guidelines
- spec file matches base package %{name}
- package meets Packaging Guidelines
- package is licensed with open source compatible license
- license field matches actual license
- license text included in %doc
- spec file written in American english
- spec file is legible
- source package matches upstream
b47730a326376cf731c313900095449c  conman-0.1.9.1.tar.bz2
- package successfully compiles and builds on FC-5 x86_64
- All build dependencies are listed
- package does not use locales
- package does not contain any shared libraries
- package is non-relocatable
- package owns all directories it creates
- no duplicate files in %files
- file permissions set appropriately
- contains proper %clean section
- macro usage consistant
- package contains permissible content
- package does not contain large documentation
- %doc files do not affect runtime
- no headers or static libraries
- no pkgconfig files
- no .so or .la files
- no GUI or .desktop file needed
- package does not own files or directories owned by other packages

=== MUST ===
- Package must add "Requires: logrotate"
- service conman start says [ OK ] but there is no conmand process started

Okay, added 'Requires: logrotate' and figured out what was up w/the non-running conmand. The problem 
is that conmand exits cleanly if no CONSOLE devices are defined in /etc/conman.conf, meaning RETVAL 
was 0 (success), so I added a check to the initscript that will trigger a failure if none are present. I'll yell 
upstream and tell them this behavior is el stupido, but the initscript workaround should suffice for now.

http://wilsonet.com/packages/conman/conman.spec
http://wilsonet.com/packages/conman/conman-0.1.9.1-3.src.rpm

I'd do that ckfsv review for you now, but it looks like someone beat me to it... I owe ya one. :)

All must items fixed. APPROVED.

Imported and built for devel, pending cvs branching for other builds.

Built for FC4 and 5, closing ticket.

(In reply to comment #13)
> Built for FC4 and 5, closing ticket.

Please do not remove the FE-ACCEPT blocker.  Thanks.