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=680473 Lakshmi Narasimhan <lakshminaras2002@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |needinfo?(shakthimaan@gmail | |.com) --- Comment #2 from Lakshmi Narasimhan <lakshminaras2002@xxxxxxxxx> 2011-02-27 01:16:27 EST --- [+]MUST: rpmlint must be run on every package. The output should be posted in the review. rpmlint -i *.rpm *.spec ghc-ForSyDe.i686: W: spelling-error Summary(en_US) Haskell -> Gaskell, Gaitskell, Skellum The value of this tag appears to be misspelled. Please double-check. ghc-ForSyDe.src: W: spelling-error Summary(en_US) Haskell -> Gaskell, Gaitskell, Skellum The value of this tag appears to be misspelled. Please double-check. ghc-ForSyDe-prof.i686: E: devel-dependency ghc-ForSyDe-devel Your package has a dependency on a devel package but it's not a devel package itself. ghc-ForSyDe-prof.i686: W: no-documentation The package contains no documentation (README, doc, etc). You have to include documentation files. ghc-ForSyDe-prof.i686: W: devel-file-in-non-devel-package /usr/lib/ghc-6.12.3/ForSyDe-3.1.1/libHSForSyDe-3.1.1_p.a A development file (usually source code) is located in a non-devel package. If you want to include source code in your package, be sure to create a development package. 4 packages and 1 specfiles checked; 1 errors, 4 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. Buildroot is ignored - OK %clean is ignored - OK Build Requires list - NOT OK, missed ghc-mtl Summary and description - OK API documentation - OK [+]MUST: The package must be licensed with a Fedora approved license and meet the Licensing Guidelines . Licensed with 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. Yes. The license text is present in LICENSE file. [+]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 md5sum for this task. md5sum ghc-ForSyDe-3.1.1-1.fc14.src/ForSyDe-3.1.1.tar.gz d215f444893538842cc30c68601036cb ghc-ForSyDe-3.1.1-1.fc14.src/ForSyDe-3.1.1.tar.gz md5sum ~/Downloads/ForSyDe-3.1.1.tar.gz d215f444893538842cc30c68601036cb ~/Downloads/ForSyDe-3.1.1.tar.gz [+]MUST: The package MUST successfully compile and build into binary rpms on at least one primary architecture. Built on i686. [+]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. ghc-mtl is missing. [NA]MUST: The spec file MUST handle locales properly using the %find_lang macro [NA]MUST: Packages stores shared library files must call ldconfig in %post and %postun. [+]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. [+]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. [+]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. [+]MUST: If a package includes something as %doc, it must not affect the runtime of the application. [+]MUST: Header files must be in a -devel package. [NA]MUST: Static libraries must be in a -static package. [NA]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: devel packages must require the base package using a fully versioned dependency: Requires: {name} = %{version}-%{release} rpm -e ghc-ForSyDe error: Failed dependencies: ghc-ForSyDe = 3.1.1-1.fc14 is needed by (installed) ghc-ForSyDe-devel-3.1.1-1.fc14.i686 rpm -e ghc-ForSyDe-devel error: Failed dependencies: ghc-ForSyDe-devel = 3.1.1-1.fc14 is needed by (installed) ghc-ForSyDe-prof-3.1.1-1.fc14.i686 [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 reviewer should test that the package functions as described. Installed the packages. Installs fine. Loaded ForSyDe.Process into ghci. Works fine [+]SHOULD: If scriptlets are used, those scriptlets must be sane. cabal2spec-diff is OK. Overall comments, 1) Should forsyde.vhd file go with the base package or the devel package? If it goes with the base package, the devel package will get it automatically. My doubt is that whether the code in the .so would need the vhd file. 2) ghc-mtl is also a dependency but pulled in indirectly. But cabal states it as an explicit dep. Please add it to BuildRequires. -- 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. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review