Sisyphus repository
Last update: 2017-12-18 13:06:59 +0300 | SRPMs: 18242 | Sign in or Sign up
en ru uk br
Group :: Development/Tools
Source RPM: nvidia-cg-toolkit

 Main   Changelog   Spec   Patches   Sources   Download   Gear   Bugs and FR (0/0)   Repocop 


package id status test message
libcg-3.1_April2012-alt1.x86_64 Ok
ok
sisyphus_check  
libcg-3.1_April2012-alt1.x86_64 Warn
warn
vendor-tag Bad Vendor: tag in a package.;
libcg-3.1_April2012-alt1.x86_64 Ok
ok
unsafe-tmp-usage-in-scripts  
libcg-3.1_April2012-alt1.x86_64 Ok
ok
buildroot  
libcg-devel-3.1_April2012-alt1.noarch Ok
ok
sisyphus_check  
libcg-devel-3.1_April2012-alt1.noarch Warn
warn
vendor-tag Bad Vendor: tag in a package.;
libcg-devel-3.1_April2012-alt1.noarch Ok
ok
unsafe-tmp-usage-in-scripts  
libcg-devel-3.1_April2012-alt1.noarch Ok
ok
buildroot  
libcggl-3.1_April2012-alt1.x86_64 Ok
ok
sisyphus_check  
libcggl-3.1_April2012-alt1.x86_64 Warn
warn
vendor-tag Bad Vendor: tag in a package.;
libcggl-3.1_April2012-alt1.x86_64 Ok
ok
unsafe-tmp-usage-in-scripts  
libcggl-3.1_April2012-alt1.x86_64 Ok
ok
buildroot  
libcggl-devel-3.1_April2012-alt1.noarch Ok
ok
sisyphus_check  
libcggl-devel-3.1_April2012-alt1.noarch Warn
warn
vendor-tag Bad Vendor: tag in a package.;
libcggl-devel-3.1_April2012-alt1.noarch Ok
ok
unsafe-tmp-usage-in-scripts  
libcggl-devel-3.1_April2012-alt1.noarch Ok
ok
buildroot  
nvidia-cg-toolkit-3.1_April2012-alt1.x86_64 Ok
ok
sisyphus_check  
nvidia-cg-toolkit-3.1_April2012-alt1.x86_64 Warn
warn
vendor-tag Bad Vendor: tag in a package.;
nvidia-cg-toolkit-3.1_April2012-alt1.x86_64 Ok
ok
unsafe-tmp-usage-in-scripts  
nvidia-cg-toolkit-3.1_April2012-alt1.x86_64 Ok
ok
buildroot  
nvidia-cg-toolkit-3.1_April2012-alt1.x86_64 Ok
ok
checkbashisms  
nvidia-cg-toolkit-3.1_April2012-alt1.x86_64 Info
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.;
 
© 2009–2017 Igor Zubkov