Repocop reports by acl

  packager rpm id test Status message
at apt-scripts-0.1.3-alt1.noarch missing-url info Missing Url: in a package.
at qa-robot-0.3.9-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/bad_elf_symbols /usr/bin/rpmelfneed /usr/bin/dup_elf_symbols /usr/bin/abi_drift /usr/bin/packages /usr/bin/bugs /usr/bin/rpmsodiff /usr/bin/linkage_problems /usr/bin/rpmfile /usr/bin/qa-robot /usr/bin/rpmelfsym /usr/bin/cmdcache /usr/bin/rpmsoname /usr/bin/rpmargs
at qa-robot-0.3.9-alt1.noarch missing-url info Missing Url: in a package.
boyarsh apt-conf-branch-8.2-alt1.x86_64 rpm-package-is-obsoleted warn The package is obsoleted by the package apt-conf-sisyphus-7.2-alt1.x86_64, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of apt-conf-sisyphus-7.2-alt1.x86_64 to remove Obsoletes: tag.
george bind-9.11.2.P1-alt1.x86_64 init-lsb warn /etc/rc.d/init.d/bind: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.
george cups-2.2.6-alt1.x86_64 altlinux-find-lang-mo warn Language specific files in /usr/share/locale should be marked, for example, using %find_lang. See http://www.altlinux.org/FindLangPolicy for details.
george cups-2.2.6-alt1.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.
george cups-2.2.6-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/cups
george cups-2.2.6-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/cups.desktop: hint: value item "Printing" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: HardwareSettings;Settings
/usr/share/applications/cups.desktop: hint: value item "HardwareSettings" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Settings
george cups-2.2.6-alt1.x86_64 systemd-check-socket-name experimental in cups-2.2.6-alt1.x86_64: there is a socket cups-lpd.socket but no service cups-lpd.service. Ask ildar@ why it is not right.
in cups-2.2.6-alt1.x86_64: there is a socket org.cups.cups-lpd.socket but no service org.cups.cups-lpd.service. Ask ildar@ why it is not right.
george cups-ipptool-2.2.6-alt1.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.
george lwresd-9.11.2.P1-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
george lwresd-9.11.2.P1-alt1.x86_64 init-lsb fail /etc/rc.d/init.d/lwresd: not systemd compatible: lsb init header missing and lwresd.service is not present. See http://www.altlinux.org/Services_Policy for details.
glebfm altlinux-release-icarus-20160328-alt1.noarch rpm-filesystem-conflict-file-file warn File /etc/altlinux-release conflicts with the package altlinux-release-p8-20160414-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package altlinux-release-sisyphus-20081222-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-alt-sisyphus-release-20170925-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-backup-server-release-6.0.0-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.
File /etc/altlinux-release conflicts with the package branding-altlinux-centaurus-release-7.0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-desktop-release-5.9.9-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.
File /etc/altlinux-release conflicts with the package branding-altlinux-kdesktop-release-8.0.0-alt0.6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-lite-release-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-lxdesktop-release-6.0.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-office-server-release-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-spt-release-7.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-tablet-release-6.0.0-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.
File /etc/altlinux-release conflicts with the package branding-informika-schoolmaster-release-6.0.0-alt47.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-ivk-chainmail-release-3.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-school-junior-release-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-school-lite-release-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-school-master-release-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-school-server-release-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-school-teacher-release-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-sisyphus-server-light-release-1.9.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-8.2.0-alt3.S1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
glebfm altlinux-release-p8-20160414-alt1.noarch rpm-filesystem-conflict-file-file warn File /etc/altlinux-release conflicts with the package altlinux-release-icarus-20160328-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-backup-server-release-6.0.0-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.
File /etc/altlinux-release conflicts with the package branding-altlinux-centaurus-release-7.0.5-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-desktop-release-5.9.9-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.
File /etc/altlinux-release conflicts with the package branding-altlinux-kdesktop-release-8.0.0-alt0.6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-lite-release-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-lxdesktop-release-6.0.0-alt7.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-office-server-release-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-spt-release-7.0.0-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-altlinux-tablet-release-6.0.0-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.
File /etc/altlinux-release conflicts with the package branding-informika-schoolmaster-release-6.0.0-alt47.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-ivk-chainmail-release-3.0-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-school-junior-release-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-school-lite-release-5.9.9-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-school-master-release-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-school-server-release-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-school-teacher-release-7.0.5-alt2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-sisyphus-server-light-release-1.9.3-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/altlinux-release conflicts with the package branding-xalt-kworkstation-release-8.2.0-alt3.S1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
glebfm altlinux-repos-0.8-alt1.noarch missing-url info Missing Url: in a package.
glebfm apt-repo-tools-0.6.0.20-alt1.x86_64 missing-url info Missing Url: in a package.
glebfm apt-repo-tools-debuginfo-0.6.0.20-alt1.x86_64 missing-url info Missing Url: in a package.
glebfm aptitude-0.4.5-alt9.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.
glebfm aptitude-doc-0.4.5-alt9.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.
glebfm bash4-devel-4.2.50-alt1.1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package bash-devel-3.2.57-alt3.x86_64, for example, /usr/include/bash/alias.h (38 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.
glebfm bash4-examples-4.2.50-alt1.1.noarch unsafe-tmp-usage-in-scripts info The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/share/doc/bash4-4.2.50/examples/scripts/bcsh.sh: $ grep -A5 -B5 /tmp/ /usr/share/doc/bash4-4.2.50/examples/scripts/bcsh.sh ;; esac trap ':' 2 trap exit 3 trap "tail -n $savehist $histfile>/tmp/hist$$;uniq /tmp/hist$$ > $histfile;\ rm -f /tmp/*$$;exit 0" 15 getcmd=yes mailcheck= exclaim= echoit= -- while test "$line" != "end"; do echo $n "$PS2$c" read line cmd="${cmd};$line" done echo "$cmd" > /tmp/bcsh$$ ed - /tmp/bcsh$$ << ++++ s/end/done/ s/foreach[ ]\(.*\)(/for \1 in / s/)// s/;/;do / w -- line=done ;; esac cmd="${cmd};$line" done echo "$cmd" > /tmp/bcsh$$ ;; if[\ \ ]*) while test "$line" != "fi" && test "$line" != "endif" do echo $n "$PS2$c" -- line=fi ;; esac cmd="${cmd};$line" done echo "$cmd" > /tmp/bcsh$$ case "`grep then /tmp/bcsh$$`" in "") # fix 'if foo bar' cases ed - /tmp/bcsh$$ << ++++ s/)/);then/ s/.*/;fi/ w ++++ ;; -- echo $n "$PS2$c" read line cmd="${cmd}@$line" done cmd="`echo \"$cmd\" | tr '@' ' '`" echo "$cmd" > /tmp/bcsh$$ ;; switch[\ \ ]*) while test "$line" != "endsw" do echo $n "$PS2$c" read line cmd="${cmd}@$line" done echo "$cmd" > /tmp/bcsh$$ ed - /tmp/bcsh$$ << '++++' 1,$s/@/\ /g g/switch.*(/s//case "/ s/)/" in/ 1,$s/case[ ]\(.*\):$/;;\ -- g/breaksw/s/// 1,$s/default.*/;;\ *)/ w ++++ cmd="`cat /tmp/bcsh$$`" ;; *!*) hist=yes ;; esac -- echoit=yes getcmd=no continue ;; *~e) echo "$cmd" | sed -e "s@~e@@" > /tmp/bcsh$$ $EDITOR /tmp/bcsh$$ cmd="`cat /tmp/bcsh$$`" getcmd=no continue ;; *~v) echo "$cmd" | sed -e "s@~v@@" > /tmp/bcsh$$ echo "$lastcmd" > /tmp/bcsh$$ $VISUAL /tmp/bcsh$$ cmd="`cat /tmp/bcsh$$`" getcmd=no continue ;; exec[\ \ ]*) tail -n $savehist $histfile>/tmp/hist$$ uniq /tmp/hist$$ > $histfile rm -f /tmp/*$$ echo $cmd > /tmp/cmd$$ . /tmp/cmd$$ ;; login[\ \ ]*|newgrp[\ \ ]*) tail -n $savehist $histfile>/tmp/hist$$ uniq /tmp/hist$$ > $histfile rm -f /tmp/*$$ echo $cmd > /tmp/cmd$$ . /tmp/cmd$$ ;; logout|exit|bye) if test -s "$logoutfile" then # sh $logoutfile $SHELL $logoutfile fi tail -n $savehist $histfile > /tmp/hist$$ uniq /tmp/hist$$ > $histfile rm -f /tmp/*$$ exit 0 ;; h|history) grep -n . $histfile | tail -n $history | sed -e 's@:@ @' | $PAGER continue -- continue ;; source[\ \ ]*) set - $cmd shift echo . $* > /tmp/cmd$$ . /tmp/cmd$$ run=no ;; wait) wait run=no ;; .[\ \ ]*) echo $cmd > /tmp/cmd$$ . /tmp/cmd$$ run=no ;; cd|cd[\ \ ]*) # check if it will work first, or else this shell will terminate # if the cd dies. If you have a built-in test, you might want # to replace the try-it-and-see below with a couple of tests, # but it is probably just as fast like this. echo $cmd > /tmp/cmd$$ if ($SHELL /tmp/cmd$$) ; then . /tmp/cmd$$ fi run=no ;; awk[\ \ ]*|dd[\ \ ]*|cc[\ \ ]*|make[\ \ ]*) # these are the only commands I can think of whose syntax # includes an equals sign. Add others as you find them. echo "$cmd" > /tmp/bcsh$$ ;; setenv*|*=*) # handle setting shell variables, turning cshell syntax to Bourne # syntax -- note all variables must be exported or they will not # be usable in other commands echo "$cmd" > /tmp/cmd$$ ed - /tmp/cmd$$ << ++++ g/^setenv[ ]/s/[ ]/@/ g/^setenv@/s/[ ]/=/ g/^setenv@/s/// g/^set/s/// .t. \$s/=.*// s/^/export / w ++++ . /tmp/cmd$$ rm -f /tmp/cmd$$ run=no ;; unset[\ \ ]*|umask[\ \ ]*|export[\ \ ]*|set[\ \ ]*) # handle commands which twiddle current environment -- continue ;; esac ;; *) echo "$cmd" > /tmp/bcsh$$ ;; esac ;; no) echo "$cmd" > /tmp/bcsh$$ ;; esac ;; esac -- ;; *) case "$exclaim" in yes) cmd="`echo \"$cmd\" | sed -e 's@REALEXCLAMATIONMARK@!@g'`" echo "$cmd" > /tmp/bcsh$$ ;; esac case "$echoit" in yes) echo $cmd -- yes) case "${noclobber+yes}" in yes) case "$cmd" in *\>![\ \ ]*) ed - /tmp/bcsh$$ << ++++ g/>!/s//>/ w ++++ ;; *\>\>*) -- read answer case "$answer" in y*) ;; *) echo ':' > /tmp/bcsh$$ ;; esac ;; *) echo "${outfile}: file exists" echo ':' > /tmp/bcsh$$ ;; esac fi ;; esac -- esac ;; *) case "$cmd" in *\>![\ \ ]*) ed - /tmp/bcsh$$ << ++++ g/>!/s//>/g w ++++ ;; esac ;; esac (trap 'exit 1' 2 3; $BASH /tmp/bcsh$$) ;; esac case "$cmd" in $lastcmd) ;;
glebfm blender-2.78c-alt1.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.
glebfm bpython-0.14.1-alt1.1.1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/bpython.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).
glebfm bpython-0.14.1-alt1.1.1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/bpython.desktop: hint: value "Development;Utility;ConsoleOnly;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
glebfm bpython-0.14.1-alt1.1.1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.
glebfm celestia-common-1.6.1-alt5.x86_64 altlinux-find-lang-mo warn Language specific files in /usr/share/locale should be marked, for example, using %find_lang. See http://www.altlinux.org/FindLangPolicy for details.
glebfm celestia-common-1.6.1-alt5.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.
glebfm celestia-common-1.6.1-alt5.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/celestia.desktop: hint: value "Qt;KDE;Education;Science;Astronomy;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
glebfm fakechroot-2.19-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/fakechroot
glebfm fb2edit-0.0.9-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/fb2edit.desktop: hint: value "Office;FileTools;Qt;Viewer;TextTools;TextEditor;Utility;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
glebfm filezilla-3.30.0-alt1.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.
glebfm gcc4.9-doc-4.9.2-alt5.noarch rpm-obsolete-live-package info The package obsoletes the package gcc3.4-doc-3.4.5-alt17.noarch, but the package gcc3.4-doc-3.4.5-alt17.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.3-doc-4.3.2-alt20.noarch, but the package gcc4.3-doc-4.3.2-alt20.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.4-doc-4.4.7-alt4.noarch, but the package gcc4.4-doc-4.4.7-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.5-doc-4.5.4-alt4.noarch, but the package gcc4.5-doc-4.5.4-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.6-doc-4.6.3-alt11.noarch, but the package gcc4.6-doc-4.6.3-alt11.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.7-doc-4.7.2-alt10.noarch, but the package gcc4.7-doc-4.7.2-alt10.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.8-doc-4.8.2-alt5.noarch, but the package gcc4.8-doc-4.8.2-alt5.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
glebfm gcc4.9-doc-4.9.2-alt5.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package gcc5-doc-5.3.1-alt4.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc5-doc-5.3.1-alt4.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc6-doc-6.3.1-alt2.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc6-doc-6.3.1-alt2.noarch to remove Obsoletes: tag.
glebfm gcc5-doc-5.3.1-alt4.noarch rpm-obsolete-live-package info The package obsoletes the package gcc3.4-doc-3.4.5-alt17.noarch, but the package gcc3.4-doc-3.4.5-alt17.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.3-doc-4.3.2-alt20.noarch, but the package gcc4.3-doc-4.3.2-alt20.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.4-doc-4.4.7-alt4.noarch, but the package gcc4.4-doc-4.4.7-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.5-doc-4.5.4-alt4.noarch, but the package gcc4.5-doc-4.5.4-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.6-doc-4.6.3-alt11.noarch, but the package gcc4.6-doc-4.6.3-alt11.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.7-doc-4.7.2-alt10.noarch, but the package gcc4.7-doc-4.7.2-alt10.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.8-doc-4.8.2-alt5.noarch, but the package gcc4.8-doc-4.8.2-alt5.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.9-doc-4.9.2-alt5.noarch, but the package gcc4.9-doc-4.9.2-alt5.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
glebfm gcc5-doc-5.3.1-alt4.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package gcc6-doc-6.3.1-alt2.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc6-doc-6.3.1-alt2.noarch to remove Obsoletes: tag.
glebfm gcc5-gdb-plugin-5.3.1-alt4.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/libcc1.so.0.0.0 conflicts with the package gcc6-gdb-plugin-6.3.1-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.
glebfm gcc6-doc-6.3.1-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package gcc3.4-doc-3.4.5-alt17.noarch, but the package gcc3.4-doc-3.4.5-alt17.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.3-doc-4.3.2-alt20.noarch, but the package gcc4.3-doc-4.3.2-alt20.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.4-doc-4.4.7-alt4.noarch, but the package gcc4.4-doc-4.4.7-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.5-doc-4.5.4-alt4.noarch, but the package gcc4.5-doc-4.5.4-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.6-doc-4.6.3-alt11.noarch, but the package gcc4.6-doc-4.6.3-alt11.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.7-doc-4.7.2-alt10.noarch, but the package gcc4.7-doc-4.7.2-alt10.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.8-doc-4.8.2-alt5.noarch, but the package gcc4.8-doc-4.8.2-alt5.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.9-doc-4.9.2-alt5.noarch, but the package gcc4.9-doc-4.9.2-alt5.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc5-doc-5.3.1-alt4.noarch, but the package gcc5-doc-5.3.1-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
glebfm gcc6-gdb-plugin-6.3.1-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/libcc1.so.0.0.0 conflicts with the package gcc5-gdb-plugin-5.3.1-alt4.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.
glebfm jimtcl-0.76-alt1.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
glebfm kavlon-0.13-alt2.noarch missing-url info Missing Url: in a package.
glebfm kernel-source-4.10-1.0.0-alt1.noarch missing-url info Missing Url: in a package.
glebfm libabigail-1.0-alt0.2.rc2.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.
glebfm libedit-devel-3.1.20141030-alt1.x86_64 library-pkgnames-static warn package contains static library which has the same name as a shared library in the repository, but neither package name ends with -devel-static according to http://altlinux.org/Drafts/SharedLibs nor the package explicitly conflicts with the package with .so library
glebfm libgcj4.9-4.9.2-alt5.x86_64 file-in-usr-marked-as-conffile warn Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
glebfm libgcj5-5.3.1-alt4.x86_64 file-in-usr-marked-as-conffile warn Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
glebfm libgcj6-6.3.1-alt2.x86_64 file-in-usr-marked-as-conffile warn Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
glebfm libploop-1.15-alt2.x86_64 subdir-in-var-run info 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.
glebfm libreadline5-devel-5.2.14-alt5.1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package libreadline-devel-6.3.8-alt2.x86_64, for example, /usr/include/readline/chardefs.h (13 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.
glebfm libreadline5-devel-5.2.14-alt5.1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libhistory.so is different from the same symlink in the package libreadline-devel-6.3.8-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.
glebfm libreadline5-devel-static-5.2.14-alt5.1.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/lib64/libhistory.a /usr/lib64/libreadline.a conflict with the package libreadline-devel-static-6.3.8-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.
glebfm libstdc++4.9-devel-4.9.2-alt5.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.
glebfm libstdc++5-devel-5.3.1-alt4.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.
glebfm libstdc++6-devel-6.3.1-alt2.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.
glebfm lyx-2.2.3-alt1.src altlinux-policy-tex-rpm-build-texmf warn According to TeX policy (http://www.altlinux.org/TeXPolicy) packages that install files to /usr/share/texmf should BuildRequires(pre): rpm-build-texmf for the dependency magic to work.
glebfm lyx-2.2.3-alt1.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.
glebfm lyx-2.2.3-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/lyxcat
glebfm mutt-1.8.3-alt1.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.
glebfm nitrokey-app-0.6.3-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/nitrokey-app.desktop: hint: value item "Security" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Settings, or System
glebfm python-module-gccjit-0.4.0.5.g541d3a6-alt1.x86_64 missing-url info Missing Url: in a package.
glebfm python-module-gccjit-debuginfo-0.4.0.5.g541d3a6-alt1.x86_64 missing-url info Missing Url: in a package.
glebfm rpm-build-4.0.4-alt108.x86_64 file-in-usr-marked-as-conffile warn Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
glebfm rpm-plugin-hdrcache-4.13.0.1-alt1.x86_64 rpm-obsolete-live-package info The package obsoletes the package rpmhdrmemcache-0.1.2-alt3.1.x86_64, but the package rpmhdrmemcache-0.1.2-alt3.1.x86_64 is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
glebfm rpmrebuild-pesign-0.2.1-alt1.noarch missing-url info Missing Url: in a package.
glebfm squid-3.5.26-alt3.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/squid
glebfm squid-3.5.26-alt3.x86_64 init-lsb warn /etc/rc.d/init.d/squid: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.
glebfm squid-3.5.26-alt3.x86_64 subdir-in-var-run info 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.
glebfm squid-doc-3.5.26-alt3.noarch big-changelog info Package contains big ChangeLog. Gzip it.
glebfm vim-X11-8.0.711-alt1.1.1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/gvim.desktop: warning: value "Text Editor" for key "Comment" in group "Desktop Entry" looks redundant with value "Text Editor" of key "GenericName"
/usr/share/applications/gvim.desktop: warning: value "???? ????" for key "Comment[ar]" in group "Desktop Entry" looks redundant with value "???? ????" of key "GenericName[ar]"
/usr/share/applications/gvim.desktop: warning: value "Texteditor" for key "Comment[de]" in group "Desktop Entry" looks redundant with value "Texteditor" of key "GenericName[de]"
/usr/share/applications/gvim.desktop: warning: value "Tekstredaktilo" for key "Comment[eo]" in group "Desktop Entry" looks redundant with value "Tekstredaktilo" of key "GenericName[eo]"
/usr/share/applications/gvim.desktop: warning: value "Tekstiredaktor" for key "Comment[et]" in group "Desktop Entry" looks redundant with value "Tekstiredaktor" of key "GenericName[et]"
/usr/share/applications/gvim.desktop: warning: value "Testu Editorea" for key "Comment[eu]" in group "Desktop Entry" looks redundant with value "Testu editorea" of key "GenericName[eu]"
/usr/share/applications/gvim.desktop: warning: value "Tekstieditori" for key "Comment[fi]" in group "Desktop Entry" looks redundant with value "Tekstieditori" of key "GenericName[fi]"
/usr/share/applications/gvim.desktop: warning: value "???? ????" for key "Comment[he]" in group "Desktop Entry" looks redundant with value "???? ????" of key "GenericName[he]"
/usr/share/applications/gvim.desktop: warning: value "Textaritill" for key "Comment[is]" in group "Desktop Entry" looks redundant with value "Textaritill" of key "GenericName[is]"
/usr/share/applications/gvim.desktop: warning: value "????????" for key "Comment[ja]" in group "Desktop Entry" looks redundant with value "????????" of key "GenericName[ja]"
/usr/share/applications/gvim.desktop: warning: value "Teksto redaktorius" for key "Comment[lt]" in group "Desktop Entry" looks redundant with value "Teksto redaktorius" of key "GenericName[lt]"
/usr/share/applications/gvim.desktop: warning: value "Editur tat-test" for key "Comment[mt]" in group "Desktop Entry" looks redundant with value "Editur tat-test" of key "GenericName[mt]"
/usr/share/applications/gvim.desktop: warning: value "Editor de Texto" for key "Comment[pt_BR]" in group "Desktop Entry" looks redundant with value "Editor de Texto" of key "GenericName[pt_BR]"
/usr/share/applications/gvim.desktop: warning: value "Editor de text" for key "Comment[ro]" in group "Desktop Entry" looks redundant with value "Editor de text" of key "GenericName[ro]"
/usr/share/applications/gvim.desktop: warning: value "Textov? editor" for key "Comment[sk]" in group "Desktop Entry" looks redundant with value "Textov? editor" of key "GenericName[sk]"
/usr/share/applications/gvim.desktop: warning: value "Urejevalnik besedil" for key "Comment[sl]" in group "Desktop Entry" looks redundant with value "Urejevalnik besedil" of key "GenericName[sl]"
/usr/share/applications/gvim.desktop: warning: value "Metin D?zenleyici" for key "Comment[tr]" in group "Desktop Entry" looks redundant with value "Metin D?zenleyici" of key "GenericName[tr]"
/usr/share/applications/gvim.desktop: warning: value "???????? ???????" for key "Comment[uk]" in group "Desktop Entry" looks redundant with value "???????? ???????" of key "GenericName[uk]"
/usr/share/applications/gvim.desktop: warning: value "Tr?nh so?n v?n b?n" for key "Comment[vi]" in group "Desktop Entry" looks redundant with value "Tr?nh so?n v?n b?n" of key "GenericName[vi]"
/usr/share/applications/gvim.desktop: warning: value "?????" for key "Comment[zh_CN]" in group "Desktop Entry" looks redundant with value "?????" of key "GenericName[zh_CN]"
/usr/share/applications/gvim.desktop: warning: value "?????" for key "Comment[zh_TW]" in group "Desktop Entry" looks redundant with value "?????" of key "GenericName[zh_TW]"
/usr/share/applications/gvim.desktop: warning: value "application/mathml+xml;application/xhtml+xml;application/x-perl;application/x-python;application/x-shellscript;audio/x-mpegurl;audio/x-scpls;image/svg+xml;message/news;message/rfc822;text/calendar;text/css;text/english;text/html;text/mrml;text/plain;text/rdf;text/rss;text/rtf;text/sgml;text/vnd.wap.wml;text/x-adasrc;text/x-bibtex;text/x-chdr;text/x-c++hdr;text/x-csrc;text/x-c++src;text/x-csv;text/x-diff;text/x-java;text/x-katefilelist;text/x-latex;text/x-log;text/x-lyx;text/x-makefile;text/xmcd;text/xml;text/x-moc;text/x-mswinurl;text/x-objcsrc;text/x-pascal;text/x-perl;text/x-python;text/x-tcl;text/x-tex;text/x-vcalendar;text/x-vcard;text/x-xslfo;text/x-xslt;" for key "MimeType" in group "Desktop Entry" contains value "message/news" which is a MIME type that should probably not be used: "message" is a media type that probably does not make sense in this context
glebfm vzctl-4.9.4-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/sbin/vzmigrate
glebfm vzctl-4.9.4-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files.
glebfm vzctl-4.9.4-alt1.x86_64 udev-files-in-etc warn Systemd files Policy Draft violation: etc/udev/rules.d/ is reserved for sysadmin. Please, move /etc/udev/rules.d/60-vzctl.rules to \%_udevrulesdir/.
lakostis clang-3.8.0-alt1.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
lakostis clang-analyzer-3.8.0-alt1.1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/share/man/man1/scan-build.1.xz conflicts with the package clang4.0-analyzer-4.0.1-alt1.2.rel.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
lakostis clang-analyzer-3.8.0-alt1.1.x86_64 rpm-filesystem-conflict-symlink-file warn symlink /usr/bin/scan-build is a file in the package clang4.0-analyzer-4.0.1-alt1.2.rel.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
symlink /usr/bin/scan-view is a file in the package clang4.0-analyzer-4.0.1-alt1.2.rel.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
lakostis clang-debuginfo-3.8.0-alt1.1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/bin/clang++.debug is different from the same symlink in the package clang4.0-debuginfo-4.0.1-alt1.2.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.
lakostis clang-devel-3.8.0-alt1.1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package clang4.0-devel-4.0.1-alt1.2.rel.x86_64, for example, /usr/include/clang-c/Index.h (269 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.
lakostis clang-devel-static-3.8.0-alt1.1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package clang4.0-devel-static-4.0.1-alt1.2.rel.x86_64, for example, /usr/lib64/libclangARCMigrate.a (24 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.
lakostis llvm-devel-3.8.0-alt1.1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package llvm4.0-devel-4.0.1-alt1.2.rel.x86_64, for example, /usr/bin/llvm-config (598 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.
lakostis llvm-devel-static-3.8.0-alt1.1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package llvm4.0-devel-static-4.0.1-alt1.2.rel.x86_64, for example, /usr/lib64/libLLVMAMDGPUAsmParser.a (53 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.
ldv alt-gpgkeys-0.7.132-alt1.noarch missing-url info Missing Url: in a package.
ldv alt-gpgkeys-utils-0.7.132-alt1.noarch missing-url info Missing Url: in a package.
ldv apt-conf-sisyphus-7.2-alt1.x86_64 rpm-obsolete-live-package info The package obsoletes the package apt-conf-branch-8.2-alt1.x86_64, but the package apt-conf-branch-8.2-alt1.x86_64 is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
ldv bash-devel-3.2.57-alt3.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package bash4-devel-4.2.50-alt1.1.x86_64, for example, /usr/include/bash/alias.h (38 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.
ldv bash-examples-3.2.57-alt3.noarch unsafe-tmp-usage-in-scripts info The test discovered scripts with errors which may be used by a user for damaging important system files. For example if a script uses in its work a temp file which is created in /tmp directory, then every user can create symlinks with the same name (pattern) in this directory in order to destroy or rewrite some system or another user's files. Scripts _must_ _use_ mktemp/tempfile or must use $TMPDIR. mktemp/tempfile is safest. $TMPDIR is safer than /tmp/ because libpam-tmpdir creates a subdirectory of /tmp that is only accessible by that user, and then sets TMPDIR and other variables to that. Hence, it doesn't matter nearly as much if you create a non-random filename, because nobody but you can access it. Found error in /usr/share/doc/bash-3.2.57/examples/misc/cshtobash: $ grep -A5 -B5 /tmp/ /usr/share/doc/bash-3.2.57/examples/misc/cshtobash # zsh-3.0. # # Chet Ramey # chet@po.cwru.edu # trap 'rm -f /tmp/cb$$.? cshout cshin' 0 1 2 3 6 15 T=$'\t' SOURCE="${1:+source $1}" cat << EOF >cshin $SOURCE alias >! /tmp/cb$$.a setenv >! /tmp/cb$$.e set >! /tmp/cb$$.v EOF # give csh a minimal environment, similar to what login would provide /usr/bin/env - USER=$USER HOME=$HOME PATH=/usr/bin:/bin:/usr/ucb:. TERM=$TERM SHELL=$SHELL /bin/csh -i < ./cshin > cshout 2>&1 # First convert aliases cat << \EOF >/tmp/cb$$.1 mkalias () { case $2 in '') echo alias ${1}="''" ;; *[#\!]*) -- *) echo alias ${1}=\'$(echo "${2}" | sed "s:':'\\\\'':")\' ;; esac } EOF sed "s/^\([a-zA-Z0-9_]*\)$T\(.*\)$/mkalias \1 '\2'/" < /tmp/cb$$.a >>/tmp/cb$$.1 echo '# csh aliases' echo $BASH /tmp/cb$$.1 | sed -e 's/\$cwd/\$PWD/g' \ -e 's/\$term/\$TERM/g' \ -e 's/\$home/\$HOME/g' \ -e 's/\$user/\$USER/g' \ -e 's/\$prompt/\$PS1/g' -- # Would be nice to deal with embedded newlines, e.g. in TERMCAP, but ... sed -e '/^SHLVL/d' \ -e '/^PWD/d' \ -e "s/'/'"\\\\"''"/g \ -e "s/^\([A-Za-z0-9_]*=\)/export \1'/" \ -e "s/$/'/" < /tmp/cb$$.e # Finally, convert local variables echo echo '# csh variables' echo -- sed -e 's/'"$T"'/=/' \ -e "s/'/'"\\\\"''"/g \ -e '/^[A-Za-z0-9_]*=[^(]/{ s/=/='"'/"' s/$/'"'/"' }' < /tmp/cb$$.v | sed -e '/^argv=/d' -e '/^cwd=/d' -e '/^filec=/d' -e '/^status=/d' \ -e '/^verbose=/d' \ -e '/^term=/d' \ -e '/^home=/d' \ -e '/^path=/d' \ -- # now some special csh variables converted to bash equivalents echo echo '# special csh variables converted to bash equivalents' echo sed -e 's/'"$T"'/=/' < /tmp/cb$$.v | grep "^cdpath=" | sed 's/(// s/ /:/g s/)// s/cdpath=/CDPATH=/' sed -e 's/'"$T"'/=/' < /tmp/cb$$.v | grep "^mail=" | sed 's/(// s/ /:/g s/)// s/mail=/MAILPATH=/' | Found error in /usr/share/doc/bash-3.2.57/examples/misc/aliasconv.sh: $ grep -A5 -B5 /tmp/ /usr/share/doc/bash-3.2.57/examples/misc/aliasconv.sh # usage: aliasconv.sh # # Chet Ramey # chet@po.cwru.edu # trap 'rm -f /tmp/cb$$.?' 0 1 2 3 6 15 T=' ' cat << \EOF >/tmp/cb$$.1 mkalias () { case $2 in '') echo alias ${1}="''" ;; *[#\!]*) -- # the first thing we want to do is to protect single quotes in the alias, # since they whole thing is going to be surrounded by single quotes when # passed to mkalias sed -e "s:':\\'\\\'\\':" -e "s/^\([a-zA-Z0-9_-]*\)$T\(.*\)$/mkalias \1 '\2'/" >>/tmp/cb$$.1 sh /tmp/cb$$.1 | sed -e 's/\$cwd/\$PWD/g' \ -e 's/\$term/\$TERM/g' \ -e 's/\$home/\$HOME/g' \ -e 's/\$user/\$USER/g' \ -e 's/\$prompt/\$PS1/g' Found error in /usr/share/doc/bash-3.2.57/examples/misc/aliasconv.bash: $ grep -A5 -B5 /tmp/ /usr/share/doc/bash-3.2.57/examples/misc/aliasconv.bash # usage: aliasconv.bash # # Chet Ramey # chet@po.cwru.edu # trap 'rm -f /tmp/cb$$.?' 0 1 2 3 6 15 T=$'\t' cat << \EOF >/tmp/cb$$.1 mkalias () { case $2 in '') echo alias ${1}="''" ;; *[#\!]*) -- # the first thing we want to do is to protect single quotes in the alias, # since they whole thing is going to be surrounded by single quotes when # passed to mkalias sed -e "s:':\\'\\\'\\':" -e "s/^\([a-zA-Z0-9_-]*\)$T\(.*\)$/mkalias \1 '\2'/" >>/tmp/cb$$.1 $BASH /tmp/cb$$.1 | sed -e 's/\$cwd/\$PWD/g' \ -e 's/\$term/\$TERM/g' \ -e 's/\$home/\$HOME/g' \ -e 's/\$user/\$USER/g' \ -e 's/\$prompt/\$PS1/g' Found error in /usr/share/doc/bash-3.2.57/examples/scripts/bcsh.sh: $ grep -A5 -B5 /tmp/ /usr/share/doc/bash-3.2.57/examples/scripts/bcsh.sh ;; esac trap ':' 2 trap exit 3 trap "tail -n $savehist $histfile>/tmp/hist$$;uniq /tmp/hist$$ > $histfile;\ rm -f /tmp/*$$;exit 0" 15 getcmd=yes mailcheck= exclaim= echoit= -- while test "$line" != "end"; do echo $n "$PS2$c" read line cmd="${cmd};$line" done echo "$cmd" > /tmp/bcsh$$ ed - /tmp/bcsh$$ << ++++ s/end/done/ s/foreach[ ]\(.*\)(/for \1 in / s/)// s/;/;do / w -- line=done ;; esac cmd="${cmd};$line" done echo "$cmd" > /tmp/bcsh$$ ;; if[\ \ ]*) while test "$line" != "fi" && test "$line" != "endif" do echo $n "$PS2$c" -- line=fi ;; esac cmd="${cmd};$line" done echo "$cmd" > /tmp/bcsh$$ case "`grep then /tmp/bcsh$$`" in "") # fix 'if foo bar' cases ed - /tmp/bcsh$$ << ++++ s/)/);then/ s/.*/;fi/ w ++++ ;; -- echo $n "$PS2$c" read line cmd="${cmd}@$line" done cmd="`echo \"$cmd\" | tr '@' ' '`" echo "$cmd" > /tmp/bcsh$$ ;; switch[\ \ ]*) while test "$line" != "endsw" do echo $n "$PS2$c" read line cmd="${cmd}@$line" done echo "$cmd" > /tmp/bcsh$$ ed - /tmp/bcsh$$ << '++++' 1,$s/@/\ /g g/switch.*(/s//case "/ s/)/" in/ 1,$s/case[ ]\(.*\):$/;;\ -- g/breaksw/s/// 1,$s/default.*/;;\ *)/ w ++++ cmd="`cat /tmp/bcsh$$`" ;; *!*) hist=yes ;; esac -- echoit=yes getcmd=no continue ;; *~e) echo "$cmd" | sed -e "s@~e@@" > /tmp/bcsh$$ $EDITOR /tmp/bcsh$$ cmd="`cat /tmp/bcsh$$`" getcmd=no continue ;; *~v) echo "$cmd" | sed -e "s@~v@@" > /tmp/bcsh$$ echo "$lastcmd" > /tmp/bcsh$$ $VISUAL /tmp/bcsh$$ cmd="`cat /tmp/bcsh$$`" getcmd=no continue ;; exec[\ \ ]*) tail -n $savehist $histfile>/tmp/hist$$ uniq /tmp/hist$$ > $histfile rm -f /tmp/*$$ echo $cmd > /tmp/cmd$$ . /tmp/cmd$$ ;; login[\ \ ]*|newgrp[\ \ ]*) tail -n $savehist $histfile>/tmp/hist$$ uniq /tmp/hist$$ > $histfile rm -f /tmp/*$$ echo $cmd > /tmp/cmd$$ . /tmp/cmd$$ ;; logout|exit|bye) if test -s "$logoutfile" then # sh $logoutfile $SHELL $logoutfile fi tail -n $savehist $histfile > /tmp/hist$$ uniq /tmp/hist$$ > $histfile rm -f /tmp/*$$ exit 0 ;; h|history) grep -n . $histfile | tail -n $history | sed -e 's@:@ @' | $PAGER continue -- continue ;; source[\ \ ]*) set - $cmd shift echo . $* > /tmp/cmd$$ . /tmp/cmd$$ run=no ;; wait) wait run=no ;; .[\ \ ]*) echo $cmd > /tmp/cmd$$ . /tmp/cmd$$ run=no ;; cd|cd[\ \ ]*) # check if it will work first, or else this shell will terminate # if the cd dies. If you have a built-in test, you might want # to replace the try-it-and-see below with a couple of tests, # but it is probably just as fast like this. echo $cmd > /tmp/cmd$$ if ($SHELL /tmp/cmd$$) ; then . /tmp/cmd$$ fi run=no ;; awk[\ \ ]*|dd[\ \ ]*|cc[\ \ ]*|make[\ \ ]*) # these are the only commands I can think of whose syntax # includes an equals sign. Add others as you find them. echo "$cmd" > /tmp/bcsh$$ ;; setenv*|*=*) # handle setting shell variables, turning cshell syntax to Bourne # syntax -- note all variables must be exported or they will not # be usable in other commands echo "$cmd" > /tmp/cmd$$ ed - /tmp/cmd$$ << ++++ g/^setenv[ ]/s/[ ]/@/ g/^setenv@/s/[ ]/=/ g/^setenv@/s/// g/^set/s/// .t. \$s/=.*// s/^/export / w ++++ . /tmp/cmd$$ rm -f /tmp/cmd$$ run=no ;; unset[\ \ ]*|umask[\ \ ]*|export[\ \ ]*|set[\ \ ]*) # handle commands which twiddle current environment -- continue ;; esac ;; *) echo "$cmd" > /tmp/bcsh$$ ;; esac ;; no) echo "$cmd" > /tmp/bcsh$$ ;; esac ;; esac -- ;; *) case "$exclaim" in yes) cmd="`echo \"$cmd\" | sed -e 's@REALEXCLAMATIONMARK@!@g'`" echo "$cmd" > /tmp/bcsh$$ ;; esac case "$echoit" in yes) echo $cmd -- yes) case "${noclobber+yes}" in yes) case "$cmd" in *\>![\ \ ]*) ed - /tmp/bcsh$$ << ++++ g/>!/s//>/ w ++++ ;; *\>\>*) -- read answer case "$answer" in y*) ;; *) echo ':' > /tmp/bcsh$$ ;; esac ;; *) echo "${outfile}: file exists" echo ':' > /tmp/bcsh$$ ;; esac fi ;; esac -- esac ;; *) case "$cmd" in *\>![\ \ ]*) ed - /tmp/bcsh$$ << ++++ g/>!/s//>/g w ++++ ;; esac ;; esac (trap 'exit 1' 2 3; $BASH /tmp/bcsh$$) ;; esac case "$cmd" in $lastcmd) ;;
ldv binutils-2.27.0-alt1.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.
ldv binutils-devel-2.27.0-alt1.x86_64 library-pkgnames-static warn package contains static library which has the same name as a shared library in the repository, but neither package name ends with -devel-static according to http://altlinux.org/Drafts/SharedLibs nor the package explicitly conflicts with the package with .so library
ldv bootloader-utils-0.4.25-alt1.noarch missing-url info Missing Url: in a package.
ldv filesystem-2.3.16-alt1.x86_64 missing-url info Missing Url: in a package.
ldv filesystem-2.3.16-alt1.x86_64 subdir-in-var-run info 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.
ldv gcc-c++-common-1.4.20-alt1.noarch missing-url info Missing Url: in a package.
ldv gcc-common-1.4.20-alt1.x86_64 missing-url info Missing Url: in a package.
ldv gcc-common-debuginfo-1.4.20-alt1.x86_64 missing-url info Missing Url: in a package.
ldv gcc-fortran-common-1.4.20-alt1.noarch missing-url info Missing Url: in a package.
ldv gcc-gnat-common-1.4.20-alt1.noarch missing-url info Missing Url: in a package.
ldv gcc-go-common-1.4.20-alt1.noarch missing-url info Missing Url: in a package.
ldv gcc-java-common-1.4.20-alt1.noarch missing-url info Missing Url: in a package.
ldv gcc-treelang-common-1.4.20-alt1.noarch missing-url info Missing Url: in a package.
ldv gcc3.4-3.4.5-alt17.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.
ldv gcc3.4-doc-3.4.5-alt17.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package gcc4.3-doc-4.3.2-alt20.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.3-doc-4.3.2-alt20.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.4-doc-4.4.7-alt4.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.4-doc-4.4.7-alt4.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.5-doc-4.5.4-alt4.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.5-doc-4.5.4-alt4.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.6-doc-4.6.3-alt11.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.6-doc-4.6.3-alt11.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.7-doc-4.7.2-alt10.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.7-doc-4.7.2-alt10.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.8-doc-4.8.2-alt5.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.8-doc-4.8.2-alt5.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.9-doc-4.9.2-alt5.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.9-doc-4.9.2-alt5.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc5-doc-5.3.1-alt4.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc5-doc-5.3.1-alt4.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc6-doc-6.3.1-alt2.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc6-doc-6.3.1-alt2.noarch to remove Obsoletes: tag.
ldv gcc4.3-doc-4.3.2-alt20.noarch rpm-obsolete-live-package info The package obsoletes the package gcc3.4-doc-3.4.5-alt17.noarch, but the package gcc3.4-doc-3.4.5-alt17.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
ldv gcc4.3-doc-4.3.2-alt20.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package gcc4.4-doc-4.4.7-alt4.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.4-doc-4.4.7-alt4.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.5-doc-4.5.4-alt4.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.5-doc-4.5.4-alt4.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.6-doc-4.6.3-alt11.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.6-doc-4.6.3-alt11.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.7-doc-4.7.2-alt10.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.7-doc-4.7.2-alt10.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.8-doc-4.8.2-alt5.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.8-doc-4.8.2-alt5.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.9-doc-4.9.2-alt5.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.9-doc-4.9.2-alt5.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc5-doc-5.3.1-alt4.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc5-doc-5.3.1-alt4.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc6-doc-6.3.1-alt2.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc6-doc-6.3.1-alt2.noarch to remove Obsoletes: tag.
ldv gcc4.4-doc-4.4.7-alt4.noarch rpm-obsolete-live-package info The package obsoletes the package gcc3.4-doc-3.4.5-alt17.noarch, but the package gcc3.4-doc-3.4.5-alt17.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.3-doc-4.3.2-alt20.noarch, but the package gcc4.3-doc-4.3.2-alt20.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
ldv gcc4.4-doc-4.4.7-alt4.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package gcc4.5-doc-4.5.4-alt4.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.5-doc-4.5.4-alt4.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.6-doc-4.6.3-alt11.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.6-doc-4.6.3-alt11.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.7-doc-4.7.2-alt10.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.7-doc-4.7.2-alt10.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.8-doc-4.8.2-alt5.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.8-doc-4.8.2-alt5.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.9-doc-4.9.2-alt5.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.9-doc-4.9.2-alt5.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc5-doc-5.3.1-alt4.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc5-doc-5.3.1-alt4.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc6-doc-6.3.1-alt2.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc6-doc-6.3.1-alt2.noarch to remove Obsoletes: tag.
ldv gcc4.5-doc-4.5.4-alt4.noarch rpm-obsolete-live-package info The package obsoletes the package gcc3.4-doc-3.4.5-alt17.noarch, but the package gcc3.4-doc-3.4.5-alt17.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.3-doc-4.3.2-alt20.noarch, but the package gcc4.3-doc-4.3.2-alt20.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.4-doc-4.4.7-alt4.noarch, but the package gcc4.4-doc-4.4.7-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
ldv gcc4.5-doc-4.5.4-alt4.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package gcc4.6-doc-4.6.3-alt11.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.6-doc-4.6.3-alt11.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.7-doc-4.7.2-alt10.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.7-doc-4.7.2-alt10.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.8-doc-4.8.2-alt5.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.8-doc-4.8.2-alt5.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.9-doc-4.9.2-alt5.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.9-doc-4.9.2-alt5.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc5-doc-5.3.1-alt4.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc5-doc-5.3.1-alt4.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc6-doc-6.3.1-alt2.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc6-doc-6.3.1-alt2.noarch to remove Obsoletes: tag.
ldv gcc4.8-doc-4.8.2-alt5.noarch rpm-obsolete-live-package info The package obsoletes the package gcc3.4-doc-3.4.5-alt17.noarch, but the package gcc3.4-doc-3.4.5-alt17.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.3-doc-4.3.2-alt20.noarch, but the package gcc4.3-doc-4.3.2-alt20.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.4-doc-4.4.7-alt4.noarch, but the package gcc4.4-doc-4.4.7-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.5-doc-4.5.4-alt4.noarch, but the package gcc4.5-doc-4.5.4-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.6-doc-4.6.3-alt11.noarch, but the package gcc4.6-doc-4.6.3-alt11.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.7-doc-4.7.2-alt10.noarch, but the package gcc4.7-doc-4.7.2-alt10.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
ldv gcc4.8-doc-4.8.2-alt5.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package gcc4.9-doc-4.9.2-alt5.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.9-doc-4.9.2-alt5.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc5-doc-5.3.1-alt4.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc5-doc-5.3.1-alt4.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc6-doc-6.3.1-alt2.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc6-doc-6.3.1-alt2.noarch to remove Obsoletes: tag.
ldv glibc-devel-2.27-alt1.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/include/rpcsvc/rquota.h /usr/include/rpcsvc/rquota.x conflict with the package quota-devel-4.03.0.39.251c-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
ldv glibc-gconv-modules-2.27-alt1.x86_64 file-in-usr-marked-as-conffile warn Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
ldv jdkgcj-0.5.14-alt1.x86_64 altlinux-java-forbidden-requires fail The package has JVM-specific Requires: java-1.5.0-gcj-aot-compile. Those requires are often due to packaging errors and also specifically forbidden by Java Packageing Policy. If you really really need it, write it in more indirect way.
ldv libgcj-common-1.4.20-alt1.x86_64 missing-url info Missing Url: in a package.
ldv libgcj4.5-4.5.4-alt4.x86_64 file-in-usr-marked-as-conffile warn Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
ldv libgcj4.8-4.8.2-alt5.x86_64 file-in-usr-marked-as-conffile warn Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
ldv libreadline-devel-6.3.8-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package libreadline5-devel-5.2.14-alt5.1.x86_64, for example, /usr/include/readline/chardefs.h (13 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.
ldv libreadline-devel-6.3.8-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libhistory.so is different from the same symlink in the package libreadline5-devel-5.2.14-alt5.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.
ldv libreadline-devel-static-6.3.8-alt2.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/lib64/libhistory.a /usr/lib64/libreadline.a conflict with the package libreadline5-devel-static-5.2.14-alt5.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.
ldv libssl-devel-static-1.0.2n-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/libssl.a conflicts with the package libnss-devel-static-3.34.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.
ldv libstdc++4.3-devel-4.3.2-alt20.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.
ldv libstdc++4.4-devel-4.4.7-alt4.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.
ldv libstdc++4.5-devel-4.5.4-alt4.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.
ldv libstdc++4.8-devel-4.8.2-alt5.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.
ldv nscd-2.27-alt1.x86_64 init-lsb warn /etc/rc.d/init.d/nscd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.
ldv nscd-2.27-alt1.x86_64 subdir-in-var-run info 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.
ldv openssh-clients-7.2p2-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/rescp
ldv openssh-server-7.2p2-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/sshd
ldv openssh-server-7.2p2-alt2.x86_64 init-lsb warn /etc/rc.d/init.d/sshd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.
ldv python-modules-unittest-2.7.14-alt1.x86_64 altlinux-python-test-is-packaged info /usr/lib64/python2.7/unittest/test/test_assertions.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/unittest/test/test_assertions.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/unittest/test/test_assertions.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 other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/unittest/test/test_break.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/unittest/test/test_break.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/unittest/test/test_break.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 other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/unittest/test/test_case.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/unittest/test/test_case.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/unittest/test/test_case.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 other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/unittest/test/test_discovery.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/unittest/test/test_discovery.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/unittest/test/test_discovery.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 other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/unittest/test/test_functiontestcase.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/unittest/test/test_functiontestcase.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/unittest/test/test_functiontestcase.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 other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/unittest/test/test_loader.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/unittest/test/test_loader.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/unittest/test/test_loader.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 other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/unittest/test/test_program.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/unittest/test/test_program.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/unittest/test/test_program.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 other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/unittest/test/test_result.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/unittest/test/test_result.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/unittest/test/test_result.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 other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/unittest/test/test_runner.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/unittest/test/test_runner.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/unittest/test/test_runner.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 other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/unittest/test/test_setups.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/unittest/test/test_setups.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/unittest/test/test_setups.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 other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/unittest/test/test_skipping.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/unittest/test/test_skipping.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/unittest/test/test_skipping.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 other packages. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/unittest/test/test_suite.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/unittest/test/test_suite.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/unittest/test/test_suite.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 other packages. See http://www.altlinux.org/Python_Policy for details.
ldv python-tools-idle-2.7.14-alt1.x86_64 altlinux-policy-debian-menu-is-deprecated warn package contains deprecated /usr/lib/menu/ files. Please, convert to .desktop files
ldv python-tools-scripts-2.7.14-alt1.x86_64 altlinux-python-obsolete-buildreq-python-dev warn python-dev is obsolete according to Python Policy (http://www.altlinux.org/Python_Policy). Please, use BuildRequires: python-devel.
ldv python3-tools-3.5.4-alt2.x86_64 altlinux-python-python3-requires-python warn python3 package requires python-base.
ldv screen-4.6.1-alt1.x86_64 subdir-in-var-run info 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.
ldv screen-4.6.1-alt1.x86_64 systemd-files-in-etc warn Systemd files Policy Draft violation: etc/tmpfiles.d/ is reserved for sysadmin overrides. Please, move /etc/tmpfiles.d/screen.conf to \%_tmpfilesdir/.
ldv sisyphus_check-0.8.44-alt1.noarch missing-url info Missing Url: in a package.
sbolshakov gcc4.6-doc-4.6.3-alt11.noarch rpm-obsolete-live-package info The package obsoletes the package gcc3.4-doc-3.4.5-alt17.noarch, but the package gcc3.4-doc-3.4.5-alt17.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.3-doc-4.3.2-alt20.noarch, but the package gcc4.3-doc-4.3.2-alt20.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.4-doc-4.4.7-alt4.noarch, but the package gcc4.4-doc-4.4.7-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.5-doc-4.5.4-alt4.noarch, but the package gcc4.5-doc-4.5.4-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
sbolshakov gcc4.6-doc-4.6.3-alt11.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package gcc4.7-doc-4.7.2-alt10.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.7-doc-4.7.2-alt10.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.8-doc-4.8.2-alt5.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.8-doc-4.8.2-alt5.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.9-doc-4.9.2-alt5.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.9-doc-4.9.2-alt5.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc5-doc-5.3.1-alt4.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc5-doc-5.3.1-alt4.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc6-doc-6.3.1-alt2.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc6-doc-6.3.1-alt2.noarch to remove Obsoletes: tag.
sbolshakov gcc4.7-doc-4.7.2-alt10.noarch rpm-obsolete-live-package info The package obsoletes the package gcc3.4-doc-3.4.5-alt17.noarch, but the package gcc3.4-doc-3.4.5-alt17.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.3-doc-4.3.2-alt20.noarch, but the package gcc4.3-doc-4.3.2-alt20.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.4-doc-4.4.7-alt4.noarch, but the package gcc4.4-doc-4.4.7-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.5-doc-4.5.4-alt4.noarch, but the package gcc4.5-doc-4.5.4-alt4.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
The package obsoletes the package gcc4.6-doc-4.6.3-alt11.noarch, but the package gcc4.6-doc-4.6.3-alt11.noarch is still alive and in the repository. Ask its maintainer to remove it, or, if it should not be removed, remove the Obsoletes: tag. Do not forget to add explicit conflicts with the other package if nessessary.
sbolshakov gcc4.7-doc-4.7.2-alt10.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package gcc4.8-doc-4.8.2-alt5.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.8-doc-4.8.2-alt5.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc4.9-doc-4.9.2-alt5.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc4.9-doc-4.9.2-alt5.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc5-doc-5.3.1-alt4.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc5-doc-5.3.1-alt4.noarch to remove Obsoletes: tag.
The package is obsoleted by the package gcc6-doc-6.3.1-alt2.noarch, but is still alive and in the repository. Consider removing the package, or, if you want the package to be alive, ask the maintainer of gcc6-doc-6.3.1-alt2.noarch to remove Obsoletes: tag.
sbolshakov libgcj4.6-4.6.3-alt11.x86_64 file-in-usr-marked-as-conffile warn Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
sbolshakov libgcj4.7-4.7.2-alt10.x86_64 file-in-usr-marked-as-conffile warn Files below /usr may not be marked as conffiles, since
/usr might be mounted read-only and thus, the local system
administrator would not have a chance to modify this configuration
file.
sbolshakov libstdc++4.6-devel-4.6.3-alt11.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.
sbolshakov libstdc++4.7-devel-4.7.2-alt10.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.

generated by repocop at Tue Feb 13 06:37:54 2018