[Bug 850646] Review Request: ghc-blaze-textual - Haskell blaze-textual library

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

Lakshmi Narasimhan <lakshminaras2002@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
              Flags|                            |fedora-review+

--- Comment #2 from Lakshmi Narasimhan <lakshminaras2002@xxxxxxxxx> ---
[+]MUST: rpmlint must be run on every package. The output should be posted in
the review.
rpmlint  -i ghc-blaze-textual-0.2.0.6-1.fc16.src.rpm
ghc-blaze-textual-devel-0.2.0.6-1.fc16.x86_64.rpm 
ghc-blaze-textual-0.2.0.6-1.fc16.x86_64.rpm  ../ghc-blaze-textual.spec 
ghc-blaze-textual.src: W: spelling-error %description -l en_US datatypes ->
data types, data-types, databases
The value of this tag appears to be misspelled. Please double-check.

ghc-blaze-textual.src: W: spelling-error %description -l en_US bytestrings ->
byte strings, byte-strings, restrings
The value of this tag appears to be misspelled. Please double-check.

ghc-blaze-textual-devel.x86_64: W: spelling-error %description -l en_US
datatypes -> data types, data-types, databases
The value of this tag appears to be misspelled. Please double-check.

ghc-blaze-textual-devel.x86_64: W: spelling-error %description -l en_US
bytestrings -> byte strings, byte-strings, restrings
The value of this tag appears to be misspelled. Please double-check.

ghc-blaze-textual.x86_64: W: spelling-error %description -l en_US datatypes ->
data types, data-types, databases
The value of this tag appears to be misspelled. Please double-check.

ghc-blaze-textual.x86_64: W: spelling-error %description -l en_US bytestrings
-> byte strings, byte-strings, restrings
The value of this tag appears to be misspelled. Please double-check.

3 packages and 1 specfiles checked; 0 errors, 6 warnings.

[+]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
[+]MUST: The package must meet the Packaging Guidelines.
        Naming-Yes
        Version-release - Matches
        License - OK
        No prebuilt external bits - OK
        Spec legibity - OK
        Package template - OK
        Arch support - OK
        Libexecdir - OK
        rpmlint - yes
        changelogs - OK
        Source url tag  - OK, validated.
        Build Requires list - OK
        Summary and description - OK
        API documentation - OK, in devel package

[+]MUST: The package must be licensed with a Fedora approved license and meet
the Licensing Guidelines.
BSD license
[+]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.
LICENSE file is included.
[+]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. Reviewers should use sha256sum for this task as it
is used by the sources file once imported into git. If no upstream URL can be
specified for this package, please see the Source URL Guidelines for how to
deal with this.
sha256sum blaze-textual-0.2.0.6.tar.gz
ghc-blaze-textual-0.2.0.6-1.fc16.src/blaze-textual-0.2.0.6.tar.gz 
671c92d82009e917fa7c8294f8672bdd5b881fd8c5cab6926ed1bcf893742999 
blaze-textual-0.2.0.6.tar.gz
671c92d82009e917fa7c8294f8672bdd5b881fd8c5cab6926ed1bcf893742999 
ghc-blaze-textual-0.2.0.6-1.fc16.src/blaze-textual-0.2.0.6.tar.gz
[+]MUST: The package MUST successfully compile and build into binary rpms on at
least one primary architecture.
Built on x86_64. koji builds for f16,f17 and f18 done by packager.
[+]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.
[+]MUST: All build dependencies must be listed in BuildRequires.
[+]MUST: Packages must NOT bundle copies of system libraries.
Checked with rpmquery --list.
[NA]MUST: If the package is designed to be relocatable, the packager must state
this fact in the request for review.
[+]MUST: A package must own all directories that it creates.
Checked with rpmquery --whatprovides.
[+]MUST: A Fedora package must not list a file more than once in the spec
file's %files listings.
[+]MUST: Permissions on files must be set properly. Executables should be set
with executable permissions, for example.
[+]MUST: Each package must consistently use macros.
[+]MUST: The package must contain code, or permissible content.
[+]MUST: Large documentation files must go in a -doc subpackage.
API documentation in -devel package.
[+]MUST: If a package includes something as %doc, it must not affect the
runtime of the application.
[+]MUST: devel packages must require the base package using a fully versioned
dependency: Requires: {name} = %{version}-%{release}
[NA]MUST: Packages must NOT contain any .la libtool archives, these must be
removed in the spec if they are built.
[NA]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
[+]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 items
[+]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 reviewer should test that the package functions as described. A
package should not segfault instead of running, for example.
Loaded Blaze.Text.Double into ghci. Loads fine.
[+]SHOULD: If scriptlets are used, those scriptlets must be sane. This is
vague, and left up to the reviewers judgement to determine sanity.

cabal2spec-diff is OK.

APPROVED.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review



[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]