https://bugzilla.redhat.com/show_bug.cgi?id=1135151 --- Comment #6 from David Vossel <dvossel@xxxxxxxxxx> --- MUST: rpmlint must be run on the source rpm and all binary rpms the build produces. The output should be posted in the review.[1] # rpmlint sbd-1.2.1-0.2.8f91294.git.src.rpm sbd.src: W: invalid-license GPL-2.0+ sbd.src:55: W: macro-in-comment %setup sbd.src:55: W: macro-in-comment %{version} no errors MUST: The package must be named according to the Package Naming Guidelines . check MUST: The spec file name must match the base package %{name}, in the format %{name}.spec unless your package has an exemption. [2] . check MUST: The package must meet the Packaging Guidelines . check MUST: The package must be licensed with a Fedora approved license and meet the Licensing Guidelines . check MUST: The License field in the package spec file must match the actual license. [3] check 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.[4] check MUST: The spec file must be written in American English. [5] check MUST: The spec file for the package MUST be legible. [6] check 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. check MUST: The package MUST successfully compile and build into binary rpms on at least one primary architecture. [7] check 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. [8] check 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. check MUST: The spec file MUST handle locales properly. This is done by using the %find_lang macro. Using %{_datadir}/locale/* is strictly forbidden.[9] check 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. [10] check MUST: Packages must NOT bundle copies of system libraries.[11] check 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. [12] check 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. [13] check 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)[14] check MUST: Permissions on files must be set properly. Executables should be set with executable permissions, for example. [15] check MUST: Each package must consistently use macros. [16] check MUST: The package must contain code, or permissible content. [17] check 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). [18] check 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. [18] check MUST: Static libraries must be in a -static package. [19] check MUST: Development files must be in a -devel package. [20] check MUST: In the vast majority of cases, devel packages must require the base package using a fully versioned dependency: Requires: %{name}%{?_isa} = %{version}-%{release} [21] check MUST: Packages must NOT contain any .la libtool archives, these must be removed in the spec if they are built.[19] check 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. [22] check 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. [23] check MUST: All filenames in rpm packages must be valid UTF-8. [24] check -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review