Repocop reports by srpm

  rpm id test Status message
lightsquid-1.8-alt1.noarch rpm-filesystem-conflict-dir-dir fail directory /etc/lightsquid is a directory in package lightsquid-admin-1.8.0.1-alt2.13.noarch with different user,group or permissions. You should add explicit conflicts.
directory /var/lib/lightsquid is a directory in package lightsquid-admin-1.8.0.1-alt2.13.noarch with different user,group or permissions. You should add explicit conflicts.
directory /var/lock/lightsquid is a directory in package lightsquid-admin-1.8.0.1-alt2.13.noarch with different user,group or permissions. You should add explicit conflicts.
directory /var/www/html/lightsquid is a directory in package lightsquid-admin-1.8.0.1-alt2.13.noarch with different user,group or permissions. You should add explicit conflicts.
lightsquid-1.8-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package lightsquid-admin-1.8.0.1-alt2.13.noarch, for example, /etc/cron.d/lightsquid (45 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
lightsquid-1.8-alt1.noarch subdir-in-var-run info Found a subdir in /var/run or /var/lock. /var/run and /var/lock may be mounted as temporary filesystems, so the init.d scripts must handle this correctly. This will typically amount to creating any required subdirectories dynamically when the init.d script is run, rather than including them in the package and relying on rpm to create them.
lightsquid-apache-1.8-alt1.noarch rpm-filesystem-conflict-file-file warn File /etc/httpd/conf/addon-modules.d/lightsquid.conf conflicts with the package lightsquid-admin-apache-1.8.0.1-alt2.13.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.

generated by repocop at Sat Feb 23 06:30:56 2019