Repocop reports by acl

  packager rpm id test Status message
greycat jabber-common-0.3-alt1.noarch missing-url info Missing Url: in a package.
greycat libqca-1.0-alt4.x86_64 missing-url info Missing Url: in a package.
greycat libqca-debuginfo-1.0-alt4.x86_64 missing-url info Missing Url: in a package.
greycat libqca-devel-1.0-alt4.x86_64 missing-url info Missing Url: in a package.
greycat libqca-devel-1.0-alt4.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libqca.so is different from the same symlink in the package libqca2-devel-2.1.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
greycat psi-0.16-alt1.git1.ccc24db.src specfile-macros-get_dep-is-deprecated experimental Versioned Requires: foo >= %{get_dep something} using %get_dep and %get_version macros on a library are deprecated by set:versions. You probably should drop %get_dep/%get_version Requires: to avoid RPM database pollution.
greycat spt3-0.5-alt2.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/spt-deploy-lilo /usr/bin/spt3
greycat spt3-0.5-alt2.noarch missing-url info Missing Url: in a package.
greycat spt3-profiles-0.5-alt2.noarch missing-url info Missing Url: in a package.
greycat spt3-tasks-0.5-alt2.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/spt-pack-iso /usr/bin/spt-copy-files-to-chroot /usr/bin/spt-make-chroot /usr/bin/spt-boot-propagator
greycat spt3-tasks-0.5-alt2.noarch missing-url info Missing Url: in a package.
zerg libtag-devel-1.11.1-alt1.x86_64 arch-dep-package-has-big-usr-share info The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.

generated by repocop at Tue Feb 13 06:37:54 2018