Bug 678199 - Review Request: perl-Role-Identifiable - Identifiable roles
Summary: Review Request: perl-Role-Identifiable - Identifiable roles
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Traylen
QA Contact: Fedora Extras Quality Assurance
URL: http://search.cpan.org/dist/Role-Iden...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-17 04:49 UTC by Iain Arnell
Modified: 2011-03-05 22:58 UTC (History)
4 users (show)

Fixed In Version: perl-Role-Identifiable-0.005-1.fc14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-03 03:11:12 UTC
Type: ---
Embargoed:
steve.traylen: fedora-review+
j: fedora-cvs+


Attachments (Terms of Use)

Description Iain Arnell 2011-02-17 04:49:23 UTC
Spec URL: http://fedorapeople.org/~iarnell/review/perl-Role-Identifiable.spec
SRPM URL: http://fedorapeople.org/~iarnell/review/perl-Role-Identifiable-0.005-1.fc16.src.rpm

Description:
This module provides several Moose roles for identifying things.

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

*rt-0.10_01

Comment 1 Ken Dreyer 2011-02-19 05:41:45 UTC
Hi Iain,

I'll informally review, just for kicks. I can see you have plenty of packages in Fedora, and this is my first review, so I may miss some things :)


rpmlint is clean on the .spec and the SRPM. I built the RPM successfully in mock on F13 on i686.

$ rpmlint perl-Role-Identifiable-0.005-1.fc13.noarch.rpm
1 packages and 0 specfiles checked; 0 errors, 0 warnings.

$ rpmlint perl-Role-Identifiable-0.005-1.fc13.src.rpm
1 packages and 0 specfiles checked; 0 errors, 0 warnings.

===========================
Fedora Packaging Guidelines
===========================

