Spec URL: http://siwinski.fedorapeople.org/rpmbuild/SPECS/drupal7-crumbs.spec SRPM URL: http://siwinski.fedorapeople.org/rpmbuild/SRPMS/drupal7-crumbs-1.9-1.fc18.src.rpm Description: Crumbs is a powerful breadcrumb-building machine, generating high-quality breadcrumbs for most every page on your site, with minimal configuration. The Crumbs engine takes advantage of the hierarchical nature inherent to breadcrumbs: It calculates the parent of the current page, the parent of the parent, etc, until it has the complete breadcrumb trail. Crumbs uses plugins with fine-grained user-defined priorities, for each step in this process. Plugins for most of your favorite modules are already built-in, and you can add more. A lot of stuff that would require laborious configuration with other breadcrumb-building modules, does work out of the box with Crumbs. And if it doesn't, there are powerful and ways to configure, customize and extend. Where in other breadcrumb-customizing modules you need to define complete breadcrumbs for various pages and their all their children, in Crumbs you mostly just say "A is the parent of B", and it can solve all the rest of the puzzle by itself. Fedora Account System Username: siwinski
Updated for drupal7-rpmbuild 7.22-5 SPEC URL: http://siwinski.fedorapeople.org/rpmbuild/SPECS/drupal7-crumbs.spec SRPM URL: http://siwinski.fedorapeople.org/rpmbuild/SRPMS/drupal7-crumbs-1.9-2.fc18.src.rpm
Scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=5574992 $ rpmlint -i -v *drupal7-crumbs.src: I: checking drupal7-crumbs.src: I: checking-url http://drupal.org/project/crumbs (timeout 10 seconds) drupal7-crumbs.src: W: invalid-url URL: http://drupal.org/project/crumbs HTTP Error 403: Forbidden The value should be a valid, public HTTP, HTTPS, or FTP URL. drupal7-crumbs.src: I: checking-url http://ftp.drupal.org/files/projects/crumbs-7.x-1.9.tar.gz (timeout 10 seconds) drupal7-crumbs.noarch: I: checking drupal7-crumbs.noarch: I: checking-url http://drupal.org/project/crumbs (timeout 10 seconds) drupal7-crumbs.noarch: W: invalid-url URL: http://drupal.org/project/crumbs HTTP Error 403: Forbidden The value should be a valid, public HTTP, HTTPS, or FTP URL. drupal7-crumbs.spec: I: checking-url http://ftp.drupal.org/files/projects/crumbs-7.x-1.9.tar.gz (timeout 10 seconds) 2 packages and 1 specfiles checked; 0 errors, 2 warnings. The HTTP 403 error is on my side again, the site is available from the Drupal mainpage. --------------------------------- key: [+] OK [.] OK, not applicable [X] needs work --------------------------------- [+] 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. GPLv2+ [+] 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. 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 * c879cac46954c5d440f92bf8d31b7eb989dbf26c1fd74fb8dc9ced2bd0126c36 crumbs-7.x-1.9.tar.gz c879cac46954c5d440f92bf8d31b7eb989dbf26c1fd74fb8dc9ced2bd0126c36 crumbs-7.x-1.9.tar.gz.orig [+] MUST: The package MUST successfully compile and build into binary rpms on at least one primary architecture. [.] 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. [+] 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: Static libraries must be in a -static package. [.] MUST: Development files must be 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}%{?_isa} = %{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. 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. [+] 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. See Koji build above (which uses Mock anyway). [+] SHOULD: The package should compile and build into binary rpms on all supported architectures. [.] 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. ---------------- PACKAGE APPROVED ----------------
THANKS for the review! New Package SCM Request ======================= Package Name: drupal7-crumbs Short Description: The ultimate breadcrumbs module Owners: siwinski asrob Branches: f17 f18 f19 el5 el6 InitialCC:
Git done (by process-git-requests).