Репозиторий Sisyphus
Последнее обновление: 23 февраля 2018 | Пакетов: 18213 | Посещений: 11016455
en ru br
Майнтейнер: Evgeny Sinelnikov

 Информация   Пакеты   Bugs and FR  Repocop 

Сообщения от repocop:

пакет статус тест сообщение
Miro-3.5.0-alt3.1.x86_64
info
freedesktop-desktop desktop-file-validate utility printed the following message(s): /usr/share/applications/miro.desktop: hint: value item "TV" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: AudioVideo;Video /usr/share/applications/miro.desktop: hint: value item "P2P" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Network /usr/share/applications/miro.desktop: hint: value item "News" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Network /usr/share/applications/miro.desktop: hint: value item "FileTransfer" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Network
Miro-3.5.0-alt3.1.x86_64
info
arch-dep-package-has-big-usr-share 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.
Tartarus-dnsupdate-0.1.0-alt0.3.2.1.x86_64
fail
init-lsb /etc/rc.d/init.d/tdnsupdate: not systemd compatible: lsb init header missing and tdnsupdate.service is not present. See http://www.altlinux.org/Services_Policy for details.
Tartarus-dnsupdate-0.1.0-alt0.3.2.1.x86_64
info
init-but-no-native-systemd The package have SysV init script(s) but no native systemd files.
alterator-net-functions-2.0.2-alt1.noarch
experimental
checkbashisms checkbashisms utility found possible bashisms in: /usr/bin/alterator-net-functions
apt-conf-tmp-cache-1.0-alt1.noarch
warn
systemd-but-no-native-init The package have native systemd file(s) but no SysV init scripts.
kbibtex-0.4.1-alt1.x86_64
info
freedesktop-desktop desktop-file-validate utility printed the following message(s): /usr/share/applications/kde4/kbibtex.desktop: hint: value "Qt;KDE;Office;Database;Science;Literature;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
kile-2.1.3-alt1.x86_64
info
dbus-xml-not-in-devel file /usr/share/dbus-1/interfaces/net.sourceforge.kile.main.xml is not used in run time. Move it to the -devel subpackage.
kile-2.1.3-alt1.x86_64
info
arch-dep-package-has-big-usr-share 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.
krb5-kdc-1.16-alt1.S1.x86_64
warn
init-lsb /etc/rc.d/init.d/kadmin: lsb init header missing. /etc/rc.d/init.d/kprop: lsb init header missing. /etc/rc.d/init.d/krb5kdc: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.
lesstif-0.95.2-alt3.x86_64
info
library-pkgnames package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs
libdbus-c++-apidocs-0.9.0-alt1.1.x86_64
info
arch-dep-package-consists-of-usr-share The package consists 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.
libmapi-2.4-alt22.zentyal23.S1.5.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /usr/lib64/libmapi.so.0 is different from the same symlink in the package zarafa-client-7.1.15-alt17.S1.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.
libmapi-debuginfo-2.4-alt22.zentyal23.S1.5.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /usr/lib/debug/usr/lib64/libmapi.so.0.debug is different from the same symlink in the package zarafa-client-debuginfo-7.1.15-alt17.S1.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.
libnss-fallback-0.0.1-alt2.qa1.i586
info
beehive-log-unpackaged-files-found-x86_64 warning: Installed (but unpackaged) file(s) found: /lib64/libnss_fallback.so
libselinux-2.5-alt4.x86_64
info
subdir-in-var-run 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.
libsss_autofs-1.15.3-alt5.S1.x86_64
warn
systemd-but-no-native-init The package have native systemd file(s) but no SysV init scripts.
libsss_sudo-1.15.3-alt5.S1.x86_64
warn
systemd-but-no-native-init The package have native systemd file(s) but no SysV init scripts.
libv-devel-1.90-alt9.2.x86_64
warn
windows-thumbnail-database-in-package /usr/share/doc/libv-devel-1.90/fig/Thumbs.db: It is the file in the package named Thumbs.db or Thumbs.db.gz, which is normally a Windows image thumbnail database. Such databases are generally useless in packages and were usually accidentally included by copying complete directories from the source tarball.
libwbclient-4.6.12-alt2.S1.x86_64
info
alt-alternatives-vs-ghost Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-sssd-1.15.3-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.13 is an alternative in package libwbclient-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.13. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.13 is an alternative in package libwbclient-DC-4.6.12-alt2.S1.x... [the rest of the message is skipped]
libwbclient-DC-4.6.12-alt2.S1.x86_64
info
alt-alternatives-vs-ghost Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-sssd-1.15.3-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.13 is an alternative in package libwbclient-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.13. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.13 is an alternative in package libwbclient-DC-4.6.12-alt2.S1.x... [the rest of the message is skipped]
libwbclient-DC-debuginfo-4.6.12-alt2.S1.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.13.debug is different from the same symlink in the package libwbclient-debuginfo-4.6.12-alt2.S1.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. value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-sssd-debuginfo-1.15.3-alt5.S1.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. value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-debuginfo-4.6.12-alt2.S1.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.
libwbclient-DC-devel-4.6.12-alt2.S1.x86_64
info
alt-alternatives-vs-ghost Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-sssd-devel-1.15.3-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-DC-devel-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-devel-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
libwbclient-debuginfo-4.6.12-alt2.S1.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.13.debug is different from the same symlink in the package libwbclient-DC-debuginfo-4.6.12-alt2.S1.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. value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-sssd-debuginfo-1.15.3-alt5.S1.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. value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-DC-debuginfo-4.6.12-alt2.S1.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.
libwbclient-devel-4.6.12-alt2.S1.x86_64
info
alt-alternatives-vs-ghost Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-sssd-devel-1.15.3-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-DC-devel-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-devel-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
libwbclient-sssd-1.15.3-alt5.S1.x86_64
info
alt-alternatives-vs-ghost Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.13.0 is an alternative in package libwbclient-sssd-1.15.3-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.13.0. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-sssd-1.15.3-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-DC-4.6.12-alt... [the rest of the message is skipped]
libwbclient-sssd-debuginfo-1.15.3-alt5.S1.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-DC-debuginfo-4.6.12-alt2.S1.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. value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-debuginfo-4.6.12-alt2.S1.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.
libwbclient-sssd-devel-1.15.3-alt5.S1.x86_64
info
alt-alternatives-vs-ghost Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-sssd-devel-1.15.3-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-DC-devel-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so. Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-devel-4.6.12-alt2.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
mcpp-doc-2.7.2-alt2.3.x86_64
info
arch-dep-package-consists-of-usr-share The package consists 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.
noip-2.1.9-alt2.x86_64
info
init-but-no-native-systemd The package have SysV init script(s) but no native systemd files.
noip-2.1.9-alt2.x86_64
experimental
checkbashisms checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/noip
nss-tartarus-daemon-0.1.1-alt3.6.1.1.x86_64
fail
init-lsb /etc/rc.d/init.d/tnscd: not systemd compatible: lsb init header missing and tnscd.service is not present. See http://www.altlinux.org/Services_Policy for details.
nss-tartarus-daemon-0.1.1-alt3.6.1.1.x86_64
info
init-but-no-native-systemd The package have SysV init script(s) but no native systemd files.
nss-tartarus-daemon-0.1.1-alt3.6.1.1.x86_64
info
subdir-in-var-run 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.
nss-tartarus-daemon-0.1.1-alt3.6.1.1.x86_64
experimental
checkbashisms checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/tnscd
openchange-devel-2.4-alt22.zentyal23.S1.5.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /usr/lib64/libmapi.so is different from the same symlink in the package monetdb-common-11.27.11-alt1.1.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. value of symlink /usr/lib64/libmapi.so is different from the same symlink in the package zarafa-devel-7.1.15-alt17.S1.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.
openchange-ocsmanager-2.4-alt22.zentyal23.S1.5.x86_64
info
init-but-no-native-systemd The package have SysV init script(s) but no native systemd files.
ponyprog2000-2.07c-alt4.i586
info
requires-ImageMagick Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell.
python-module-openchange-2.4-alt22.zentyal23.S1.5.x86_64
info
altlinux-python-test-is-packaged /usr/lib64/python2.7/site-packages/openchange/tests/test_mailbox.py: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details. /usr/lib64/python2.7/site-packages/openchange/tests/test_mailbox.pyc: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build other packages. See http://www.altlinux.org/Python_Policy for details. /usr/lib64/python2.7/site-packages/openchange/tests/test_mailbox.pyo: It is the file in the package whose name matches the format python modules use for test files. It may have been installed by accident. Remove it or move it to the -devel subpackage, if the test is required to build othe... [the rest of the message is skipped]
python-module-pyldb-1.1.29-alt3.S1.x86_64
info
library-pkgnames package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs
samba-DC-4.6.12-alt2.S1.x86_64
info
arch-dep-package-has-big-usr-share 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.
samba-DC-common-4.6.12-alt2.S1.x86_64
info
subdir-in-var-run 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.
samba-DC-winbind-clients-4.6.12-alt2.S1.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /lib64/libnss_winbind.so.2 is different from the same symlink in the package samba-winbind-clients-4.6.12-alt2.S1.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. value of symlink /lib64/libnss_wins.so.2 is different from the same symlink in the package samba-winbind-clients-4.6.12-alt2.S1.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.
samba-client-libs-4.6.12-alt2.S1.x86_64
info
library-pkgnames package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs
samba-common-4.6.12-alt2.S1.noarch
info
subdir-in-var-run 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.
samba-winbind-clients-4.6.12-alt2.S1.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /lib64/libnss_winbind.so.2 is different from the same symlink in the package samba-DC-winbind-clients-4.6.12-alt2.S1.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. value of symlink /lib64/libnss_wins.so.2 is different from the same symlink in the package samba-DC-winbind-clients-4.6.12-alt2.S1.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.
samba-winbind-clients-4.6.12-alt2.S1.x86_64
info
altlinux-policy-shared-lib-contains-devel-so SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libnss_winbind.so but just /usr/lib64/libnss_winbind.so.2. According to SharedLibs Policy Draft, symlink /usr/lib64/libnss_winbind.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libnss_winbind.so to \%files of samba-winbind-clients-4.6.12-alt2.S1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test. SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libnss_wins.so but just /usr/lib64/libnss_wins.so.2. According to SharedLibs Policy Draft, symlink /usr/lib64/libnss_wins.so should be placed in a special subpackage named lib-devel. If you have already packaged th... [the rest of the message is skipped]
socket_wrapper-1.1.8-alt2.S1.x86_64
info
altlinux-policy-shared-lib-contains-devel-so SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libsocket_wrapper.so but just /usr/lib64/libsocket_wrapper.so.0.1.8. According to SharedLibs Policy Draft, symlink /usr/lib64/libsocket_wrapper.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libsocket_wrapper.so to \%files of socket_wrapper-1.1.8-alt2.S1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.
sssd-1.15.3-alt5.S1.x86_64
experimental
systemd-check-socket-name in sssd-1.15.3-alt5.S1.x86_64: there is a socket sssd-pam-priv.socket but no service sssd-pam-priv.service. Ask ildar@ why it is not right.
sssd-kcm-1.15.3-alt5.S1.x86_64
warn
systemd-but-no-native-init The package have native systemd file(s) but no SysV init scripts.
sssd-pac-1.15.3-alt5.S1.x86_64
warn
systemd-but-no-native-init The package have native systemd file(s) but no SysV init scripts.
 
дизайн и разработка: Vladimir Lettiev aka crux © 2004-2005, Andrew Avramenko aka liks © 2007-2008
текущий майнтейнер: Michael Shigorin