[+] MUST: rpmlint must be run on the source rpm and all binary rpms the build
produces. The output should be posted in the review.
[+] MUST: The package must be named according to the Package Naming Guidelines
.
[+] MUST: The spec file name must match the base package %{name}, in the format
%{name}.spec unless your package has an exemption.
[+] MUST: The package must meet the Packaging Guidelines .
[+] MUST: The package must be licensed with a Fedora approved license and meet
the Licensing Guidelines .
[+] MUST: The License field in the package spec file must match the actual
license.
[+] MUST: If (and only if) the source package includes the text of the
license(s) in its own file, then that file, containing the text of the
license(s) for the package must be included in %doc.
[+] MUST: The spec file must be written in American English. 
[+] MUST: The spec file for the package MUST be legible. 
[+] MUST: The sources used to build the package must match the upstream source,
as provided in the spec URL. (Yes, md5sum is ab9c638b5413c4eca9ac69017bafc715)
[+] MUST: The package MUST successfully compile and build into binary rpms on
at least one primary architecture. (Yes, F13 i686, though the package is noarch).
[+] MUST: If the package does not successfully compile, build or work on an
architecture, then those architectures should be listed in the spec in
ExcludeArch. Each architecture listed in ExcludeArch MUST have a bug filed in
bugzilla, describing the reason that the package does not compile/build/work on
that architecture. The bug number MUST be placed in a comment, next to the
corresponding ExcludeArch line. 
[+] MUST: All build dependencies must be listed in BuildRequires, except for
any that are listed in the exceptions section of the Packaging Guidelines ;
inclusion of those as BuildRequires is optional. Apply common sense.
[/] MUST: The spec file MUST handle locales properly. This is done by using the
%find_lang macro. Using %{_datadir}/locale/* is strictly forbidden.
[/] MUST: Every binary RPM package (or subpackage) which stores shared library
files (not just symlinks) in any of the dynamic linker's default paths, must
call ldconfig in %post and %postun. 
[+] MUST: Packages must NOT bundle copies of system libraries.
[/] MUST: If the package is designed to be relocatable, the packager must state
this fact in the request for review, along with the rationalization for
relocation of that specific package. Without this, use of Prefix: /usr is
considered a blocker. 
[+] MUST: A package must own all directories that it creates. If it does not
create a directory that it uses, then it should require a package which does
create that directory. 
[+] MUST: A Fedora package must not list a file more than once in the spec
file's %files listings. (Notable exception: license texts in specific
situations)
[+] MUST: Permissions on files must be set properly. Executables should be set
with executable permissions, for example. Every %files section must include a
%defattr(...) line. 
[+] MUST: Each package must consistently use macros. 
[+] MUST: The package must contain code, or permissable content. 
[/] MUST: Large documentation files must go in a -doc subpackage. (The
definition of large is left up to the packager's best judgement, but is not
restricted to size. Large can refer to either size or quantity). 
[+] MUST: If a package includes something as %doc, it must not affect the
runtime of the application. To summarize: If it is in %doc, the program must
run properly if it is not present. 
[/] MUST: Header files must be in a -devel package. 
[/] MUST: Static libraries must be in a -static package. 
[/] MUST: If a package contains library files with a suffix (e.g.
libfoo.so.1.1), then library files that end in .so (without suffix) must go in
a -devel package. 
[/] MUST: In the vast majority of cases, devel packages must require the base
package using a fully versioned dependency: Requires: %{name} =
%{version}-%{release} 
[/] MUST: Packages must NOT contain any .la libtool archives, these must be
removed in the spec if they are built.
[/] MUST: Packages containing GUI applications must include a %{name}.desktop
file, and that file must be properly installed with desktop-file-install in the
%install section. If you feel that your packaged GUI application does not need
a .desktop file, you must put a comment in the spec file with your explanation. 
[/] MUST: Packages must not own files or directories already owned by other
packages.
[+] MUST: All filenames in rpm packages must be valid UTF-8. 
[/] SHOULD: If the source package does not include license text(s) as a
separate file from upstream, the packager SHOULD query upstream to include it. 
[/] SHOULD: The description and summary sections in the package spec file
should contain translations for supported Non-English languages, if available. 
[+] SHOULD: The reviewer should test that the package builds in mock. 
[+] SHOULD: The package should compile and build into binary rpms on all
supported architectures. 

Build tested on i686 (package is noarch).

[+] SHOULD: The reviewer should test that the package functions as described. A
package should not segfault instead of running, for example.
[/] SHOULD: If scriptlets are used, those scriptlets must be sane. This is
vague, and left up to the reviewers judgement to determine sanity. 
[/] SHOULD: Usually, subpackages other than devel should require the base
package using a fully versioned dependency. 
[/] SHOULD: The placement of pkgconfig(.pc) files depends on their usecase, and
this is usually for development purposes, so should be placed in a -devel pkg.
A reasonable exception is that the main pkg itself is a devel tool not
installed in a user runtime, e.g. gcc or gdb. 
[/] SHOULD: If the package has file dependencies outside of /etc, /bin, /sbin,
/usr/bin, or /usr/sbin consider requiring the package which provides the file
instead of the file itself. 
[/] SHOULD: your package should contain man pages for binaries/scripts. If it
doesn't, work with upstream to add them where they make sense.

This package looks OK to me, good job.

Comment 2 Steve Traylen 2011-02-23 18:36:10 UTC
Informal review is good.

APPROVED.

Steve.

Comment 3 Iain Arnell 2011-02-24 04:03:19 UTC
New Package SCM Request
=======================
Package Name: perl-Role-Identifiable
Short Description: Identifiable roles
Owners: iarnell
Branches: f13 f14 f15
InitialCC: perl-sig

Comment 4 Jason Tibbitts 2011-02-24 18:28:51 UTC
Git done (by process-git-requests).

Comment 5 Fedora Update System 2011-02-25 03:51:06 UTC
perl-Role-Identifiable-0.005-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/perl-Role-Identifiable-0.005-1.fc14

Comment 6 Fedora Update System 2011-02-25 03:51:13 UTC
perl-Role-Identifiable-0.005-1.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/perl-Role-Identifiable-0.005-1.fc13

Comment 7 Fedora Update System 2011-02-25 03:51:19 UTC
perl-Role-Identifiable-0.005-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/perl-Role-Identifiable-0.005-1.fc15

Comment 8 Fedora Update System 2011-02-25 08:20:40 UTC
perl-Role-Identifiable-0.005-1.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update perl-Role-Identifiable'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/perl-Role-Identifiable-0.005-1.fc14

Comment 9 Fedora Update System 2011-03-03 03:11:01 UTC
perl-Role-Identifiable-0.005-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2011-03-05 22:57:20 UTC
perl-Role-Identifiable-0.005-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2011-03-05 22:58:03 UTC
perl-Role-Identifiable-0.005-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.