pcb-20081128-alt4.x86_64	freedesktop-categories	fail	Main Categories consist of those categories that every conforming desktop environment MUST support.(http://standards.freedesktop.org/menu-spec/latest/apa.html). None found in /usr/share/applications/pcb.desktop. please, fix.; 
pcb-20081128-alt4.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/pcb.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated; /usr/share/applications/pcb.desktop: hint: value "Engineering;Electronics;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu; 
pcb-doc-20081128-alt4.x86_64	arch-dep-package-consists-of-usr-share	info	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.; 
pcb-library-20081128-alt4.x86_64	arch-dep-package-consists-of-usr-share	info	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.; 
pcb-library-m4-20081128-alt4.x86_64	arch-dep-package-consists-of-usr-share	info	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.;