Репозиторий Sisyphus
Последнее обновление: 4 июня 2020 | Пакетов: 17570 | Посещений: 18691857
en ru br
Майнтейнер: Nikita Ermakov

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

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

пакет статус тест сообщение
acr-1.7.2-alt1.noarch
warn
sisyphus_check-check-dirlist sisyphus_check --check-dirlist failed: package contains a directory /usr/share/vim that exclusively belongs to package vim-common sisyphus_check --check-dirlist failed: package contains a directory /usr/share/vim/vimfiles that exclusively belongs to package vim-common sisyphus_check --check-dirlist failed: package contains a directory /usr/share/vim/vimfiles/ftplugin that exclusively belongs to package vim-common sisyphus_check --check-dirlist failed: package contains a directory /usr/share/vim/vimfiles/syntax that exclusively belongs to package vim-common
altocation-1.0-alt1.noarch
experimental
checkbashisms checkbashisms utility found possible bashisms in: /usr/bin/altocation.sh
capstone-4.0.2-alt1.x86_64
info
beehive-log-unpackaged-files-found-i586 warning: Installed (but unpackaged) file(s) found: /usr/bin/cstool
capstone-4.0.2-alt1.x86_64
info
beehive-log-unpackaged-files-found-x86_64 warning: Installed (but unpackaged) file(s) found: /usr/bin/cstool
capstone-4.0.2-alt1.x86_64
info
altlinux-policy-shared-lib-contains-devel-so SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libcapstone.so but just /usr/lib64/libcapstone.so.4. According to SharedLibs Policy Draft, symlink /usr/lib64/libcapstone.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/libcapstone.so to \%files of capstone-4.0.2-alt1.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.
capstone-4.0.2-alt1.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
clang10.0-10.0.0-alt2.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /usr/bin/clang is different from the same symlink in the package clang9.0-9.0.1-alt3.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/bin/clang is different from the same symlink in the package clang7.0-7.0.1-alt7.rel.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.
clang10.0-10.0.0-alt2.x86_64
warn
rpm-filesystem-conflict-file-file There are file conflicts with the package clang7.0-7.0.1-alt7.rel.x86_64, for example, /usr/bin/c-index-test (9 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. There are file conflicts with the package clang9.0-9.0.1-alt3.x86_64, for example, /usr/bin/c-index-test (11 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.
clang10.0-analyzer-10.0.0-alt2.noarch
warn
rpm-filesystem-conflict-file-file There are file conflicts with the package clang7.0-analyzer-7.0.1-alt7.rel.noarch, for example, /usr/bin/scan-build (7 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. Files /usr/bin/scan-build /usr/libexec/ccc-analyzer conflict with the package clang9.0-analyzer-9.0.1-alt3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
clang10.0-debuginfo-10.0.0-alt2.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /usr/lib/debug/usr/bin/clang++.debug is different from the same symlink in the package clang9.0-debuginfo-9.0.1-alt3.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/bin/clang++.debug is different from the same symlink in the package clang7.0-debuginfo-7.0.1-alt7.rel.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/bin/clang-cl.debug is different from the same symlink in the package clang9.0-debuginfo-9.0.1-alt3.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/bin/clang-cl.debug is different from the sam... [the rest of the message is skipped]
clang10.0-devel-10.0.0-alt2.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /usr/lib64/libclang-cpp.so is different from the same symlink in the package clang9.0-devel-9.0.1-alt3.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/libclang.so is different from the same symlink in the package clang9.0-devel-9.0.1-alt3.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/libclang.so is different from the same symlink in the package clang7.0-devel-7.0.1-alt7.rel.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.
clang10.0-devel-10.0.0-alt2.x86_64
warn
rpm-filesystem-conflict-file-file There are file conflicts with the package clang7.0-devel-7.0.1-alt7.rel.x86_64, for example, /usr/include/clang-c/BuildSystem.h (508 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. There are file conflicts with the package clang9.0-devel-9.0.1-alt3.x86_64, for example, /usr/include/clang-c/BuildSystem.h (235 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.
clang10.0-devel-static-10.0.0-alt2.x86_64
warn
rpm-filesystem-conflict-file-file There are file conflicts with the package clang7.0-devel-static-7.0.1-alt7.rel.x86_64, for example, /usr/lib64/libclangARCMigrate.a (29 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. There are file conflicts with the package clang9.0-devel-static-9.0.1-alt3.x86_64, for example, /usr/lib64/libclangARCMigrate.a (33 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.
clang10.0-doc-10.0.0-alt2.noarch
warn
rpm-filesystem-conflict-file-file There are file conflicts with the package clang7.0-doc-7.0.1-alt7.rel.noarch, for example, /usr/share/doc/clang/html/AddressSanitizer.html (113 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. There are file conflicts with the package clang9.0-doc-9.0.1-alt3.noarch, for example, /usr/share/doc/clang/html/AddressSanitizer.html (99 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.
clang10.0-libs-10.0.0-alt2.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
cppunit-1.15.1-alt1.x86_64
info
beehive-log-unpackaged-files-found-i586 warning: Installed (but unpackaged) file(s) found: /usr/share/cppunit/html/_additional_message_8cpp.html /usr/share/cppunit/html/_additional_message_8cpp__incl.map /usr/share/cppunit/html/_additional_message_8cpp__incl.md5 /usr/share/cppunit/html/_additional_message_8cpp__incl.png /usr/share/cppunit/html/_additional_message_8h.html /usr/share/cppunit/html/_additional_message_8h__dep__incl.map /usr/share/cppunit/html/_additional_message_8h__dep__incl.md5 /usr/share/cppunit/html/_additional_message_8h__dep__incl.png /usr/share/cppunit/html/_additional_message_8h__incl.map /usr/share/cppunit/html/_additional_message_8h__incl.md5 /usr/share/cppunit/html/_additional_message_8h__incl.png /usr/share/cppunit/html/_additional_message_8h_source.html /usr/share/cppunit/html/_algorithm_8h.html /usr/share/cppunit/html/_algorithm_8h__dep__incl.map /usr/share/cppunit/html/_algorithm_8h__dep__incl.md5 /usr/share/cppunit/html/_algorithm_8h__dep__incl.png /usr/share/cppunit/html/_algorithm_8h__incl.map ... [the rest of the message is skipped]
cppunit-1.15.1-alt1.x86_64
info
beehive-log-unpackaged-files-found-x86_64 warning: Installed (but unpackaged) file(s) found: /usr/share/cppunit/html/_additional_message_8cpp.html /usr/share/cppunit/html/_additional_message_8cpp__incl.map /usr/share/cppunit/html/_additional_message_8cpp__incl.md5 /usr/share/cppunit/html/_additional_message_8cpp__incl.png /usr/share/cppunit/html/_additional_message_8h.html /usr/share/cppunit/html/_additional_message_8h__dep__incl.map /usr/share/cppunit/html/_additional_message_8h__dep__incl.md5 /usr/share/cppunit/html/_additional_message_8h__dep__incl.png /usr/share/cppunit/html/_additional_message_8h__incl.map /usr/share/cppunit/html/_additional_message_8h__incl.md5 /usr/share/cppunit/html/_additional_message_8h__incl.png /usr/share/cppunit/html/_additional_message_8h_source.html /usr/share/cppunit/html/_algorithm_8h.html /usr/share/cppunit/html/_algorithm_8h__dep__incl.map /usr/share/cppunit/html/_algorithm_8h__dep__incl.md5 /usr/share/cppunit/html/_algorithm_8h__dep__incl.png /usr/share/cppunit/html/_algorithm_8h__incl.map ... [the rest of the message is skipped]
gd3-2.3.0-alt2.x86_64
warn
altlinux-policy-obsolete-buildreq Build dependency on rpm-build-ubt is obsolete and should be dropped to get rid of rpm-build-ubt package.
lld10.0-10.0.0-alt2.x86_64
warn
rpm-filesystem-conflict-file-file File /usr/bin/lld conflicts with the package lld7.0-7.0.1-alt7.rel.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. File /usr/bin/lld conflicts with the package lld9.0-9.0.1-alt3.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.
lld10.0-devel-10.0.0-alt2.x86_64
warn
rpm-filesystem-conflict-file-file There are file conflicts with the package lld7.0-devel-7.0.1-alt7.rel.x86_64, for example, /usr/include/lld/Common/Args.h (33 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. There are file conflicts with the package lld9.0-devel-9.0.1-alt3.x86_64, for example, /usr/include/lld/Common/Driver.h (12 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.
llvm10.0-10.0.0-alt2.x86_64
warn
rpm-filesystem-conflict-file-file There are file conflicts with the package llvm7.0-7.0.1-alt7.rel.x86_64, for example, /usr/bin/bugpoint (78 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. There are file conflicts with the package llvm9.0-9.0.1-alt3.x86_64, for example, /usr/bin/bugpoint (75 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.
llvm10.0-10.0.0-alt2.x86_64
info
beehive-log-unpackaged-files-found-i586 warning: Installed (but unpackaged) file(s) found: /usr/share/clang/bash-autocomplete.sh /usr/share/clang/clang-format-bbedit.applescript /usr/share/clang/clang-format-diff.py /usr/share/clang/clang-format-sublime.py /usr/share/clang/clang-format.el /usr/share/clang/clang-format.py /usr/share/clang/clang-rename.el /usr/share/clang/clang-rename.py /usr/share/opt-viewer/opt-diff.py /usr/share/opt-viewer/opt-stats.py /usr/share/opt-viewer/opt-viewer.py /usr/share/opt-viewer/optpmap.py /usr/share/opt-viewer/optrecord.py /usr/share/opt-viewer/style.css
llvm10.0-10.0.0-alt2.x86_64
info
beehive-log-unpackaged-files-found-x86_64 warning: Installed (but unpackaged) file(s) found: /usr/share/clang/bash-autocomplete.sh /usr/share/clang/clang-format-bbedit.applescript /usr/share/clang/clang-format-diff.py /usr/share/clang/clang-format-sublime.py /usr/share/clang/clang-format.el /usr/share/clang/clang-format.py /usr/share/clang/clang-rename.el /usr/share/clang/clang-rename.py /usr/share/opt-viewer/opt-diff.py /usr/share/opt-viewer/opt-stats.py /usr/share/opt-viewer/opt-viewer.py /usr/share/opt-viewer/optpmap.py /usr/share/opt-viewer/optrecord.py /usr/share/opt-viewer/style.css
llvm10.0-devel-10.0.0-alt2.x86_64
warn
rpm-filesystem-conflict-symlink-symlink value of symlink /usr/lib64/libLLVM.so is different from the same symlink in the package llvm9.0-devel-9.0.1-alt3.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/libLLVM.so is different from the same symlink in the package llvm7.0-devel-7.0.1-alt7.rel.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/libLTO.so is different from the same symlink in the package llvm9.0-devel-9.0.1-alt3.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/libLTO.so is different from the same symlink in the package llvm7.0-devel-7.0.1-alt7.rel.x86_64. Moreover, the pac... [the rest of the message is skipped]
llvm10.0-devel-10.0.0-alt2.x86_64
warn
rpm-filesystem-conflict-file-file There are file conflicts with the package llvm7.0-devel-7.0.1-alt7.rel.x86_64, for example, /usr/bin/llvm-config (1202 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. There are file conflicts with the package llvm9.0-devel-9.0.1-alt3.x86_64, for example, /usr/bin/llvm-config (595 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.
llvm10.0-devel-static-10.0.0-alt2.x86_64
warn
rpm-filesystem-conflict-file-file There are file conflicts with the package llvm7.0-devel-static-7.0.1-alt7.rel.x86_64, for example, /usr/lib64/libLLVMAMDGPUAsmParser.a (88 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. There are file conflicts with the package llvm9.0-devel-static-9.0.1-alt3.x86_64, for example, /usr/lib64/libLLVMAMDGPUAsmParser.a (94 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.
llvm10.0-doc-10.0.0-alt2.noarch
warn
rpm-filesystem-conflict-file-file There are file conflicts with the package llvm7.0-doc-7.0.1-alt7.rel.noarch, for example, /usr/share/doc/llvm/html/AMDGPUOperandSyntax.html (277 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. There are file conflicts with the package llvm9.0-doc-9.0.1-alt3.noarch, for example, /usr/share/doc/llvm/html/AMDGPU/AMDGPUAsmGFX10.html (721 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.
llvm10.0-libs-10.0.0-alt2.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
pinentry-common-1.1.0-alt5.x86_64
experimental
checkbashisms checkbashisms utility found possible bashisms in: /usr/bin/pinentry
pythia8-8.243-alt2.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.
qt5-base-5.12.8-alt4.x86_64
warn
altlinux-policy-obsolete-buildreq Build dependency on rpm-build-ubt is obsolete and should be dropped to get rid of rpm-build-ubt package.
qt5-base-doc-5.12.8-alt4.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.
qt5-declarative-5.12.8-alt3.x86_64
warn
altlinux-policy-obsolete-buildreq Build dependency on rpm-build-ubt is obsolete and should be dropped to get rid of rpm-build-ubt package.
qt5-declarative-doc-5.12.8-alt3.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.
radare2-4.4.0-alt1.x86_64
info
altlinux-policy-shared-lib-contains-devel-so SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libr_anal.so but just /usr/lib64/libr_anal.so.4.4.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libr_anal.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/libr_anal.so to \%files of radare2-4.4.0-alt1.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/libr_asm.so but just /usr/lib64/libr_asm.so.4.4.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libr_asm.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just app... [the rest of the message is skipped]
radare2-4.4.0-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.
root6-6.19.01-alt3.x86_64
warn
rpm-filesystem-conflict-file-file File /usr/bin/roots conflicts with the package arprec-2.2.19-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.
root6-6.19.01-alt3.x86_64
info
beehive-log-unpackaged-files-found-x86_64 warning: Installed (but unpackaged) file(s) found: /usr/share/doc/root/CREDITS /usr/share/doc/root/INSTALL /usr/share/doc/root/LICENSE /usr/share/doc/root/README /usr/share/doc/root/README.ALIEN /usr/share/doc/root/README.AUTH /usr/share/doc/root/README.CXXMODULES.md /usr/share/doc/root/README.MONALISA /usr/share/doc/root/README.SELECTOR /usr/share/doc/root/ReleaseNotes/empty.md /usr/share/doc/root/ReleaseNotes/old/ChangeLog-2-24 /usr/share/doc/root/ReleaseNotes/v604/colz0.png /usr/share/doc/root/ReleaseNotes/v604/index.md /usr/share/doc/root/ReleaseNotes/v604/nostackb.png /usr/share/doc/root/ReleaseNotes/v604/palette_100.png /usr/share/doc/root/ReleaseNotes/v604/palette_101.png /usr/share/doc/root/ReleaseNotes/v604/palette_102.png /usr/share/doc/root/ReleaseNotes/v604/palette_103.png /usr/share/doc/root/ReleaseNotes/v604/palette_104.png /usr/share/doc/root/ReleaseNotes/v604/palette_105.png /usr/share/doc/root/ReleaseNotes/v604/palette_106.png /usr/share/doc/root/ReleaseNotes/v604/pale... [the rest of the message is skipped]
root6-6.19.01-alt3.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.
root6-6.19.01-alt3.x86_64
info
bin-permissions not executable file /usr/bin/setxrd.csh not executable file /usr/bin/setxrd.sh not executable file /usr/bin/thisroot.csh not executable file /usr/bin/thisroot.fish not executable file /usr/bin/thisroot.sh
root6-6.19.01-alt3.x86_64
experimental
checkbashisms checkbashisms utility found possible bashisms in: /usr/bin/proofserv /usr/bin/roots
runns-1.2-alt1.x86_64
experimental
checkbashisms checkbashisms utility found possible bashisms in: /usr/bin/clean-net
sandbox-2.18-alt1.x86_64
warn
rpm-filesystem-conflict-file-file File /usr/bin/sandbox conflicts with the package policycoreutils-sandbox-3.0-alt2.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.
sandbox-2.18-alt1.x86_64
info
beehive-log-unpackaged-files-found-i586 warning: Installed (but unpackaged) file(s) found: /usr/share/applications/sandbox.desktop /usr/share/pixmaps/sandbox.svg
sandbox-2.18-alt1.x86_64
info
beehive-log-unpackaged-files-found-x86_64 warning: Installed (but unpackaged) file(s) found: /usr/share/applications/sandbox.desktop /usr/share/pixmaps/sandbox.svg
xrootd-4.9.1-alt1.x86_64
info
altlinux-policy-shared-lib-contains-devel-so SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libXrdAppUtils.so but just /usr/lib64/libXrdAppUtils.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libXrdAppUtils.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/libXrdAppUtils.so to \%files of xrootd-4.9.1-alt1.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/libXrdCl.so but just /usr/lib64/libXrdCl.so.2.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libXrdCl.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib
xrootd-4.9.1-alt1.x86_64
info
beehive-log-unpackaged-files-found-i586 warning: Installed (but unpackaged) file(s) found: /usr/lib/libXrdHttpTPC-4.so
xrootd-4.9.1-alt1.x86_64
info
beehive-log-unpackaged-files-found-x86_64 warning: Installed (but unpackaged) file(s) found: /usr/lib64/libXrdHttpTPC-4.so
xrootd-devel-4.9.1-alt1.x86_64
info
altlinux-policy-shared-lib-contains-devel-so SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libXrdCryptoLite.so but just /usr/lib64/libXrdCryptoLite.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libXrdCryptoLite.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/libXrdCryptoLite.so to \%files of xrootd-devel-4.9.1-alt1.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/libXrdHttpUtils.so but just /usr/lib64/libXrdHttpUtils.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libXrdHttpUtils.so should be placed in a special subpackage named lib-devel. If you have alre... [the rest of the message is skipped]
 
дизайн и разработка: Vladimir Lettiev aka crux © 2004-2005, Andrew Avramenko aka liks © 2007-2008
текущий майнтейнер: Michael Shigorin