Repocop reports by srpm

  rpm id test Status message
eGroupWare-addressbook-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/addressbook/doc/README (80 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.
eGroupWare-bookmarks-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/bookmarks/glist.wml (54 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.
eGroupWare-calendar-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/calendar/egroupware.org/accept_holiday.php (92 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.
eGroupWare-core-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/about.php (702 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.
eGroupWare-developer_tools-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/developer_tools/doc/copyright.gpl (21 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.
eGroupWare-emailadmin-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/emailadmin/inc/class.dbmaildbmailuser.inc.php (39 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.
eGroupWare-filemanager-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/filemanager/cli.php (44 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.
eGroupWare-importexport-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/importexport/doc/README_developers.txt (46 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.
eGroupWare-infolog-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/infolog/inc/class.infolog_bo.inc.php (57 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.
eGroupWare-manual-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/manual/inc/class.uimanual.inc.php (19 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.
eGroupWare-news_admin-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/news_admin/doc/copyright.gpl (55 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.
eGroupWare-notifications-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/notifications/inc/class.notifications.inc.php (30 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.
eGroupWare-phpbrain-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/phpbrain/inc/class.bokb.inc.php (57 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.
eGroupWare-phpsysinfo-1.8-alt6.noarch unsafe-tmp-usage-in-scripts fail The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/share/egroupware/phpsysinfo/tools/GenerateCL.sh: $ grep -A5 -B5 /tmp/ /usr/share/egroupware/phpsysinfo/tools/GenerateCL.sh #!/bin/sh # run this in phpsysinfo home dir # rm -f ChangeLog.bak ChangeLog /tmp/xx.txt /tmp/ChangeLog find . -type f | sed -e 's/\.\///g' | grep -v -w CVS | grep -v -x 'config.php'| grep -v '^tools/' | grep -v -x 'genlog.sh' > /tmp/xx.txt cat /tmp/xx.txt | xargs ./tools/cvs2cl.pl -t -f /tmp/ChangeLog sed -e 's/webbie$/webbie (webbie at ipfw dot org)/g' \ -e 's/precision$/precision Uriah Welcome (precision at users.sf.net)/g' \ -e 's/jengo$/jengo Joseph Engo (jengo at users.sf.net)/g' \ -e 's/neostrider$/neostrider Joseph King (neostrider at users.sf.net)/g' \ -e 's/bigmichi1$/bigmichi1 Michael Cramer (bigmichi1 at users.sf.net)/g' \ /tmp/ChangeLog > ChangeLog rm -f /tmp/xx.txt /tmp/ChangeLog
eGroupWare-projectmanager-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/projectmanager/inc/class.datasource.inc.php (62 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.
eGroupWare-registration-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/registration/doc/README (37 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.
eGroupWare-resources-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/resources/inc/class.bo_acl.inc.php (43 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.
eGroupWare-sambaadmin-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/sambaadmin/inc/class.bosambaadmin.inc.php (15 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.
eGroupWare-sitemgr-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/sitemgr/inc/class.ACL_BO.inc.php (268 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.
eGroupWare-timesheet-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/timesheet/inc/class.timesheet_bo.inc.php (41 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.
eGroupWare-tracker-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/tracker/inc/class.botracker.inc.php (42 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.
eGroupWare-wiki-1.8-alt6.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package egroupware-epl-14.2-alt1.noarch, for example, /usr/share/egroupware/wiki/action/admin.php (82 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.

generated by repocop at Sat May 26 04:40:17 2018