[Bug 728649] Review Request: airrac - C++ Simulated Revenue Accounting (RAC) System Library

Thu Aug 18 13:24:09 UTC 2011

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

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

Martin Krizek <mkrizek at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mkrizek at redhat.com

Bug 728649 depends on bug 702987, which changed state.

Bug 702987 Summary: Review Request: stdair - C++ Standard Airline IT Library
https://bugzilla.redhat.com/show_bug.cgi?id=702987

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
         Resolution|                            |ERRATA
             Status|ON_QA                       |CLOSED

--- Comment #1 from Martin Krizek <mkrizek at redhat.com> 2011-08-18 09:24:08 EDT ---
Hi Denis,
*informal* review follows:

[ OK ] MUST: rpmlint must be run on the source rpm and all binary rpms the
build produces. The output should be posted in the review.
$ rpmlint rpmbuild/SPECS/airrac.spec Downloads/airrac-0.1.0-1.fc15.src.rpm 
1 packages and 1 specfiles checked; 0 errors, 0 warnings.
[ OK ] MUST: The package must be named according to the Package Naming
Guidelines.
[ BAD ] MUST: The spec file name must match the base package %{name}, in the
format %{name}.spec unless your package has an exemption. ===> Needs to be
renamed to airrac.spec
[ OK ] MUST: The package must meet the Packaging Guidelines.
[ OK ] MUST: The package must be licensed with a Fedora approved license and
meet the Licensing Guidelines.
[ OK ] MUST: The License field in the package spec file must match the actual
license.
[ OK ] 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.
[ OK ] MUST: The spec file must be written in American English.
[ OK ] MUST: The spec file for the package MUST be legible.
[ OK ] MUST: The sources used to build the package must match the upstream
source, as provided in the spec URL. Reviewers should use md5sum for this task.
If no upstream URL can be specified for this package, please see the Source URL
Guidelines for how to deal with this.
[ BAD ] MUST: The package MUST successfully compile and build into binary rpms
on at least one primary architecture.
[ BAD ] 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.
===> I could not build rpm from provided srpm using 'mock -r fedora-15-x86_64
--rebuild airrac-0.1.0-1.fc15.src.rpm' -- seems like problem with tex, sorry if
it was my bad due to unapproriate usage of mock.
[ OK ] 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.
[ NA ] MUST: The spec file MUST handle locales properly. This is done by using
the %find_lang macro. Using %{_datadir}/locale/* is strictly forbidden.
[ OK ] 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.
[ OK ] MUST: Packages must NOT bundle copies of system libraries.
[ OK ] 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.
[ OK ] 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.
[ OK ] 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)
[ OK ] MUST: Permissions on files must be set properly. Executables should be
set with executable permissions, for example.
[ OK ] MUST: Each package must consistently use macros.
[ OK ] MUST: The package must contain code, or permissable content.
[ OK ] 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).
[ OK ] 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.
[ OK ] MUST: Header files must be in a -devel package.
[ OK ] MUST: Static libraries must be in a -static package.
[ OK ] 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.
[ OK ] MUST: In the vast majority of cases, devel packages must require the
base package using a fully versioned dependency: Requires: %{name}%{?_isa} =
%{version}-%{release}
[ BAD ] MUST: Packages must NOT contain any .la libtool archives, these must be
removed in the spec if they are built. ===> I am not sure about that, are there
any .la archives created? If not, consider it as OK.
[ OK ] 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.
[ OK ] MUST: Packages must not own files or directories already owned by other
packages. The rule of thumb here is that the first package to be installed
should own the files or directories that other packages may rely upon. This
means, for example, that no package in Fedora should ever share ownership with
any of the files or directories owned by the filesystem or man package. If you
feel that you have a good reason to own a file or directory that another
package owns, then please present that at package review time.
[ OK ] MUST: All filenames in rpm packages must be valid UTF-8.

[ BAD ] 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.
===> No license file included.
[ OK ] SHOULD: The description and summary sections in the package spec file
should contain translations for supported Non-English languages, if available.
[ BAD ] SHOULD: The reviewer should test that the package builds in mock. ===>
As stated above.
[ BAD ] SHOULD: The package should compile and build into binary rpms on all
supported architectures. ===> As stated above.
[ OK ] SHOULD: The reviewer should test that the package functions as
described. A package should not segfault instead of running, for example.
[ OK ] SHOULD: If scriptlets are used, those scriptlets must be sane. This is
vague, and left up to the reviewers judgement to determine sanity.
[ BAD ] SHOULD: Usually, subpackages other than devel should require the base
package using a fully versioned dependency. ===> doc package doesn't require
the base package.
[ OK ] 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.
[ OK ] 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.
[ OK ] SHOULD: your package should contain man pages for binaries/scripts. If
it doesn't, work with upstream to add them where they make sense.

-- 
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.