| rpm id | test | Status | message | |
|---|---|---|---|---|
 |
fcitx-4.2.7-alt2.1.x86_64 | checkbashisms | experimental | checkbashisms utility found possible bashisms in: /usr/bin/fcitx-skin-installer /usr/bin/fcitx-configtool |
 |
fcitx-4.2.7-alt2.1.x86_64 | freedesktop-categories | warn | Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/fcitx.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt). Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/fcitx-configtool.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt). |
 |
fcitx-4.2.7-alt2.1.x86_64 | freedesktop-desktop | info | desktop-file-validate utility printed the following message(s): /usr/share/applications/fcitx.desktop: hint: value "System;Utility;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu |
|
fcitx-4.2.7-alt2.1.x86_64 | rpm-filesystem-conflict-file-file | warn | Files /usr/bin/createPYMB /usr/bin/mb2txt /usr/bin/txt2mb conflict with the package scim-fcitx-tools-3.1.1-alt1.1.qa1.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. |
|
fcitx-libs-4.2.7-alt2.1.x86_64 | library-pkgnames | info | package contains public library which is used in external packages: name should be lib* according to http://altlinux.org/Drafts/SharedLibs |
|
fcitx-pinyin-4.2.7-alt2.1.x86_64 | arch-dep-package-has-big-usr-share | info | 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. |