Repocop reports by acl

  packager rpm id test Status message
@emacs emacs-prog-modes-0.2-alt7.noarch missing-url info Missing Url: in a package.
@emacs emacs-xslt-process-2.2-alt9.1.qa2.src requires-ImageMagick info Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell.
@gnome glade3-3.8.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.
@gnome mirage-0.9.5.2-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.
@gnome mirage-0.9.5.2-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.
@gnome pympd-0.08.1-alt1.4.1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/pympd.desktop: error: value "0.06.2" for key "Version" in group "Desktop Entry" is not a known version
@gnome pympd-0.08.1-alt1.4.1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy.
@gnome pyneighborhood-0.4-alt1.2.1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/pyNeighborhood
@gnome pyneighborhood-0.4-alt1.2.1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/pyNeighborhood.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).
@gnome pyneighborhood-0.4-alt1.2.1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/pyNeighborhood.desktop: hint: value "Network;System;Utility;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
/usr/share/applications/pyNeighborhood.desktop: hint: value "Network;System;Utility;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
@kernel kernel-headers-std-def-4.9.101-alt1.x86_64 buildroot fail found paths to buildroot: /usr/include/linux-4.9.101-std-def/include/sound/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/sound/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/sound ./include/uapi/sound asequencer.h asoc.h asound.h asound_fm.h compress_offload.h compress_params.h emu10k1.h firewire.h hdsp.h hdspm.h sb16_csp.h sfnt_info.h snd_sst_tokens.h tlv.h usb_stream.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/sound ./include/sound ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/sound ./include/generated/uapi/sound ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/sound/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/sound/.install /usr/include/linux-4.9.101-std-def/include/asm-generic/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/asm-generic/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/asm-generic ./include/uapi/asm-generic auxvec.h bitsperlong.h errno-base.h errno.h fcntl.h int-l64.h int-ll64.h ioctl.h ioctls.h ipcbuf.h kvm_para.h mman-common.h mman.h msgbuf.h param.h poll.h posix_types.h resource.h sembuf.h setup.h shmbuf.h shmparam.h siginfo.h signal-defs.h signal.h socket.h sockios.h stat.h statfs.h swab.h termbits.h termios.h types.h ucontext.h unistd.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/asm-generic ./include/asm-generic ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/asm-generic ./include/generated/uapi/asm-generic ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/asm-generic/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/asm-generic/.install /usr/include/linux-4.9.101-std-def/include/asm/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/asm/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/asm ./arch/x86/include/uapi/asm a.out.h auxvec.h bitsperlong.h boot.h bootparam.h byteorder.h debugreg.h e820.h errno.h fcntl.h hw_breakpoint.h hyperv.h ioctl.h ioctls.h ipcbuf.h ist.h kvm.h kvm_para.h kvm_perf.h ldt.h mce.h mman.h msgbuf.h msr.h mtrr.h param.h perf_regs.h poll.h posix_types.h posix_types_32.h posix_types_64.h posix_types_x32.h prctl.h processor-flags.h ptrace-abi.h ptrace.h resource.h sembuf.h setup.h shmbuf.h sigcontext.h sigcontext32.h siginfo.h signal.h socket.h sockios.h stat.h statfs.h svm.h swab.h termbits.h termios.h types.h ucontext.h unistd.h vm86.h vmx.h vsyscall.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/asm ./arch/x86/include/asm msr-index.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/asm ./arch/x86/include/generated/uapi/asm unistd_32.h unistd_64.h unistd_x32.h unistd_32.h unistd_64.h unistd_x32.h; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/asm/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/asm/.install /usr/include/linux-4.9.101-std-def/include/xen/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/xen/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/xen ./include/uapi/xen evtchn.h gntalloc.h gntdev.h privcmd.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/xen ./include/xen ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/xen ./include/generated/uapi/xen ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/xen/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/xen/.install /usr/include/linux-4.9.101-std-def/include/linux/tc_act/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/tc_act/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/tc_act ./include/uapi/linux/tc_act tc_bpf.h tc_connmark.h tc_csum.h tc_defact.h tc_gact.h tc_ife.h tc_ipt.h tc_mirred.h tc_nat.h tc_pedit.h tc_skbedit.h tc_skbmod.h tc_tunnel_key.h tc_vlan.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/tc_act ./include/linux/tc_act ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/tc_act ./include/generated/uapi/linux/tc_act ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/tc_act/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/tc_act/.install /usr/include/linux-4.9.101-std-def/include/linux/dvb/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/dvb/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/dvb ./include/uapi/linux/dvb audio.h ca.h dmx.h frontend.h net.h osd.h version.h video.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/dvb ./include/linux/dvb ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/dvb ./include/generated/uapi/linux/dvb ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/dvb/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/dvb/.install /usr/include/linux-4.9.101-std-def/include/linux/android/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/android/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/android ./include/uapi/linux/android binder.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/android ./include/linux/android ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/android ./include/generated/uapi/linux/android ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/android/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/android/.install /usr/include/linux-4.9.101-std-def/include/linux/spi/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/spi/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/spi ./include/uapi/linux/spi spidev.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/spi ./include/linux/spi ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/spi ./include/generated/uapi/linux/spi ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/spi/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/spi/.install /usr/include/linux-4.9.101-std-def/include/linux/isdn/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/isdn/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/isdn ./include/uapi/linux/isdn capicmd.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/isdn ./include/linux/isdn ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/isdn ./include/generated/uapi/linux/isdn ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/isdn/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/isdn/.install /usr/include/linux-4.9.101-std-def/include/linux/hsi/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/hsi/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/hsi ./include/uapi/linux/hsi cs-protocol.h hsi_char.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/hsi ./include/linux/hsi ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/hsi ./include/generated/uapi/linux/hsi ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/hsi/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/hsi/.install /usr/include/linux-4.9.101-std-def/include/linux/netfilter_arp/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_arp/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_arp ./include/uapi/linux/netfilter_arp arp_tables.h arpt_mangle.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_arp ./include/linux/netfilter_arp ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_arp ./include/generated/uapi/linux/netfilter_arp ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_arp/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_arp/.install /usr/include/linux-4.9.101-std-def/include/linux/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux ./include/uapi/linux a.out.h acct.h adb.h adfs_fs.h affs_hardblocks.h agpgart.h aio_abi.h am437x-vpfe.h apm_bios.h arcfb.h atalk.h atm.h atm_eni.h atm_he.h atm_idt77105.h atm_nicstar.h atm_tcp.h atm_zatm.h atmapi.h atmarp.h atmbr2684.h atmclip.h atmdev.h atmioc.h atmlec.h atmmpc.h atmppp.h atmsap.h atmsvc.h audit.h aufs_type.h auto_fs.h auto_fs4.h auxvec.h ax25.h b1lli.h baycom.h bcm933xx_hcs.h bfs_fs.h binfmts.h blkpg.h blktrace_api.h bpf.h bpf_common.h bpf_perf_event.h bpqether.h bsg.h bt-bmc.h btrfs.h can.h capability.h capi.h cciss_defs.h cciss_ioctl.h cdrom.h cgroupstats.h chio.h cm4000_cs.h cn_proc.h coda.h coda_psdev.h coff.h connector.h const.h cramfs_fs.h cuda.h cyclades.h cycx_cfm.h dcbnl.h dccp.h devlink.h dlm.h dlm_device.h dlm_netlink.h dlm_plock.h dlmconstants.h dm-ioctl.h dm-log-userspace.h dn.h dqblk_xfs.h edd.h efs_fs_sb.h elf-em.h elf-fdpic.h elf.h elfcore.h errno.h errqueue.h ethtool.h eventpoll.h fadvise.h falloc.h fanotify.h fb.h fcntl.h fd.h fdreg.h fib_rules.h fiemap.h filter.h firewire-cdev.h firewire-constants.h flat.h fou.h fs.h fsl_hypervisor.h fuse.h futex.h gameport.h gen_stats.h genetlink.h gfs2_ondisk.h gigaset_dev.h gpio.h gsmmux.h gtp.h hdlc.h hdlcdrv.h hdreg.h hid.h hiddev.h hidraw.h hpet.h hsr_netlink.h hw_breakpoint.h hyperv.h hysdn_if.h i2c-dev.h i2c.h i2o-dev.h i8k.h icmp.h icmpv6.h if.h if_addr.h if_addrlabel.h if_alg.h if_arcnet.h if_arp.h if_bonding.h if_bridge.h if_cablemodem.h if_eql.h if_ether.h if_fc.h if_fddi.h if_frad.h if_hippi.h if_infiniband.h if_link.h if_ltalk.h if_macsec.h if_packet.h if_phonet.h if_plip.h if_ppp.h if_pppol2tp.h if_pppox.h if_slip.h if_team.h if_tun.h if_tunnel.h if_vlan.h if_x25.h igmp.h ila.h in.h in6.h in_route.h inet_diag.h inotify.h input-event-codes.h input.h ioctl.h ip.h ip6_tunnel.h ip_vs.h ipc.h ipmi.h ipmi_msgdefs.h ipsec.h ipv6.h ipv6_route.h ipx.h irda.h irqnr.h isdn.h isdn_divertif.h isdn_ppp.h isdnif.h iso_fs.h ivtv.h ivtvfb.h ixjuser.h jffs2.h joystick.h kcmp.h kd.h kdev_t.h kernel-page-flags.h kernel.h kernelcapi.h kexec.h keyboard.h keyctl.h kvm.h kvm_para.h l2tp.h libc-compat.h limits.h lirc.h llc.h loop.h lp.h lwtunnel.h magic.h major.h map_to_7segment.h matroxfb.h mdio.h media-bus-format.h media.h mei.h membarrier.h memfd.h mempolicy.h meye.h mic_common.h mic_ioctl.h mii.h minix_fs.h mman.h mmtimer.h mpls.h mpls_iptunnel.h mqueue.h mroute.h mroute6.h msdos_fs.h msg.h mtio.h n_r3964.h nbd.h ncp.h ncp_fs.h ncp_mount.h ncp_no.h ndctl.h neighbour.h net.h net_dropmon.h net_namespace.h net_tstamp.h netconf.h netdevice.h netfilter.h netfilter_arp.h netfilter_bridge.h netfilter_decnet.h netfilter_ipv4.h netfilter_ipv6.h netlink.h netlink_diag.h netrom.h nfc.h nfs.h nfs2.h nfs3.h nfs4.h nfs4_mount.h nfs_fs.h nfs_idmap.h nfs_mount.h nfsacl.h nl80211.h nubus.h nvme_ioctl.h nvram.h omap3isp.h omapfb.h oom.h openvswitch.h packet_diag.h param.h parport.h patchkey.h pci.h pci_regs.h perf_event.h personality.h pfkeyv2.h pg.h phantom.h phonet.h pkt_cls.h pkt_sched.h pktcdvd.h pmu.h poll.h posix_acl.h posix_acl_xattr.h posix_types.h ppdev.h ppp-comp.h ppp-ioctl.h ppp_defs.h pps.h prctl.h psci.h ptp_clock.h ptrace.h qnx4_fs.h qnxtypes.h quota.h radeonfb.h random.h raw.h rds.h reboot.h reiserfs_fs.h reiserfs_xattr.h resource.h rfkill.h rio_cm_cdev.h rio_mport_cdev.h romfs_fs.h rose.h route.h rtc.h rtnetlink.h scc.h sched.h scif_ioctl.h screen_info.h sctp.h sdla.h seccomp.h securebits.h selinux_netlink.h sem.h serial.h serial_core.h serial_reg.h serio.h shm.h signal.h signalfd.h smiapp.h snmp.h sock_diag.h socket.h sockios.h sonet.h sonypi.h sound.h soundcard.h stat.h stddef.h string.h suspend_ioctls.h swab.h sync_file.h synclink.h sysctl.h sysinfo.h target_core_user.h taskstats.h tcp.h tcp_metrics.h telephony.h termios.h thermal.h time.h times.h timex.h tiocl.h tipc.h tipc_config.h tipc_netlink.h toshiba.h tty.h tty_flags.h types.h udf_fs_i.h udp.h uhid.h uinput.h uio.h ultrasound.h un.h unistd.h unix_diag.h usbdevice_fs.h usbip.h userfaultfd.h utime.h utsname.h uuid.h uvcvideo.h v4l2-common.h v4l2-controls.h v4l2-dv-timings.h v4l2-mediabus.h v4l2-subdev.h veth.h vfio.h vhost.h videodev2.h virtio_9p.h virtio_balloon.h virtio_blk.h virtio_config.h virtio_console.h virtio_gpu.h virtio_ids.h virtio_input.h virtio_net.h virtio_pci.h virtio_ring.h virtio_rng.h virtio_scsi.h virtio_types.h virtio_vsock.h vm_sockets.h vt.h vtpm_proxy.h wait.h wanrouter.h watchdog.h wimax.h wireless.h x25.h xattr.h xfrm.h xilinx-v4l2-controls.h zorro.h zorro_ids.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux ./include/linux ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux ./include/generated/uapi/linux version.h; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/.install /usr/include/linux-4.9.101-std-def/include/linux/mmc/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/mmc/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/mmc ./include/uapi/linux/mmc ioctl.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/mmc ./include/linux/mmc ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/mmc ./include/generated/uapi/linux/mmc ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/mmc/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/mmc/.install /usr/include/linux-4.9.101-std-def/include/linux/can/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/can/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/can ./include/uapi/linux/can bcm.h error.h gw.h netlink.h raw.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/can ./include/linux/can ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/can ./include/generated/uapi/linux/can ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/can/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/can/.install /usr/include/linux-4.9.101-std-def/include/linux/byteorder/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/byteorder/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/byteorder ./include/uapi/linux/byteorder big_endian.h little_endian.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/byteorder ./include/linux/byteorder ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/byteorder ./include/generated/uapi/linux/byteorder ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/byteorder/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/byteorder/.install /usr/include/linux-4.9.101-std-def/include/linux/tc_ematch/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/tc_ematch/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/tc_ematch ./include/uapi/linux/tc_ematch tc_em_cmp.h tc_em_meta.h tc_em_nbyte.h tc_em_text.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/tc_ematch ./include/linux/tc_ematch ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/tc_ematch ./include/generated/uapi/linux/tc_ematch ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/tc_ematch/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/tc_ematch/.install /usr/include/linux-4.9.101-std-def/include/linux/hdlc/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/hdlc/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/hdlc ./include/uapi/linux/hdlc ioctl.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/hdlc ./include/linux/hdlc ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/hdlc ./include/generated/uapi/linux/hdlc ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/hdlc/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/hdlc/.install /usr/include/linux-4.9.101-std-def/include/linux/sunrpc/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/sunrpc/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/sunrpc ./include/uapi/linux/sunrpc debug.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/sunrpc ./include/linux/sunrpc ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/sunrpc ./include/generated/uapi/linux/sunrpc ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/sunrpc/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/sunrpc/.install /usr/include/linux-4.9.101-std-def/include/linux/netfilter_bridge/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_bridge/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_bridge ./include/uapi/linux/netfilter_bridge ebt_802_3.h ebt_among.h ebt_arp.h ebt_arpreply.h ebt_ip.h ebt_ip6.h ebt_limit.h ebt_log.h ebt_mark_m.h ebt_mark_t.h ebt_nat.h ebt_nflog.h ebt_pkttype.h ebt_redirect.h ebt_stp.h ebt_vlan.h ebtables.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_bridge ./include/linux/netfilter_bridge ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_bridge ./include/generated/uapi/linux/netfilter_bridge ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_bridge/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_bridge/.install /usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv4/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv4/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv4 ./include/uapi/linux/netfilter_ipv4 ip_tables.h ipt_CLUSTERIP.h ipt_ECN.h ipt_LOG.h ipt_REJECT.h ipt_TTL.h ipt_ah.h ipt_ecn.h ipt_ttl.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv4 ./include/linux/netfilter_ipv4 ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv4 ./include/generated/uapi/linux/netfilter_ipv4 ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv4/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv4/.install /usr/include/linux-4.9.101-std-def/include/linux/iio/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/iio/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/iio ./include/uapi/linux/iio events.h types.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/iio ./include/linux/iio ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/iio ./include/generated/uapi/linux/iio ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/iio/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/iio/.install /usr/include/linux-4.9.101-std-def/include/linux/usb/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/usb/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/usb ./include/uapi/linux/usb audio.h cdc-wdm.h cdc.h ch11.h ch9.h functionfs.h g_printer.h gadgetfs.h midi.h tmc.h video.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/usb ./include/linux/usb ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/usb ./include/generated/uapi/linux/usb ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/usb/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/usb/.install /usr/include/linux-4.9.101-std-def/include/linux/caif/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/caif/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/caif ./include/uapi/linux/caif caif_socket.h if_caif.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/caif ./include/linux/caif ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/caif ./include/generated/uapi/linux/caif ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/caif/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/caif/.install /usr/include/linux-4.9.101-std-def/include/linux/raid/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/raid/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/raid ./include/uapi/linux/raid md_p.h md_u.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/raid ./include/linux/raid ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/raid ./include/generated/uapi/linux/raid ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/raid/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/raid/.install /usr/include/linux-4.9.101-std-def/include/linux/netfilter/ipset/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter/ipset/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter/ipset ./include/uapi/linux/netfilter/ipset ip_set.h ip_set_bitmap.h ip_set_hash.h ip_set_list.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter/ipset ./include/linux/netfilter/ipset ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter/ipset ./include/generated/uapi/linux/netfilter/ipset ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter/ipset/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter/ipset/.install /usr/include/linux-4.9.101-std-def/include/linux/netfilter/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter ./include/uapi/linux/netfilter nf_conntrack_common.h nf_conntrack_ftp.h nf_conntrack_sctp.h nf_conntrack_tcp.h nf_conntrack_tuple_common.h nf_log.h nf_nat.h nf_tables.h nf_tables_compat.h nfnetlink.h nfnetlink_acct.h nfnetlink_compat.h nfnetlink_conntrack.h nfnetlink_cthelper.h nfnetlink_cttimeout.h nfnetlink_log.h nfnetlink_queue.h x_tables.h xt_AUDIT.h xt_CHECKSUM.h xt_CLASSIFY.h xt_CONNMARK.h xt_CONNSECMARK.h xt_CT.h xt_DSCP.h xt_HMARK.h xt_IDLETIMER.h xt_LED.h xt_LOG.h xt_MARK.h xt_NFLOG.h xt_NFQUEUE.h xt_RATEEST.h xt_SECMARK.h xt_SYNPROXY.h xt_TCPMSS.h xt_TCPOPTSTRIP.h xt_TEE.h xt_TPROXY.h xt_addrtype.h xt_bpf.h xt_cgroup.h xt_cluster.h xt_comment.h xt_connbytes.h xt_connlabel.h xt_connlimit.h xt_connmark.h xt_conntrack.h xt_cpu.h xt_dccp.h xt_devgroup.h xt_dscp.h xt_ecn.h xt_esp.h xt_hashlimit.h xt_helper.h xt_ipcomp.h xt_iprange.h xt_ipvs.h xt_l2tp.h xt_length.h xt_limit.h xt_mac.h xt_mark.h xt_multiport.h xt_nfacct.h xt_osf.h xt_owner.h xt_physdev.h xt_pkttype.h xt_policy.h xt_quota.h xt_rateest.h xt_realm.h xt_recent.h xt_rpfilter.h xt_sctp.h xt_set.h xt_socket.h xt_state.h xt_statistic.h xt_string.h xt_tcpmss.h xt_tcpudp.h xt_time.h xt_u32.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter ./include/linux/netfilter ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter ./include/generated/uapi/linux/netfilter ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter/.install /usr/include/linux-4.9.101-std-def/include/linux/wimax/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/wimax/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/wimax ./include/uapi/linux/wimax i2400m.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/wimax ./include/linux/wimax ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/wimax ./include/generated/uapi/linux/wimax ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/wimax/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/wimax/.install /usr/include/linux-4.9.101-std-def/include/linux/nfsd/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/nfsd/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/nfsd ./include/uapi/linux/nfsd cld.h debug.h export.h nfsfh.h stats.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/nfsd ./include/linux/nfsd ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/nfsd ./include/generated/uapi/linux/nfsd ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/nfsd/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/nfsd/.install /usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv6/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv6/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv6 ./include/uapi/linux/netfilter_ipv6 ip6_tables.h ip6t_HL.h ip6t_LOG.h ip6t_NPT.h ip6t_REJECT.h ip6t_ah.h ip6t_frag.h ip6t_hl.h ip6t_ipv6header.h ip6t_mh.h ip6t_opts.h ip6t_rt.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv6 ./include/linux/netfilter_ipv6 ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv6 ./include/generated/uapi/linux/netfilter_ipv6 ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv6/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/linux/netfilter_ipv6/.install /usr/include/linux-4.9.101-std-def/include/scsi/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/scsi/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/scsi ./include/uapi/scsi cxlflash_ioctl.h scsi_bsg_fc.h scsi_netlink.h scsi_netlink_fc.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/scsi ./include/scsi ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/scsi ./include/generated/uapi/scsi ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/scsi/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/scsi/.install /usr/include/linux-4.9.101-std-def/include/scsi/fc/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/scsi/fc/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/scsi/fc ./include/uapi/scsi/fc fc_els.h fc_fs.h fc_gs.h fc_ns.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/scsi/fc ./include/scsi/fc ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/scsi/fc ./include/generated/uapi/scsi/fc ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/scsi/fc/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/scsi/fc/.install /usr/include/linux-4.9.101-std-def/include/rdma/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/rdma/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/rdma ./include/uapi/rdma cxgb3-abi.h cxgb4-abi.h ib_user_cm.h ib_user_mad.h ib_user_sa.h ib_user_verbs.h mlx4-abi.h mlx5-abi.h mthca-abi.h nes-abi.h ocrdma-abi.h rdma_netlink.h rdma_user_cm.h rdma_user_rxe.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/rdma ./include/rdma ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/rdma ./include/generated/uapi/rdma ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/rdma/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/rdma/.install /usr/include/linux-4.9.101-std-def/include/rdma/hfi/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/rdma/hfi/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/rdma/hfi ./include/uapi/rdma/hfi hfi1_user.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/rdma/hfi ./include/rdma/hfi ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/rdma/hfi ./include/generated/uapi/rdma/hfi ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/rdma/hfi/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/rdma/hfi/.install /usr/include/linux-4.9.101-std-def/include/video/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/video/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/video ./include/uapi/video edid.h sisfb.h uvesafb.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/video ./include/video ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/video ./include/generated/uapi/video ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/video/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/video/.install /usr/include/linux-4.9.101-std-def/include/uapi/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/uapi/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/uapi ./include/uapi ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/uapi ./include ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/uapi ./include/generated/uapi ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/uapi/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/uapi/.install /usr/include/linux-4.9.101-std-def/include/mtd/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/mtd/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/mtd ./include/uapi/mtd inftl-user.h mtd-abi.h mtd-user.h nftl-user.h ubi-user.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/mtd ./include/mtd ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/mtd ./include/generated/uapi/mtd ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/mtd/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/mtd/.install /usr/include/linux-4.9.101-std-def/include/misc/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/misc/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/misc ./include/uapi/misc cxl.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/misc ./include/misc ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/misc ./include/generated/uapi/misc ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/misc/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/misc/.install /usr/include/linux-4.9.101-std-def/include/drm/..install.cmd: cmd_/usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/drm/.install := /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/drm ./include/uapi/drm amdgpu_drm.h drm.h drm_fourcc.h drm_mode.h drm_sarea.h exynos_drm.h i810_drm.h i915_drm.h mga_drm.h msm_drm.h nouveau_drm.h qxl_drm.h r128_drm.h radeon_drm.h savage_drm.h sis_drm.h tegra_drm.h vc4_drm.h via_drm.h virtgpu_drm.h vmwgfx_drm.h; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/drm ./include/drm ; /bin/sh scripts/headers_install.sh /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/drm ./include/generated/uapi/drm ; for F in ; do echo "\#include " > /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/drm/$$F; done; touch /usr/src/tmp/kernel-image-std-def-buildroot/usr/include/linux-4.9.101-std-def/include/drm/.install
@kernel kernel-source-u200-1.0-alt1.noarch missing-url info Missing Url: in a package.
@lxde lxdm-conf-0.2.0-alt5.1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/lxdmconf.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).
@lxde lxdm-conf-0.2.0-alt5.1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/lxdmconf.desktop: hint: value "System;Settings;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
@openldap nss_ldap-debuginfo-265-alt5.x86_64 rpm-filesystem-conflict-symlink-file warn symlink /usr/lib/debug/lib64/libnss_ldap.so.2.debug is a file in the package nss-ldapd-debuginfo-0.9.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@pgsql libecpg6.5-debuginfo-9.3.23-alt1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6.10-debuginfo-10.4-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6.6-debuginfo-9.4.18-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6.7-debuginfo-9.5.13-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6.8-1C-debuginfo-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libecpg.so.6.debug is different from the same symlink in the package libecpg6.8-debuginfo-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6.10-debuginfo-10.4-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6.6-debuginfo-9.4.18-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6.7-debuginfo-9.5.13-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6.8-1C-debuginfo-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libecpg_compat.so.3.debug is different from the same symlink in the package libecpg6.8-debuginfo-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6.10-debuginfo-10.4-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6.6-debuginfo-9.4.18-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6.7-debuginfo-9.5.13-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6.8-1C-debuginfo-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libpgtypes.so.3.debug is different from the same symlink in the package libecpg6.8-debuginfo-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@pgsql libpq5.6-debuginfo-9.3.23-alt1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libpq.so.5.debug is different from the same symlink in the package libpq5.10-debuginfo-10.4-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libpq.so.5.debug is different from the same symlink in the package libpq5.7-debuginfo-9.4.18-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libpq.so.5.debug is different from the same symlink in the package libpq5.8-debuginfo-9.5.13-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libpq.so.5.debug is different from the same symlink in the package libpq5.9-1C-debuginfo-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libpq.so.5.debug is different from the same symlink in the package libpq5.9-debuginfo-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@pgsql postgresql9.3-contrib-9.3.23-alt1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package postgresql10-contrib-10.4-alt1.x86_64, for example, /usr/bin/oid2name (35 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package postgresql9.4-contrib-9.4.18-alt1.x86_64, for example, /usr/bin/oid2name (23 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package postgresql9.5-contrib-9.5.13-alt1.x86_64, for example, /usr/bin/oid2name (28 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.
File /usr/bin/pg_xlogdump conflicts with the package postgresql9.6-1C-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package postgresql9.6-1C-contrib-9.6.9-alt1.x86_64, for example, /usr/bin/oid2name (29 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package postgresql9.6-contrib-9.6.9-alt1.x86_64, for example, /usr/bin/oid2name (31 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.
@pgsql postgresql9.3-perl-9.3.23-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql10-perl-10.4-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.5-perl-9.5.13-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-1C-perl-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/lib64/pgsql/plperl.so conflicts with the package postgresql9.6-perl-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@pgsql postgresql9.3-python-9.3.23-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql10-python-10.4-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.5-python-9.5.13-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-1C-python-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/lib64/pgsql/plpython2.so conflicts with the package postgresql9.6-python-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@pgsql postgresql9.3-server-9.3.23-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.
@pgsql postgresql9.3-tcl-9.3.23-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/pgsql/pltcl.so conflicts with the package postgresql10-tcl-10.4-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/bin/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.4-tcl-9.4.18-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/bin/pltcl_listmod /usr/bin/pltcl_loadmod conflict with the package postgresql9.5-tcl-9.5.13-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/bin/pltcl_listmod /usr/bin/pltcl_loadmod /usr/lib64/pgsql/pltcl.so conflict with the package postgresql9.6-1C-tcl-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/bin/pltcl_listmod /usr/bin/pltcl_loadmod /usr/lib64/pgsql/pltcl.so conflict with the package postgresql9.6-tcl-9.6.9-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python bombono-dvd-data-1.2.4-alt4.noarch freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/bombono-dvd.desktop: error: file contains multiple keys named "GenericName" in group "Desktop Entry"
@python digitemp-utils-3.6.0-alt1.2.1.x86_64 unsafe-tmp-usage-in-scripts fail 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/digitemp/rrdb/log-temperature.pl: $ grep -A5 -B5 /tmp/ /usr/share/digitemp/rrdb/log-temperature.pl } else { die "Could not find rrdtool binary\n"; } # The RRD database to put the data into $wx_rrd = "/tmp/digitemp.rrd"; # Read the output from digitemp # Output in form 0\troom\tattic\tdrink open( DIGITEMP, "digitemp -a -q -o2 |" ); -- chomp; if( $_ =~ /^nanosleep/i ) { $now = localtime; open( ERRLOG, ">>/tmp/dt-error") or die "Error opening dt-error"; print ERRLOG "nanosleep error at $now\n"; close( ERRLOG ); die "nanosleep error"; } else { -- # This section was used to create up to date email signature files # Create the email header in Fahrenheit #open( HEADER, ">/tmp/.header") or die "Error opening .header"; #$now = localtime; #print HEADER "[$now]--[Inside "; #printf HEADER "%0.2f",ctof( $room ); #print HEADER "F]--[Outside "; Found error in /usr/share/digitemp/perl/maxplot: $ grep -A5 -B5 /tmp/ /usr/share/digitemp/perl/maxplot $im->string(gdSmallFont,$hmargin,&ytransform(-30),"Harddrive #1",$red); $im->string(gdSmallFont,$hmargin,&ytransform(-35),"Room Temperature",$green); $im->string(gdSmallFont,$hmargin,&ytransform(-40),"Outside Temperature",$orange); # Output it to a .gif image file open( PLOT, ">/tmp/tempplot.gif"); print PLOT $im->gif; close(PLOT); # copy the image to its final destination and make sure it is owned # by the right person. system "cp /tmp/tempplot.gif /home/nexus/.public_html/tempplot.gif"; system "chown nexus.users /home/nexus/.public_html/tempplot.gif"; system "chmod 0644 /home/nexus/.public_html/tempplot.gif";
@python fail2ban-0.9.6-alt1.S1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/fail2ban/tests/action_d/test_badips.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/lib/python2.7/site-packages/fail2ban/tests/action_d/test_badips.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/lib/python2.7/site-packages/fail2ban/tests/action_d/test_badips.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/lib/python2.7/site-packages/fail2ban/tests/action_d/test_smtp.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/lib/python2.7/site-packages/fail2ban/tests/action_d/test_smtp.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/lib/python2.7/site-packages/fail2ban/tests/action_d/test_smtp.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.
@python fail2ban-0.9.6-alt1.S1.noarch init-condrestart fail /etc/rc.d/init.d/fail2ban: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix.
@python fail2ban-0.9.6-alt1.S1.noarch init-lsb warn /etc/rc.d/init.d/fail2ban: lsb init header missing. See http://www.altlinux.org/Services_Policy for details.
@python fail2ban-0.9.6-alt1.S1.noarch 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.
@python ipython-5.5.0-alt3.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/IPython/testing/plugin/test_combo.txt: 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/lib/python2.7/site-packages/IPython/testing/plugin/test_example.txt: 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/lib/python2.7/site-packages/IPython/testing/plugin/test_exampleip.txt: 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/lib/python2.7/site-packages/IPython/testing/plugin/test_ipdoctest.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/lib/python2.7/site-packages/IPython/testing/plugin/test_ipdoctest.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/lib/python2.7/site-packages/IPython/testing/plugin/test_ipdoctest.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/lib/python2.7/site-packages/IPython/testing/plugin/test_refs.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/lib/python2.7/site-packages/IPython/testing/plugin/test_refs.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/lib/python2.7/site-packages/IPython/testing/plugin/test_refs.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.
@python libprelude-doc-4.0.0-alt1_3.3.1.noarch big-changelog info Package contains big ChangeLog. Gzip it.
@python lorem-ipsum-generator-0.3-alt1.svn20090927.1.noarch freedesktop-categories fail Main Categories consist of those categories that every conforming desktop environment MUST support.(http://standards.freedesktop.org/menu-spec/latest/apa.html). None found in /usr/share/applications/lorem-ipsum-generator.desktop. please, fix. Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/lorem-ipsum-generator.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).
@python lorem-ipsum-generator-0.3-alt1.svn20090927.1.noarch freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lorem-ipsum-generator.desktop: error: value "0.1" for key "Version" in group "Desktop Entry" is not a known version
/usr/share/applications/lorem-ipsum-generator.desktop: error: file contains key "Category" in group "Desktop Entry", but keys extending the format should start with "X-"
/usr/share/applications/lorem-ipsum-generator.desktop: error: key "GenericName[en_AU]" in group "Desktop Entry" is a localized key, but there is no non-localized key "GenericName"
/usr/share/applications/lorem-ipsum-generator.desktop: error: key "Comment[en_AU]" in group "Desktop Entry" is a localized key, but there is no non-localized key "Comment"
@python pymol-1.8.6.0-alt1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it.
@python pyrpm-0.69-alt2.1.noarch unsafe-tmp-usage-in-scripts fail 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/bin/pyrpmkickstart: $ grep -A5 -B5 /tmp/ /usr/bin/pyrpmkickstart return 1 source_dir = stage2_dir+"/mnt/source" target_dir = stage2_dir+"/mnt/sysimage" repos_dir = stage2_dir+"/mnt/repos" # nfs repo base directory cache_dir = stage2_dir+"/tmp/cache" # create mount points create_dir("", source_dir) create_dir("", target_dir) create_dir("", repos_dir) -- # create cache dir pyrpm.rpmconfig.cachedir = cache_dir # global logging create_dir(tempdir, "/tmp") log_filename = tempdir+"/tmp/pyrpmkickstart.log" log_file = pyrpm.logger.FileLog(log_filename) log.info1("Logging to '%s'.", log_filename) log.addInfoLogging("*", log_file, fmt="%(date)s %(label)s%(message)s") log.addDebugLogging("*", log_file, fmt="%(date)s %(label)s%(message)s") # set extra file logging -- del t # create temporary devices which are usable by grub (hda, hda1, ..) devmap = { } # device mapping for disk in hds: dev = "/tmp/%s" % disk copy_device(diskmap[disk]["device"], target_chroot, source_dir=stage2_dir, target=dev) devmap[diskmap[disk]["device"]] = dev for onpart in partitionmap: if partitionmap[onpart].has_key("raid"): pass elif partitionmap[onpart].has_key("volgroup"): # already done pass else: dev = "/tmp/%s%d" % (partitionmap[onpart]["disk"], partitionmap[onpart]["id"]) copy_device(partitionmap[onpart]["device"], target_chroot, source_dir=stage2_dir, target=dev) devmap[partitionmap[onpart]["device"]] = dev -- if not create_file(target_chroot, "/boot/grub/devices.map", content): return 1 # grub setup content = [ '/sbin/grub --batch >/tmp/grub-setup.log <
@python python-module-Pillow-devel-5.1.0-alt2.noarch 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.
@python python-module-PyAMF-0.8.0-alt1.1.x86_64 altlinux-python-test-is-packaged info /usr/lib64/python2.7/site-packages/pyamf/adapters/tests/google/test_blobstore.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/site-packages/pyamf/adapters/tests/google/test_blobstore.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/site-packages/pyamf/adapters/tests/google/test_blobstore.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/site-packages/pyamf/adapters/tests/google/test_datastore_types.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/site-packages/pyamf/adapters/tests/google/test_datastore_types.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/site-packages/pyamf/adapters/tests/google/test_datastore_types.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/site-packages/pyamf/adapters/tests/google/test_ndb.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/site-packages/pyamf/adapters/tests/google/test_ndb.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/site-packages/pyamf/adapters/tests/google/test_ndb.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/site-packages/pyamf/adapters/tests/google/test_xdb.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/site-packages/pyamf/adapters/tests/google/test_xdb.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/site-packages/pyamf/adapters/tests/google/test_xdb.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/site-packages/pyamf/adapters/tests/test_array.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/site-packages/pyamf/adapters/tests/test_array.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/site-packages/pyamf/adapters/tests/test_array.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/site-packages/pyamf/adapters/tests/test_collections.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/site-packages/pyamf/adapters/tests/test_collections.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/site-packages/pyamf/adapters/tests/test_collections.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/site-packages/pyamf/adapters/tests/test_django.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/site-packages/pyamf/adapters/tests/test_django.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/site-packages/pyamf/adapters/tests/test_django.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/site-packages/pyamf/adapters/tests/test_elixir.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/site-packages/pyamf/adapters/tests/test_elixir.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/site-packages/pyamf/adapters/tests/test_elixir.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/site-packages/pyamf/adapters/tests/test_sqlalchemy.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/site-packages/pyamf/adapters/tests/test_sqlalchemy.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/site-packages/pyamf/adapters/tests/test_sqlalchemy.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/site-packages/pyamf/adapters/tests/test_weakref.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/site-packages/pyamf/adapters/tests/test_weakref.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/site-packages/pyamf/adapters/tests/test_weakref.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.
@python python-module-Pyrex-0.9.9-alt1.1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/lib/python2.7/site-packages/Pyrex/Mac/DarwinSystem.py
/usr/lib/python2.7/site-packages/Pyrex/Mac/DarwinSystem.pyc
/usr/lib/python2.7/site-packages/Pyrex/Mac/DarwinSystem.pyo
/usr/lib/python2.7/site-packages/Pyrex/Mac/MacSystem.py
/usr/lib/python2.7/site-packages/Pyrex/Mac/MacSystem.pyc
/usr/lib/python2.7/site-packages/Pyrex/Mac/MacSystem.pyo
/usr/lib/python2.7/site-packages/Pyrex/Mac/MacUtils.py
/usr/lib/python2.7/site-packages/Pyrex/Mac/MacUtils.pyc
/usr/lib/python2.7/site-packages/Pyrex/Mac/MacUtils.pyo
/usr/lib/python2.7/site-packages/Pyrex/Mac/TS_Misc_Suite.py
/usr/lib/python2.7/site-packages/Pyrex/Mac/TS_Misc_Suite.pyc
/usr/lib/python2.7/site-packages/Pyrex/Mac/TS_Misc_Suite.pyo
/usr/lib/python2.7/site-packages/Pyrex/Mac/__init__.py
/usr/lib/python2.7/site-packages/Pyrex/Mac/__init__.pyc
/usr/lib/python2.7/site-packages/Pyrex/Mac/__init__.pyo
/usr/lib/python2.7/site-packages/Pyrex/Mac/setup.py
/usr/lib/python2.7/site-packages/Pyrex/Mac/setup.pyc
/usr/lib/python2.7/site-packages/Pyrex/Mac/setup.pyo
/usr/lib/python2.7/site-packages/Pyrex/Plex/test_tm.py
/usr/lib/python2.7/site-packages/Pyrex/Plex/test_tm.pyc
/usr/lib/python2.7/site-packages/Pyrex/Plex/test_tm.pyo
@python python-module-SPARQLWrapper-1.8.0-alt2.1.src 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.
@python python-module-Scientific-debuginfo-2.9.3-alt2.x86_64 buildroot fail found paths to buildroot: /usr/lib/debug/usr/bin/mpipython.debug: Binary file /usr/lib/debug/usr/bin/mpipython.debug matches
@python python-module-ZODB-5.3.0-alt1.1.src 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.
@python python-module-aiodns-1.1.1-alt1.noarch missing-url info Missing Url: in a package.
@python python-module-apiclient-1.0.3-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/lib/python2.7/site-packages/apiclient/__init__.py /usr/lib/python2.7/site-packages/apiclient/__init__.pyc /usr/lib/python2.7/site-packages/apiclient/__init__.pyo conflict with the package python-module-google-api-client-1.6.7-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.
@python python-module-autobahn-17.7.1-alt1.1.x86_64 altlinux-python-test-is-packaged info /usr/lib64/python2.7/site-packages/autobahn/test/test_util.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/site-packages/autobahn/test/test_util.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/site-packages/autobahn/test/test_util.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.
@python python-module-autobahn-docs-17.7.1-alt1.1.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.
@python python-module-boto3-1.4.6-alt1.1.noarch altlinux-python-test-is-packaged experimental /usr/lib/python2.7/site-packages/boto3/examples/cloudfront.rst: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/boto3/examples/s3.rst: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
@python python-module-cubicweb-3.25.3-alt2.1.src 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.
@python python-module-dap-2.2.6.7-alt1.svn20081222.3.1.src unmet-dependency-build-missing-package fail build dependency python-module-cheetah not found.
@python python-module-dataflake-1.4-alt1.1.1.1.1.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/lib64/python2.7/site-packages/dataflake/__init__.py /usr/lib64/python2.7/site-packages/dataflake/__init__.pyc /usr/lib64/python2.7/site-packages/dataflake/__init__.pyo conflict with the package python-module-dataflake.fakeldap-2.1-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-dataflake.fakeldap-2.1-alt1.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/lib64/python2.7/site-packages/dataflake/__init__.py /usr/lib64/python2.7/site-packages/dataflake/__init__.pyc /usr/lib64/python2.7/site-packages/dataflake/__init__.pyo conflict with the package python-module-dataflake-1.4-alt1.1.1.1.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.
@python python-module-deform-2.0-alt2.a2.git20141001.1.1.noarch altlinux-python-test-is-packaged experimental /usr/lib/python2.7/site-packages/deform/static/tinymce/plugins/example/plugin.min.js: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/deform/static/tinymce/plugins/example_dependency/plugin.min.js: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
@python python-module-django-admin-tools-0.8.0-alt1.noarch buildroot fail found paths to buildroot: /usr/share/doc/python-module-django-admin-tools-0.8.0/docs/_build/doctrees/dashboard.doctree: Binary file /usr/share/doc/python-module-django-admin-tools-0.8.0/docs/_build/doctrees/dashboard.doctree matches /usr/share/doc/python-module-django-admin-tools-0.8.0/docs/_build/doctrees/menu.doctree: Binary file /usr/share/doc/python-module-django-admin-tools-0.8.0/docs/_build/doctrees/menu.doctree matches
@python python-module-django-cms3.0-3.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python-module-django-cms-2.1.5-alt3.noarch, for example, /usr/lib/python2.7/site-packages/cms/__init__.py (442 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package python-module-django-cms2.3-2.3.5-alt3.noarch, for example, /usr/lib/python2.7/site-packages/cms/__init__.py (513 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.
@python python-module-django-countries-4.0-alt1.x86_64 altlinux-python-test-is-packaged info /usr/lib64/python2.7/site-packages/django_countries/tests/test_countries.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/site-packages/django_countries/tests/test_countries.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/site-packages/django_countries/tests/test_countries.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/site-packages/django_countries/tests/test_drf.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/site-packages/django_countries/tests/test_drf.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/site-packages/django_countries/tests/test_drf.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/site-packages/django_countries/tests/test_fields.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/site-packages/django_countries/tests/test_fields.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/site-packages/django_countries/tests/test_fields.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/site-packages/django_countries/tests/test_settings.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/site-packages/django_countries/tests/test_settings.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/site-packages/django_countries/tests/test_settings.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/site-packages/django_countries/tests/test_tags.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/site-packages/django_countries/tests/test_tags.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/site-packages/django_countries/tests/test_tags.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/site-packages/django_countries/tests/test_widgets.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/site-packages/django_countries/tests/test_widgets.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/site-packages/django_countries/tests/test_widgets.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.
@python python-module-django-facebook-utils-1.0.4-alt1.git20130201.1.1.noarch rpm-filesystem-conflict-file-file warn Files /usr/lib/python2.7/site-packages/facebook_utils/__init__.py /usr/lib/python2.7/site-packages/facebook_utils/__init__.pyc /usr/lib/python2.7/site-packages/facebook_utils/__init__.pyo conflict with the package python-module-facebook_utils-0.20.3-alt1.git20140717.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-django-filter-1.0.1-alt1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/tests/rest_framework/test_backends.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/lib/python2.7/site-packages/tests/rest_framework/test_backends.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/lib/python2.7/site-packages/tests/rest_framework/test_backends.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/lib/python2.7/site-packages/tests/rest_framework/test_filters.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/lib/python2.7/site-packages/tests/rest_framework/test_filters.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/lib/python2.7/site-packages/tests/rest_framework/test_filters.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/lib/python2.7/site-packages/tests/rest_framework/test_filterset.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/lib/python2.7/site-packages/tests/rest_framework/test_filterset.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/lib/python2.7/site-packages/tests/rest_framework/test_filterset.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.
@python python-module-django-publisher-0.0.3-alt1.1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python-module-django-cms-2.1.5-alt3.noarch, for example, /usr/lib/python2.7/site-packages/publisher/__init__.py (6 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.
@python python-module-django-socketio-0.3.9-alt1.git20140105.1.1.x86_64 altlinux-python-test-is-packaged experimental /usr/lib64/python2.7/site-packages/django_socketio/example_project/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/events.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/events.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/events.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/models.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/models.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/models.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/static/css/chat.css: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/static/js/chat.js: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/templates/base.html: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/templates/room.html: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/templates/rooms.html: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/templates/system_message.html: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/urls.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/urls.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/urls.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/views.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/views.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/chat/views.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/manage.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/manage.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/manage.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/settings.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/settings.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/settings.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/urls.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/urls.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/django_socketio/example_project/urls.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
@python python-module-django-uni-form-0.9.0-alt2.2.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/uni_form/tests/test_settings.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/lib/python2.7/site-packages/uni_form/tests/test_settings.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/lib/python2.7/site-packages/uni_form/tests/test_settings.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.
@python python-module-django-uni-form-0.9.0-alt2.2.noarch macos-ds-store-file-in-package warn There is a file in the package named .DS_Store or .DS_Store.gz, the file name used by Mac OS X to store folder attributes. Such files are generally useless in packages and were usually accidentally included by copying complete directories from the source tarball.
@python python-module-egenix-mx-experimental-3.0.0-alt4.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/lib/python2.7/site-packages/mx/Tidy/README
/usr/lib/python2.7/site-packages/mx/Tidy/mxTidy/input.html
/usr/lib/python2.7/site-packages/mx/Tidy/mxTidy/mxTidy.h
/usr/lib/python2.7/site-packages/mx/Tidy/mxTidy/mxh.h
@python python-module-facebook-2.3.14-alt1.git20140409.1.1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python-module-facebook_api-0.1.4-alt1.1.noarch, for example, /usr/lib/python2.7/site-packages/facebook/__init__.py (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-facebook-ads-api-0.3.0-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/lib/python2.7/site-packages/facebook.py /usr/lib/python2.7/site-packages/facebook.pyc /usr/lib/python2.7/site-packages/facebook.pyo conflict with the package python-module-geventhttpclient-facebook-0.4.4-alt1.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/lib/python2.7/site-packages/facebook.py /usr/lib/python2.7/site-packages/facebook.pyc /usr/lib/python2.7/site-packages/facebook.pyo conflict with the package python-module-requests-facebook-0.4.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.
@python python-module-facebook-scribe-2.0-alt2.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python-module-fb303-0.10.0-alt1_9jpp8.noarch, for example, /usr/lib/python2.7/site-packages/fb303/FacebookService.py (9 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.1.1.noarch rpm-filesystem-conflict-file-file warn Files /usr/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-facebook_api-0.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-facebook_api-0.1.4-alt1.1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python-module-facebook-2.3.14-alt1.git20140409.1.1.noarch, for example, /usr/lib/python2.7/site-packages/facebook/__init__.py (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-facebook_utils-0.20.3-alt1.git20140717.1.noarch rpm-filesystem-conflict-file-file warn Files /usr/lib/python2.7/site-packages/facebook_utils/__init__.py /usr/lib/python2.7/site-packages/facebook_utils/__init__.pyc /usr/lib/python2.7/site-packages/facebook_utils/__init__.pyo conflict with the package python-module-django-facebook-utils-1.0.4-alt1.git20130201.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-fake-factory-docs-0.5.0-alt1.git20150222.1.1.1.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.
@python python-module-fido-4.2.2-alt1.1.src 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.
@python python-module-filterpy-1.1.0-alt1.1.noarch altlinux-python-test-is-packaged experimental /usr/lib/python2.7/site-packages/filterpy/examples/GetRadar.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/GetRadar.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/GetRadar.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/RadarEKF.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/RadarEKF.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/RadarEKF.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/RadarUKF.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/RadarUKF.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/RadarUKF.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/bearing_only.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/bearing_only.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/bearing_only.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/radar_sim.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/radar_sim.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/filterpy/examples/radar_sim.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
@python python-module-geventhttpclient-1.3.1-alt1.x86_64 altlinux-python-test-is-packaged info /usr/lib64/python2.7/site-packages/geventhttpclient/tests/test_client.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/site-packages/geventhttpclient/tests/test_client.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/site-packages/geventhttpclient/tests/test_client.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/site-packages/geventhttpclient/tests/test_headers.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/site-packages/geventhttpclient/tests/test_headers.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/site-packages/geventhttpclient/tests/test_headers.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/site-packages/geventhttpclient/tests/test_httplib.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/site-packages/geventhttpclient/tests/test_httplib.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/site-packages/geventhttpclient/tests/test_httplib.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/site-packages/geventhttpclient/tests/test_keep_alive.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/site-packages/geventhttpclient/tests/test_keep_alive.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/site-packages/geventhttpclient/tests/test_keep_alive.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/site-packages/geventhttpclient/tests/test_network_failures.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/site-packages/geventhttpclient/tests/test_network_failures.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/site-packages/geventhttpclient/tests/test_network_failures.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/site-packages/geventhttpclient/tests/test_no_module_ssl.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/site-packages/geventhttpclient/tests/test_no_module_ssl.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/site-packages/geventhttpclient/tests/test_no_module_ssl.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/site-packages/geventhttpclient/tests/test_parser.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/site-packages/geventhttpclient/tests/test_parser.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/site-packages/geventhttpclient/tests/test_parser.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/site-packages/geventhttpclient/tests/test_ssl.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/site-packages/geventhttpclient/tests/test_ssl.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/site-packages/geventhttpclient/tests/test_ssl.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/site-packages/geventhttpclient/tests/test_url.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/site-packages/geventhttpclient/tests/test_url.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/site-packages/geventhttpclient/tests/test_url.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/site-packages/geventhttpclient/tests/test_useragent.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/site-packages/geventhttpclient/tests/test_useragent.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/site-packages/geventhttpclient/tests/test_useragent.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.
@python python-module-geventhttpclient-facebook-0.4.4-alt1.1.1.noarch rpm-filesystem-conflict-file-file warn Files /usr/lib/python2.7/site-packages/facebook.py /usr/lib/python2.7/site-packages/facebook.pyc /usr/lib/python2.7/site-packages/facebook.pyo conflict with the package python-module-facebook-ads-api-0.3.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.
Files /usr/lib/python2.7/site-packages/facebook.py /usr/lib/python2.7/site-packages/facebook.pyc /usr/lib/python2.7/site-packages/facebook.pyo conflict with the package python-module-requests-facebook-0.4.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.
@python python-module-google-api-client-1.6.7-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/lib/python2.7/site-packages/apiclient/__init__.py /usr/lib/python2.7/site-packages/apiclient/__init__.pyc /usr/lib/python2.7/site-packages/apiclient/__init__.pyo conflict with the package python-module-apiclient-1.0.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.
@python python-module-greenlet-0.4.11-alt1.1.1.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.
@python python-module-guzzle_sphinx_theme-0.7.11-alt1.1.noarch macos-ds-store-file-in-package warn There is a file in the package named .DS_Store or .DS_Store.gz, the file name used by Mac OS X to store folder attributes. Such files are generally useless in packages and were usually accidentally included by copying complete directories from the source tarball.
@python python-module-html5lib-0.999999999-alt4.src 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.
@python python-module-http-checks-0.2.0-alt1.1.src 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.
@python python-module-inotifyx-0.2.2-alt1.bzr20140825.1.x86_64 buildroot fail found paths to buildroot: /usr/lib64/python2.7/site-packages/inotifyx/distinfo.py: install_purelib = u'/usr/src/tmp/python-module-inotifyx-buildroot/usr/lib/python2.7/site-packages'
install_platlib = u'/usr/src/tmp/python-module-inotifyx-buildroot/usr/lib64/python2.7/site-packages'
install_lib = u'/usr/src/tmp/python-module-inotifyx-buildroot/usr/lib64/python2.7/site-packages'
install_headers = u'/usr/src/tmp/python-module-inotifyx-buildroot/usr/include/python2.7/inotifyx'
install_scripts = u'/usr/src/tmp/python-module-inotifyx-buildroot/usr/bin'
install_data = u'/usr/src/tmp/python-module-inotifyx-buildroot/usr'
install_data_arch = u'/usr/src/tmp/python-module-inotifyx-buildroot/usr/lib'
install_data_arch_pkg = u'/usr/src/tmp/python-module-inotifyx-buildroot/usr/lib/inotifyx'
install_data_indep = u'/usr/src/tmp/python-module-inotifyx-buildroot/usr/share'
install_data_indep_pkg = u'/usr/src/tmp/python-module-inotifyx-buildroot/usr/share/inotifyx'
@python python-module-js.tinymce-4.2.7-alt1.x86_64 altlinux-python-test-is-packaged experimental /usr/lib64/python2.7/site-packages/js/tinymce/resources/plugins/example/dialog.html: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/js/tinymce/resources/plugins/example/plugin.js: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/js/tinymce/resources/plugins/example/plugin.min.js: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/js/tinymce/resources/plugins/example_dependency/plugin.js: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/js/tinymce/resources/plugins/example_dependency/plugin.min.js: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
@python python-module-json_resource-0.2.11-alt1.1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/json_resource/tests/test_collection.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/lib/python2.7/site-packages/json_resource/tests/test_collection.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/lib/python2.7/site-packages/json_resource/tests/test_collection.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/lib/python2.7/site-packages/json_resource/tests/test_instance.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/lib/python2.7/site-packages/json_resource/tests/test_instance.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/lib/python2.7/site-packages/json_resource/tests/test_instance.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/lib/python2.7/site-packages/json_resource/tests/test_resource.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/lib/python2.7/site-packages/json_resource/tests/test_resource.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/lib/python2.7/site-packages/json_resource/tests/test_resource.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/lib/python2.7/site-packages/json_resource/tests/test_store.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/lib/python2.7/site-packages/json_resource/tests/test_store.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/lib/python2.7/site-packages/json_resource/tests/test_store.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.
@python python-module-ladon-0.9.40-alt1.1.src 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.
@python python-module-martian-1.1-alt2.S1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/martian/tests/test_all.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/lib/python2.7/site-packages/martian/tests/test_all.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/lib/python2.7/site-packages/martian/tests/test_all.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.
@python python-module-ndg-httpsclient-docs-0.4.2-alt1.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.
@python python-module-ndg.oauth.client.examples-0.5.1-alt1.git20131210.1.1.x86_64 altlinux-python-test-is-packaged experimental /usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/README: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/bearer_tok/README: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/bearer_tok/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/bearer_tok/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/bearer_tok/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/bearer_tok/bearer_tok_client_app.ini: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/bearer_tok/bearer_tok_client_app_serve.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/bearer_tok/bearer_tok_client_app_serve.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/bearer_tok/bearer_tok_client_app_serve.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/README: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/pki/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/pki/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/pki/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/pki/ca/8764c6d9.0: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/pki/ca/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/pki/ca/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/pki/ca/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/pki/ca/d573507a.0: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/pki/localhost.crt: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/shared_config/pki/localhost.key: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/slcs/README: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/slcs/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/slcs/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/slcs/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/slcs/slcs_client_app.ini: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/slcs/slcs_client_app_serve.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/slcs/slcs_client_app_serve.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/client/examples/slcs/slcs_client_app_serve.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
@python python-module-ndg.oauth.server.examples-0.5.1-alt1.git20131210.1.1.x86_64 altlinux-python-test-is-packaged experimental /usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/README: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/README: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/bearer_tok_server_app.ini: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/bearer_tok_server_app_serve.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/bearer_tok_server_app_serve.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/bearer_tok_server_app_serve.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/client_register.ini: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/passwd: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/repoze_who.ini: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/static/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/static/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/static/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/static/layout/CEDA_RightButton60.png: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/static/layout/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/static/layout/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/static/layout/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/static/layout/default.css: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/static/layout/help.png: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/templates/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/templates/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/templates/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/templates/auth_client_form.html: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/templates/base.html: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/templates/login_cancelled.html: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/bearer_tok/templates/login_form.html: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/README: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/pki/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/pki/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/pki/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/pki/ca/530f7122.0: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/pki/ca/7ed47087.0: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/pki/ca/8764c6d9.0: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/pki/ca/98ef0ee5.0: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/pki/ca/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/pki/ca/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/pki/ca/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/pki/ca/d573507a.0: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/pki/ca/ffc3d59b.0: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/shared_config/pki/host.pem: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/README: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/client_register.ini: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/passwd: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/repoze_who.ini: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/slcs_server_app.ini: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/slcs_server_app_serve.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/slcs_server_app_serve.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/slcs_server_app_serve.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/static/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/static/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/static/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/static/layout/CEDA_RightButton60.png: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/static/layout/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/static/layout/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/static/layout/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/static/layout/default.css: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/static/layout/help.png: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/templates/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/templates/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/templates/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/templates/auth_client_form.html: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/templates/base.html: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/templates/login_cancelled.html: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/slcs/templates/login_form.html: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/utils.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/utils.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/ndg/oauth/server/examples/utils.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
@python python-module-nibabel-2.2.1-alt2.src unmet-dependency-build-missing-package fail build dependency python-module-pydicom not found.
@python python-module-numdifftools-doc-0.9.12-alt1.git20150828.1.1.1.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.
@python python-module-optimus-0.0.2-alt1.1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/optimus/templates/tornado/tests/handlers/test_hello.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/lib/python2.7/site-packages/optimus/templates/tornado/tests/handlers/test_hello.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/lib/python2.7/site-packages/optimus/templates/tornado/tests/handlers/test_hello.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.
@python python-module-oslotest-2.10.0-alt1.1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/oslotest/tests/unit/test_base.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/lib/python2.7/site-packages/oslotest/tests/unit/test_base.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/lib/python2.7/site-packages/oslotest/tests/unit/test_base.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/lib/python2.7/site-packages/oslotest/tests/unit/test_createfile.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/lib/python2.7/site-packages/oslotest/tests/unit/test_createfile.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/lib/python2.7/site-packages/oslotest/tests/unit/test_createfile.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/lib/python2.7/site-packages/oslotest/tests/unit/test_log.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/lib/python2.7/site-packages/oslotest/tests/unit/test_log.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/lib/python2.7/site-packages/oslotest/tests/unit/test_log.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/lib/python2.7/site-packages/oslotest/tests/unit/test_mockpatch.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/lib/python2.7/site-packages/oslotest/tests/unit/test_mockpatch.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/lib/python2.7/site-packages/oslotest/tests/unit/test_mockpatch.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/lib/python2.7/site-packages/oslotest/tests/unit/test_modules.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/lib/python2.7/site-packages/oslotest/tests/unit/test_modules.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/lib/python2.7/site-packages/oslotest/tests/unit/test_modules.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/lib/python2.7/site-packages/oslotest/tests/unit/test_moxstubout.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/lib/python2.7/site-packages/oslotest/tests/unit/test_moxstubout.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/lib/python2.7/site-packages/oslotest/tests/unit/test_moxstubout.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/lib/python2.7/site-packages/oslotest/tests/unit/test_output.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/lib/python2.7/site-packages/oslotest/tests/unit/test_output.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/lib/python2.7/site-packages/oslotest/tests/unit/test_output.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/lib/python2.7/site-packages/oslotest/tests/unit/test_timeout.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/lib/python2.7/site-packages/oslotest/tests/unit/test_timeout.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/lib/python2.7/site-packages/oslotest/tests/unit/test_timeout.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.
@python python-module-pathtools-0.1.2-alt1.src 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.
@python python-module-peak-0.5-alt2.alpha4.svn.2590.1.1.x86_64 altlinux-python-test-is-packaged info /usr/lib64/python2.7/site-packages/peak/config/tests/test_keys.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/site-packages/peak/config/tests/test_keys.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/site-packages/peak/config/tests/test_keys.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/site-packages/peak/config/tests/test_links.ini: 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/site-packages/peak/events/tests/test_events.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/site-packages/peak/events/tests/test_events.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/site-packages/peak/events/tests/test_events.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/site-packages/peak/events/tests/test_twisted.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/site-packages/peak/events/tests/test_twisted.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/site-packages/peak/events/tests/test_twisted.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/site-packages/peak/persistence/tests/test_cache.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/site-packages/peak/persistence/tests/test_cache.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/site-packages/peak/persistence/tests/test_cache.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/site-packages/peak/persistence/tests/test_list.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/site-packages/peak/persistence/tests/test_list.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/site-packages/peak/persistence/tests/test_list.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/site-packages/peak/persistence/tests/test_persistence.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/site-packages/peak/persistence/tests/test_persistence.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/site-packages/peak/persistence/tests/test_persistence.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/site-packages/peak/query/tests/test_algebra.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/site-packages/peak/query/tests/test_algebra.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/site-packages/peak/query/tests/test_algebra.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/site-packages/peak/running/tests/test_cluster.txt: 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/site-packages/peak/running/tests/test_logs.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/site-packages/peak/running/tests/test_logs.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/site-packages/peak/running/tests/test_logs.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/site-packages/peak/storage/tests/test_undo.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/site-packages/peak/storage/tests/test_undo.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/site-packages/peak/storage/tests/test_undo.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/site-packages/peak/util/tests/test_conflict.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/site-packages/peak/util/tests/test_conflict.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/site-packages/peak/util/tests/test_conflict.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/site-packages/peak/util/tests/test_expr.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/site-packages/peak/util/tests/test_expr.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/site-packages/peak/util/tests/test_expr.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/site-packages/peak/util/tests/test_mockdb.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/site-packages/peak/util/tests/test_mockdb.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/site-packages/peak/util/tests/test_mockdb.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/site-packages/peak/util/tests/test_mockets.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/site-packages/peak/util/tests/test_mockets.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/site-packages/peak/util/tests/test_mockets.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/site-packages/peak/util/tests/test_signature.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/site-packages/peak/util/tests/test_signature.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/site-packages/peak/util/tests/test_signature.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/site-packages/peak/web/tests/test_environ.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/site-packages/peak/web/tests/test_environ.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/site-packages/peak/web/tests/test_environ.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/site-packages/peak/web/tests/test_resources.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/site-packages/peak/web/tests/test_resources.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/site-packages/peak/web/tests/test_resources.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/site-packages/peak/web/tests/test_sitemap.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/site-packages/peak/web/tests/test_sitemap.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/site-packages/peak/web/tests/test_sitemap.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/site-packages/peak/web/tests/test_templates.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/site-packages/peak/web/tests/test_templates.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/site-packages/peak/web/tests/test_templates.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.
@python python-module-phonon-2.0-alt1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/test/test_client.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/lib/python2.7/site-packages/test/test_client.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/lib/python2.7/site-packages/test/test_client.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.
@python python-module-phonon-2.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python2.7/site-packages/test/__init__.py conflicts with the package python-module-sqlalchemy_monetdb-1.0.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-pisa-3.0.33-alt2.noarch rpm-filesystem-conflict-file-file warn Files /usr/lib/python2.7/site-packages/sx/__init__.py /usr/lib/python2.7/site-packages/sx/__init__.pyc /usr/lib/python2.7/site-packages/sx/__init__.pyo conflict with the package libsx-2.17-alt1_9.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-ptest-1.7.4-alt1.1.noarch rpm-filesystem-conflict-file-file warn File /usr/bin/ptest conflicts with the package parmetis-4.0.3-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-pycrypto-docs-2.7-alt3.a1.git20140620.1.1.1.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.
@python python-module-pyface-5.1.0-alt1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/pyface/action/tests/test_action.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/lib/python2.7/site-packages/pyface/action/tests/test_action.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/lib/python2.7/site-packages/pyface/action/tests/test_action.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/lib/python2.7/site-packages/pyface/action/tests/test_action_controller.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/lib/python2.7/site-packages/pyface/action/tests/test_action_controller.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/lib/python2.7/site-packages/pyface/action/tests/test_action_controller.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/lib/python2.7/site-packages/pyface/action/tests/test_action_event.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/lib/python2.7/site-packages/pyface/action/tests/test_action_event.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/lib/python2.7/site-packages/pyface/action/tests/test_action_event.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/lib/python2.7/site-packages/pyface/action/tests/test_action_item.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/lib/python2.7/site-packages/pyface/action/tests/test_action_item.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/lib/python2.7/site-packages/pyface/action/tests/test_action_item.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/lib/python2.7/site-packages/pyface/action/tests/test_action_manager.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/lib/python2.7/site-packages/pyface/action/tests/test_action_manager.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/lib/python2.7/site-packages/pyface/action/tests/test_action_manager.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/lib/python2.7/site-packages/pyface/action/tests/test_group.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/lib/python2.7/site-packages/pyface/action/tests/test_group.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/lib/python2.7/site-packages/pyface/action/tests/test_group.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/lib/python2.7/site-packages/pyface/tasks/tests/test_action_manager_builder.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/lib/python2.7/site-packages/pyface/tasks/tests/test_action_manager_builder.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/lib/python2.7/site-packages/pyface/tasks/tests/test_action_manager_builder.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/lib/python2.7/site-packages/pyface/tasks/tests/test_dock_pane_toggle_group.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/lib/python2.7/site-packages/pyface/tasks/tests/test_dock_pane_toggle_group.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/lib/python2.7/site-packages/pyface/tasks/tests/test_dock_pane_toggle_group.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/lib/python2.7/site-packages/pyface/tasks/tests/test_editor_area_pane.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/lib/python2.7/site-packages/pyface/tasks/tests/test_editor_area_pane.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/lib/python2.7/site-packages/pyface/tasks/tests/test_editor_area_pane.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/lib/python2.7/site-packages/pyface/tasks/tests/test_enaml_dock_pane.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/lib/python2.7/site-packages/pyface/tasks/tests/test_enaml_dock_pane.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/lib/python2.7/site-packages/pyface/tasks/tests/test_enaml_dock_pane.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/lib/python2.7/site-packages/pyface/tasks/tests/test_enaml_editor.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/lib/python2.7/site-packages/pyface/tasks/tests/test_enaml_editor.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/lib/python2.7/site-packages/pyface/tasks/tests/test_enaml_editor.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/lib/python2.7/site-packages/pyface/tasks/tests/test_enaml_task_pane.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/lib/python2.7/site-packages/pyface/tasks/tests/test_enaml_task_pane.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/lib/python2.7/site-packages/pyface/tasks/tests/test_enaml_task_pane.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/lib/python2.7/site-packages/pyface/tasks/tests/test_task_layout.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/lib/python2.7/site-packages/pyface/tasks/tests/test_task_layout.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/lib/python2.7/site-packages/pyface/tasks/tests/test_task_layout.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/lib/python2.7/site-packages/pyface/tasks/tests/test_topological_sort.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/lib/python2.7/site-packages/pyface/tasks/tests/test_topological_sort.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/lib/python2.7/site-packages/pyface/tasks/tests/test_topological_sort.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/lib/python2.7/site-packages/pyface/ui/qt4/code_editor/tests/test_code_widget.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/lib/python2.7/site-packages/pyface/ui/qt4/code_editor/tests/test_code_widget.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/lib/python2.7/site-packages/pyface/ui/qt4/code_editor/tests/test_code_widget.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/lib/python2.7/site-packages/pyface/ui/qt4/tasks/tests/test_split_editor_area_pane.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/lib/python2.7/site-packages/pyface/ui/qt4/tasks/tests/test_split_editor_area_pane.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/lib/python2.7/site-packages/pyface/ui/qt4/tasks/tests/test_split_editor_area_pane.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/lib/python2.7/site-packages/pyface/ui/qt4/tests/test_progress_dialog.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/lib/python2.7/site-packages/pyface/ui/qt4/tests/test_progress_dialog.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/lib/python2.7/site-packages/pyface/ui/qt4/tests/test_progress_dialog.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/lib/python2.7/site-packages/pyface/ui/qt4/workbench/tests/test_workbench_window_layout.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/lib/python2.7/site-packages/pyface/ui/qt4/workbench/tests/test_workbench_window_layout.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/lib/python2.7/site-packages/pyface/ui/qt4/workbench/tests/test_workbench_window_layout.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/lib/python2.7/site-packages/pyface/workbench/tests/test_workbench_window.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/lib/python2.7/site-packages/pyface/workbench/tests/test_workbench_window.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/lib/python2.7/site-packages/pyface/workbench/tests/test_workbench_window.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.
@python python-module-pygsl-devel-2.2.0-alt1.noarch 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.
@python python-module-pygtk_git-devel-2.24.1-alt10.git20111002.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.
@python python-module-pymol-1.8.6.0-alt1.x86_64 altlinux-python-test-is-packaged experimental /usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/chempy/generate_amber.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/chempy/generate_amber.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/chempy/generate_amber.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/chempy/generate_mmff.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/chempy/generate_mmff.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/chempy/generate_mmff.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/area_diff.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/build_peptide.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/build_peptide.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/build_peptide.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/contact.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/dali.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/dali.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/dali.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/density.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/groel_es.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/multiclip_ray.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/packing.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/packsurf.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/ref_frame.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/ribosome.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/scenes2movie.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/seq_match_sele.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/ss_xfer.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/symsph.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/symsph.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/cookbook/symsph.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/brick01.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/brick01.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/brick01.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cam2crd.pym: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo01.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo01.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo01.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo02.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo02.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo02.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo03.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo03.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo03.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo04.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo04.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo04.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo05.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo05.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo05.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo06.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo06.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo06.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo07.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo07.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo07.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo08.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo08.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo08.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo_3Dtext01.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo_3Dtext01.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo_3Dtext01.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo_axes.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo_axes.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo_axes.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo_label_hack.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo_label_hack.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo_label_hack.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo_plane.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo_plane.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/cgo_plane.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/chempy_model01.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/chempy_model01.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/chempy_model01.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/chempy_model02.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/chempy_model02.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/chempy_model02.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/chempy_model03.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/chempy_model03.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/chempy_model03.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/click_ordered_list.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/click_ordered_list.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/click_ordered_list.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/count_molecules.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/count_molecules.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/count_molecules.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/demo.sdf: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/extend_demo01.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/extend_demo01.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/extend_demo01.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/gl01.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/gl01.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/gl01.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/gl02.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/gl02.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/gl02.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/gl03.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/gl03.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/gl03.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/hole_vmd_tri.pym: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/importing.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/importing.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/importing.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/link_demo.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/link_demo.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/link_demo.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/membrane.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/membrane.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/membrane.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/mutate01.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/mutate02.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/mutate02.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/mutate02.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/my_ext_gui.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/my_ext_gui.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/my_ext_gui.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/particle01.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/particle01.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/particle01.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/particle02.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/particle02.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/particle02.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/pick_wiz.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/pick_wiz.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/pick_wiz.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/povray01.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/povray01.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/povray01.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/scenes_to_movie01.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/sd_annotate.pml: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/sele_wiz.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/sele_wiz.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/sele_wiz.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/start_pymol.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/start_pymol.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/start_pymol.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/syncmol.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/syncmol.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/syncmol.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/tkwindow.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/tkwindow.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/tkwindow.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/webgui01.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/webgui01.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/webgui01.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/webgui02.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/webgui02.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/webgui02.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/xmlrpc01.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/xmlrpc01.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/xmlrpc01.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/xmlrpc02.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/xmlrpc02.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/devel/xmlrpc02.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/README: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch_demo.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch_demo.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch_demo.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch_no_tk.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch_no_tk.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch_no_tk.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch_viewer1.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch_viewer1.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch_viewer1.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch_viewer2.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch_viewer2.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/launching/launch_viewer2.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/package/redhat/pymol-0.93-1.rh62.py152.spec: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/package/redhat/pymol-0.93-1.rh70.py152.spec: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/package/redhat/pymol-0.93-1.rh72.py21.spec: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/package/redhat/pymol-0.93-1.rh73.py22.spec: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/package/redhat/pymol-0.93-1.rh80.py22.spec: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/package/redhat/pymol-0.93-1.rh90.py22.spec: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/package/redhat/pymol-0.96-1.rh62.py152.spec: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/package/redhat/pymol-0.96-1.rh70.py152.spec: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/package/redhat/pymol-0.96-1.rh72.py21.spec: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/package/redhat/pymol-0.96-1.rh73.py22.spec: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/package/redhat/pymol-0.96-1.rh80.py22.spec: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib64/python2.7/site-packages/pymol/pymol_path/examples/package/redhat/pymol-0.96-1.rh90.py22.spec: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
@python python-module-pysparse-1.3-alt1.git20130305.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.
@python python-module-rasterio-0.36.0-alt1.1.1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/bin/rio conflicts with the package plan9-wm-1.0-alt1.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.
@python python-module-repoze.debug-1.1-alt1.x86_64 altlinux-python-test-is-packaged info /usr/lib64/python2.7/site-packages/repoze/debug/scripts/tests/test_requestprofiler.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/site-packages/repoze/debug/scripts/tests/test_requestprofiler.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/site-packages/repoze/debug/scripts/tests/test_requestprofiler.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.
@python python-module-requests-facebook-0.4.0-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/lib/python2.7/site-packages/facebook.py /usr/lib/python2.7/site-packages/facebook.pyc /usr/lib/python2.7/site-packages/facebook.pyo conflict with the package python-module-facebook-ads-api-0.3.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.
Files /usr/lib/python2.7/site-packages/facebook.py /usr/lib/python2.7/site-packages/facebook.pyc /usr/lib/python2.7/site-packages/facebook.pyo conflict with the package python-module-geventhttpclient-facebook-0.4.4-alt1.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-robotsuite-2.0.0-alt1.1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/robotsuite/tests/test_example.robot: 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/lib/python2.7/site-packages/robotsuite/tests/test_robot.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/lib/python2.7/site-packages/robotsuite/tests/test_robot.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/lib/python2.7/site-packages/robotsuite/tests/test_robot.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/lib/python2.7/site-packages/robotsuite/tests/test_setups/__init__.robot: 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/lib/python2.7/site-packages/robotsuite/tests/test_setups/a.robot: 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/lib/python2.7/site-packages/robotsuite/tests/test_setups/b.robot: 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/lib/python2.7/site-packages/robotsuite/tests/test_setups/global_variable.robot: 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/lib/python2.7/site-packages/robotsuite/tests/test_variables.robot: 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.
@python python-module-servicemanager-0.0.16-alt1.git20141007.1.noarch rpm-filesystem-conflict-file-file warn File /usr/bin/sm conflicts with the package inn-2.4.5-alt6.1.1.1.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.
File /usr/bin/sm conflicts with the package screen-message-0.6-alt1.qa1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-setuptools-39.0.1-alt2.S1.src 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.
@python python-module-spec-1.4.0-alt1.1.noarch rpm-filesystem-conflict-file-file warn File /usr/bin/spec conflicts with the package iceb-18.5-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-sphinx-bootstrap-theme-0.6.0-alt2.src 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.
@python python-module-sqlalchemy_monetdb-1.0.0-alt1.1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/test/test_doc.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/lib/python2.7/site-packages/test/test_doc.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/lib/python2.7/site-packages/test/test_doc.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/lib/python2.7/site-packages/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/lib/python2.7/site-packages/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/lib/python2.7/site-packages/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.
@python python-module-sqlalchemy_monetdb-1.0.0-alt1.1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python2.7/site-packages/test/__init__.py conflicts with the package python-module-phonon-2.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.
@python python-module-theano-0.6.0-alt4.src 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.
@python python-module-toolz-0.8.2-alt1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/toolz/tests/test_compatibility.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/lib/python2.7/site-packages/toolz/tests/test_compatibility.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/lib/python2.7/site-packages/toolz/tests/test_compatibility.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/lib/python2.7/site-packages/toolz/tests/test_curried.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/lib/python2.7/site-packages/toolz/tests/test_curried.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/lib/python2.7/site-packages/toolz/tests/test_curried.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/lib/python2.7/site-packages/toolz/tests/test_curried_doctests.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/lib/python2.7/site-packages/toolz/tests/test_curried_doctests.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/lib/python2.7/site-packages/toolz/tests/test_curried_doctests.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/lib/python2.7/site-packages/toolz/tests/test_dicttoolz.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/lib/python2.7/site-packages/toolz/tests/test_dicttoolz.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/lib/python2.7/site-packages/toolz/tests/test_dicttoolz.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/lib/python2.7/site-packages/toolz/tests/test_functoolz.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/lib/python2.7/site-packages/toolz/tests/test_functoolz.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/lib/python2.7/site-packages/toolz/tests/test_functoolz.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/lib/python2.7/site-packages/toolz/tests/test_inspect_args.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/lib/python2.7/site-packages/toolz/tests/test_inspect_args.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/lib/python2.7/site-packages/toolz/tests/test_inspect_args.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/lib/python2.7/site-packages/toolz/tests/test_itertoolz.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/lib/python2.7/site-packages/toolz/tests/test_itertoolz.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/lib/python2.7/site-packages/toolz/tests/test_itertoolz.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/lib/python2.7/site-packages/toolz/tests/test_recipes.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/lib/python2.7/site-packages/toolz/tests/test_recipes.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/lib/python2.7/site-packages/toolz/tests/test_recipes.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/lib/python2.7/site-packages/toolz/tests/test_serialization.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/lib/python2.7/site-packages/toolz/tests/test_serialization.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/lib/python2.7/site-packages/toolz/tests/test_serialization.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/lib/python2.7/site-packages/toolz/tests/test_signatures.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/lib/python2.7/site-packages/toolz/tests/test_signatures.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/lib/python2.7/site-packages/toolz/tests/test_signatures.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/lib/python2.7/site-packages/toolz/tests/test_tlz.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/lib/python2.7/site-packages/toolz/tests/test_tlz.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/lib/python2.7/site-packages/toolz/tests/test_tlz.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/lib/python2.7/site-packages/toolz/tests/test_utils.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/lib/python2.7/site-packages/toolz/tests/test_utils.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/lib/python2.7/site-packages/toolz/tests/test_utils.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.
@python python-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.1.noarch rpm-filesystem-conflict-file-file warn Files /usr/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-facebook-2.3.14-alt1.git20140409.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/lib/python2.7/site-packages/facebook/__init__.py /usr/lib/python2.7/site-packages/facebook/__init__.pyc /usr/lib/python2.7/site-packages/facebook/__init__.pyo conflict with the package python-module-facebook_api-0.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-unittest2-1.1.0-alt3.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/test/test_new_tests.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/lib/python2.7/site-packages/unittest2/test/test_new_tests.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/lib/python2.7/site-packages/unittest2/test/test_new_tests.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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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/lib/python2.7/site-packages/unittest2/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.
/usr/lib/python2.7/site-packages/unittest2/test/test_unittest2_with.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/lib/python2.7/site-packages/unittest2/test/test_unittest2_with.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/lib/python2.7/site-packages/unittest2/test/test_unittest2_with.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.
@python python-module-xstatic-1.0.1-alt2.1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-html5shiv-3.6.1-alt3.1.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 /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-less-1.3.0.1-alt3.1.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 /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-socialshareprivacy-1.4.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-xstatic-html5shiv-3.6.1-alt3.1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-1.0.1-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-xstatic-less-1.3.0.1-alt3.1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-1.0.1-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-xstatic-socialshareprivacy-1.4.1-alt3.1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python2.7/site-packages/xstatic/pkg/__init__.py conflicts with the package python-module-xstatic-1.0.1-alt2.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python-module-xstatic-svg-edit-moin-2012.11.27.1-alt2.1.noarch altlinux-python-test-is-packaged experimental /usr/lib/python2.7/site-packages/xstatic/pkg/svgedit_moin/data/examples/arbelos.svg: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/xstatic/pkg/svgedit_moin/data/examples/mickey.svg: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
@python python-module-zc-zookeeper-static-3.4.4.1-alt1.git20120925.1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/lib64/python2.7/site-packages/zookeeper.so conflicts with the package python-module-zookeeper-3.4.9-alt1_7jpp8.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.
@python python-module-zconfig-3.2.0-alt1.1.src 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.
@python python-module-zest.releaser-6.12.2-alt1.1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/bin/release conflicts with the package perl-Module-Release-scripts-2.125-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.
@python python-module-zope.i18nmessageid-4.1.0-alt1.S1.1.src 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.
@python python3-module-aiodns-1.1.1-alt1.noarch missing-url info Missing Url: in a package.
@python python3-module-apiclient-1.0.3-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python3/site-packages/apiclient/__init__.py conflicts with the package python3-module-google-api-client-1.6.7-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.
@python python3-module-django-admin-tools-0.8.0-alt1.noarch buildroot fail found paths to buildroot: /usr/share/doc/python3-module-django-admin-tools-0.8.0/docs/_build/doctrees/dashboard.doctree: Binary file /usr/share/doc/python3-module-django-admin-tools-0.8.0/docs/_build/doctrees/dashboard.doctree matches /usr/share/doc/python3-module-django-admin-tools-0.8.0/docs/_build/doctrees/menu.doctree: Binary file /usr/share/doc/python3-module-django-admin-tools-0.8.0/docs/_build/doctrees/menu.doctree matches
@python python3-module-django-facebook-utils-1.0.4-alt1.git20130201.1.1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python3/site-packages/facebook_utils/__init__.py conflicts with the package python3-module-facebook_utils-0.20.3-alt1.git20140717.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python3-module-django-uni-form-0.9.0-alt2.2.noarch macos-ds-store-file-in-package warn There is a file in the package named .DS_Store or .DS_Store.gz, the file name used by Mac OS X to store folder attributes. Such files are generally useless in packages and were usually accidentally included by copying complete directories from the source tarball.
@python python3-module-facebook-2.3.14-alt1.git20140409.1.1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python3-module-facebook_api-0.1.4-alt1.1.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (4 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.
File /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python3-module-facebook-ads-api-0.3.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python3/site-packages/facebook.py conflicts with the package python3-module-geventhttpclient-facebook-0.4.4-alt1.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package python3-module-requests-facebook-0.4.0-alt1.noarch, for example, /usr/lib/python3/site-packages/__pycache__/facebook.cpython-35.opt-1.pyc (4 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.
@python python3-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.1.1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-facebook_api-0.1.4-alt1.1.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 /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python3-module-facebook_api-0.1.4-alt1.1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python3-module-facebook-2.3.14-alt1.git20140409.1.1.noarch, for example, /usr/lib/python3/site-packages/facebook/__init__.py (4 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.
File /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.1.1.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 /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python3-module-facebook_utils-0.20.3-alt1.git20140717.1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python3/site-packages/facebook_utils/__init__.py conflicts with the package python3-module-django-facebook-utils-1.0.4-alt1.git20130201.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python3-module-geventhttpclient-facebook-0.4.4-alt1.1.1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python3/site-packages/facebook.py conflicts with the package python3-module-facebook-ads-api-0.3.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 /usr/lib/python3/site-packages/facebook.py conflicts with the package python3-module-requests-facebook-0.4.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.
@python python3-module-google-api-client-1.6.7-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python3/site-packages/apiclient/__init__.py conflicts with the package python3-module-apiclient-1.0.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.
@python python3-module-js.jquery-1.9.1-alt1.1.1.1.1.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/lib64/python3/site-packages/js/jquery/__pycache__/__init__.cpython-35.opt-1.pyc /usr/lib64/python3/site-packages/js/jquery/__pycache__/__init__.cpython-35.opt-2.pyc conflict with the package python3-module-js.query-1.9.2-alt1.dev0.hg20130303.1.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.
@python python3-module-js.query-1.9.2-alt1.dev0.hg20130303.1.1.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/lib64/python3/site-packages/js/jquery/__pycache__/__init__.cpython-35.opt-1.pyc /usr/lib64/python3/site-packages/js/jquery/__pycache__/__init__.cpython-35.opt-2.pyc conflict with the package python3-module-js.jquery-1.9.1-alt1.1.1.1.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.
@python python3-module-phonon-2.0-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python3-module-sqlalchemy_monetdb-1.0.0-alt1.1.noarch, for example, /usr/lib/python3/site-packages/test/__init__.py (4 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.
@python python3-module-py3k-bcrypt-0.3-alt1.git20120906.1.1.1.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package python3-module-bcrypt-3.1.4-alt1.1.x86_64, for example, /usr/lib64/python3/site-packages/bcrypt/__init__.py (4 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.
@python python3-module-requests-facebook-0.4.0-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python3-module-facebook-ads-api-0.3.0-alt1.noarch, for example, /usr/lib/python3/site-packages/__pycache__/facebook.cpython-35.opt-1.pyc (4 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.
File /usr/lib/python3/site-packages/facebook.py conflicts with the package python3-module-geventhttpclient-facebook-0.4.4-alt1.1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
@python python3-module-simpleparse-docs-3.0.0-alt1.a1.bzr20140102.1.noarch buildroot fail found paths to buildroot: /usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.simpleparsegrammar.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/simpleparsegrammar.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.common.strings.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/common/strings.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.printers.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/printers.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.xmlparser.__init__.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/xmlparser/__init__.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.boyermoore.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/boyermoore.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/__init__.py

__path__ = ['/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse']
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.common.iso_date_loose.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/common/iso_date_loose.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.error.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/error.py

__file__ = '/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/error.py'
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.objectgenerator.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/objectgenerator.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.common.calendar_names.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/common/calendar_names.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.__init__.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/__init__.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.common.chartypes.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/common/chartypes.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.baseparser.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/baseparser.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.common.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/common/__init__.py

__path__ = ['/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/common'] /usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.common.comments.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/common/comments.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.common.__init__.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/common/__init__.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.common.phonetics.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/common/phonetics.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.common.timezone_names.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/common/timezone_names.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.xmlparser.xml_parser.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/xmlparser/xml_parser.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.common.numbers.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/common/numbers.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.dispatchprocessor.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/dispatchprocessor.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.generator.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/generator.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.parser.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/parser.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.xmlparser.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/xmlparser/__init__.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.common.iso_date.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/common/iso_date.py
/usr/share/doc/python3-module-simpleparse-docs-3.0.0/pydoc/simpleparse.processor.html: >index
/usr/src/tmp/python3-module-simpleparse-buildroot/usr/lib/python3/site-packages/simpleparse/processor.py
@python python3-module-sqlalchemy_monetdb-1.0.0-alt1.1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python3-module-phonon-2.0-alt1.noarch, for example, /usr/lib/python3/site-packages/test/__init__.py (4 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. @python python3-module-tornado-facebook-sdk-0.1.0-alt1.git20121001.1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-facebook-2.3.14-alt1.git20140409.1.1.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 /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-facebook-sdk-1.0.0-alt1.alpha.git20140828.1.1.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 /usr/lib/python3/site-packages/facebook/__init__.py conflicts with the package python3-module-facebook_api-0.1.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. @python python3-module-xstatic-1.0.1-alt2.1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python3-module-xstatic-html5shiv-3.6.1-alt3.1.noarch, for example, /usr/lib/python3/site-packages/xstatic/pkg/__init__.py (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package python3-module-xstatic-less-1.3.0.1-alt3.1.noarch, for example, /usr/lib/python3/site-packages/xstatic/pkg/__init__.py (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package python3-module-xstatic-socialshareprivacy-1.4.1-alt3.1.noarch, for example, /usr/lib/python3/site-packages/xstatic/pkg/__init__.py (4 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. @python python3-module-xstatic-html5shiv-3.6.1-alt3.1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python3-module-xstatic-1.0.1-alt2.1.noarch, for example, /usr/lib/python3/site-packages/xstatic/pkg/__init__.py (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.opt-1.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.opt-2.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.pyc conflict with the package python3-module-xstatic-less-1.3.0.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.opt-1.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.opt-2.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.pyc conflict with the package python3-module-xstatic-socialshareprivacy-1.4.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. @python python3-module-xstatic-less-1.3.0.1-alt3.1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python3-module-xstatic-1.0.1-alt2.1.noarch, for example, /usr/lib/python3/site-packages/xstatic/pkg/__init__.py (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.opt-1.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.opt-2.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.pyc conflict with the package python3-module-xstatic-html5shiv-3.6.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.opt-1.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.opt-2.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.pyc conflict with the package python3-module-xstatic-socialshareprivacy-1.4.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. @python python3-module-xstatic-socialshareprivacy-1.4.1-alt3.1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python3-module-xstatic-1.0.1-alt2.1.noarch, for example, /usr/lib/python3/site-packages/xstatic/pkg/__init__.py (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.opt-1.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.opt-2.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.pyc conflict with the package python3-module-xstatic-html5shiv-3.6.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.opt-1.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.opt-2.pyc /usr/lib/python3/site-packages/xstatic/pkg/__pycache__/__init__.cpython-35.pyc conflict with the package python3-module-xstatic-less-1.3.0.1-alt3.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. @python tuxpaint-0.9.22-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. @python yaws-server-1.92-alt1.noarch init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. @ruby ruby-makeconf-doc-0.3.0-alt1.svn20130509.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-httpclient-doc-2.8.2.4-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-iconv-1.0.5-alt1.2.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.
Files /usr/share/ri/site/Installer/cdesc-Installer.ri /usr/share/ri/site/Installer/new-c.ri conflict with the package ruby-idn-doc-0.1.0-alt3.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/cache.ri /usr/share/ri/site/created.rid conflict with the package ruby-parseconfig-doc-0.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Installer/cdesc-Installer.ri /usr/share/ri/site/Installer/new-c.ri conflict with the package ruby-sigar-doc-0.7.3-alt1.4.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. @sugar olpcsound-5.10.1-alt3.1.2.x86_64 big-changelog info Package contains big ChangeLog. Gzip it. aas exim-common-4.90.1-alt1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it. aas exim-common-4.90.1-alt1.x86_64 init-lsb warn /etc/rc.d/init.d/exim: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. aas exim-common-4.90.1-alt1.x86_64 rpm-filesystem-conflict-symlink-file warn symlink /usr/sbin/sendmail is a file in the package sendmail-submit-8.15.2-alt5.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.
symlink /usr/sbin/sendmail is a file in the package postfix-2.11.11-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. aas exim-common-4.90.1-alt1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /etc/aliases is different from the same symlink in the package postfix-2.11.11-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/sbin/sendmail is different from the same symlink in the package msmtp-sendmail-1.6.6-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. aas exim-monitor-4.90.1-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/eximon.desktop: warning: value "Exim Monitor" for key "Comment" in group "Desktop Entry" looks redundant with value "Exim Monitor" of key "Name" ab libwbclient-4.7.7-alt1.S1.x86_64 alt-alternatives-vs-ghost info Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.14 is an alternative in package libwbclient-4.7.7-alt1.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.14.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-4.7.7-alt1.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.14 is an alternative in package libwbclient-DC-4.7.7-alt1.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.14.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-DC-4.7.7-alt1.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-sssd-1.16.1-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0. ab libwbclient-debuginfo-4.7.7-alt1.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.14.debug is different from the same symlink in the package libwbclient-DC-debuginfo-4.7.7-alt1.S1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-DC-debuginfo-4.7.7-alt1.S1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-sssd-debuginfo-1.16.1-alt5.S1.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. ab libwbclient-devel-4.7.7-alt1.S1.x86_64 alt-alternatives-vs-ghost info Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-DC-devel-4.7.7-alt1.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-devel-4.7.7-alt1.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-sssd-devel-1.16.1-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so. ab samba-client-libs-4.7.7-alt1.S1.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 ab samba-common-4.7.7-alt1.S1.noarch 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. ab samba-winbind-clients-4.7.7-alt1.S1.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libnss_winbind.so but just /usr/lib64/libnss_winbind.so.2. According to SharedLibs Policy Draft, symlink /usr/lib64/libnss_winbind.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libnss_winbind.so to \%files of samba-winbind-clients-4.7.7-alt1.S1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libnss_wins.so but just /usr/lib64/libnss_wins.so.2. According to SharedLibs Policy Draft, symlink /usr/lib64/libnss_wins.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libnss_wins.so to \%files of samba-winbind-clients-4.7.7-alt1.S1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test. ab samba-winbind-clients-4.7.7-alt1.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /lib64/libnss_winbind.so.2 is different from the same symlink in the package samba-DC-winbind-clients-4.7.7-alt1.S1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /lib64/libnss_wins.so.2 is different from the same symlink in the package samba-DC-winbind-clients-4.7.7-alt1.S1.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. ach plastex-0.9.2-alt1.1.src 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. akv cherrytree-0.38.2-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/cherrytree.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). akv cherrytree-0.38.2-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/cherrytree.desktop: hint: value "Office;GNOME;GTK;Utility;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu akv cherrytree-0.38.2-alt1.src 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. akv compton-0.1_beta2_1-alt3.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/compton-trans akv compton-0.1_beta2_1-alt3.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/compton.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). akv kde5-krusader-2.7.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. akv kde5-krusader-2.7.0-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/kf5/applications/kf5/org.kde.krusader.desktop: hint: value item "FileManager" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: System;FileTools akv libbcg729-0.1-alt2.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libbcg729.so but just /usr/lib64/libbcg729.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libbcg729.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libbcg729.so to \%files of libbcg729-0.1-alt2.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test. akv libbcg729-0.1-alt2.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 akv libbcg729-devel-0.1-alt2.x86_64 rpm-filesystem-conflict-file-file warn File /usr/include/utils.h conflicts with the package libcdparanoia-devel-10.2-alt6.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. akv libta-lib-0.4.0-alt2.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libta_lib.so but just /usr/lib64/libta_lib.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libta_lib.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libta_lib.so to \%files of libta-lib-0.4.0-alt2.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test. akv libta-lib-0.4.0-alt2.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 akv python-module-telebot-3.2.0-alt1.noarch rpm-obsolete-live-package info The package obsoletes the package python-module-pytelegrambotapi-3.2.0-alt1.noarch, but the package python-module-pytelegrambotapi-3.2.0-alt1.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. akv python3-module-telebot-3.2.0-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package python3-module-pytelegrambotapi-3.2.0-alt1.noarch, for example, /usr/lib/python3/site-packages/pyTelegramBotAPI-3.1.1-py3.5.egg-info/PKG-INFO (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. akv pywinery-0.3.2-alt1.noarch freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/pywinery.desktop: error: value "Wine;Applications;GTK;System;Emulator;" for key "Categories" in group "Desktop Entry" contains an unregistered value "Wine"; values extending the format should start with "X-"
/usr/share/applications/pywinery.desktop: warning: value "Wine;Applications;GTK;System;Emulator;" for key "Categories" in group "Desktop Entry" contains a deprecated value "Applications" akv pywinery-0.3.2-alt1.src 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. akv qownnotes-17.06.6-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/QOwnNotes.desktop: hint: value "Office;Utility;TextTools;TextEditor;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu akv rkward-0.6.5-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. akv roxterm-3.1.4-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/roxterm.desktop: hint: value "GTK;Utility;TerminalEmulator;System;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu akv sakura-3.5.0-alt2.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. akv synapse-0.2.99.2-alt2.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/synapse.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). akv synapse-0.2.99.2-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/synapse.desktop: hint: value item "GNOME" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: GTK akv synapse-0.2.99.2-alt2.x86_64 obsolete-call-in-post-gtk-update-icon-cache warn gtk-update-icon-cache call in post/postun is deprecated akv unibilium-1.2.0-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 akv vkplayer-0.08.16-alt5.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/vkplayer.desktop: warning: boolean key "Terminal" in group "Desktop Entry" has value "0", which is deprecated: boolean values should be "false" or "true"
/usr/share/applications/vkplayer.desktop: error: value "AudioVideo;Internet;Player;Qt;" for key "Categories" in group "Desktop Entry" contains an unregistered value "Internet"; values extending the format should start with "X-" akv wxGlade-0.7.2-alt1.noarch freedesktop-categories fail Main Categories consist of those categories that every conforming desktop environment MUST support.(http://standards.freedesktop.org/menu-spec/latest/apa.html). None found in /usr/share/applications/wxGlade.desktop. please, fix. akv wxGlade-0.7.2-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/wxGlade.desktop: hint: value item "GUIDesigner" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Development
/usr/share/applications/wxGlade.desktop: hint: value "X-MandrivaLinux-MoreApplications-Development-Tools;GUIDesigner;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu akv wxGlade-0.7.2-alt1.src 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. alb gtkevemon-1.8-alt2.qa2.1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. alecs qamix-0.0.7-alt3.1.src requires-ImageMagick info Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell. alexey cbp2make-147-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. alexey fachoda-2.1-alt3.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/fachoda.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). alexey fachoda-2.1-alt3.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/fachoda.desktop: error: value "2.1" for key "Version" in group "Desktop Entry" is not a known version alexey visualboyadvance-m-2.0.1-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. alexsid jabber-muc-0.8-alt0.3.r51.qa1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. alexsid jabber-muc-0.8-alt0.3.r51.qa1.x86_64 init-lsb fail /etc/rc.d/init.d/jabber-muc: not systemd compatible: lsb init header missing and jabber-muc.service is not present. See http://www.altlinux.org/Services_Policy for details. alexsid jabber-muc-0.8-alt0.3.r51.qa1.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. alexsid jabberd2-jud-1.2-alt5.noarch init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. alexsid jabberd2-jud-1.2-alt5.noarch init-lsb fail /etc/rc.d/init.d/jabberd2-jud: not systemd compatible: lsb init header missing and jabberd2-jud.service is not present. See http://www.altlinux.org/Services_Policy for details. alexsid jabberd2-jud-1.2-alt5.noarch missing-url info Missing Url: in a package. alexvm nspec-15.5547-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/nspec.desktop: hint: value "Science;Physics;Education;Engineering;DataVisualization;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu alexvm nspec-15.5547-alt2.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. alexvm nspec-15.5547-alt2.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/99-nst.rules to \%_udevrulesdir/. ali qtspim-9.1.7-alt1.r598.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/qtspim.desktop: error: value "9.1.7" for key "Version" in group "Desktop Entry" is not a known version ali stellarium-0.16.1-alt1.S1.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. ali stellarium-0.16.1-alt1.S1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/stellarium.desktop: hint: value "Astronomy;Education;Science;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
/usr/share/applications/stellarium.desktop: warning: value "Planet?rio" for key "Comment[pt]" in group "Desktop Entry" looks redundant with value "Planet?rio" of key "GenericName[pt]" amike libtag-extras-1.0.1-alt4.src specfile-macros-get_dep-is-deprecated experimental Versioned Requires: foo >= %{get_dep something} using %get_dep and %get_version macros on a library are deprecated by set:versions. You probably should drop %get_dep/%get_version Requires: to avoid RPM database pollution. amike libtag-extras-1.0.1-alt4.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libtag-extras.so but just /usr/lib64/libtag-extras.so.1.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libtag-extras.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libtag-extras.so to \%files of libtag-extras-1.0.1-alt4.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test. antohami CanFestival-3-source-2015.08.03-alt1.noarch unsafe-tmp-usage-in-scripts fail 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/src/CanFestival-3/configure: $ grep -A5 -B5 /tmp/ /usr/src/CanFestival-3/configure ########################################################################### if [ "$SUB_WX" = "" ]; then if which wx-config >/dev/null 2>&1; then echo -n "Testing wxWidgets compiles ... " cat > /tmp/wx_test.cpp </dev/null 2>&1 ; then SUB_WX=1 echo "Yes" else SUB_WX=0 echo "No" fi rm -f /tmp/wx_test* else SUB_WX=0 echo "No wxWidgets available" fi fi antohami ConsoleKit2-1.2.1-alt1.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts. antohami OpenBoard-1.3.6-alt2.S1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. antohami arm-none-eabi-binutils-2.30-alt1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it. antohami arm-none-eabi-gcc-7.3.1-alt2.x86_64 uncompressed-manpages info Package contains uncompressed manual pages. antohami arm-none-eabi-gcc-c++-7.3.1-alt2.x86_64 uncompressed-manpages info Package contains uncompressed manual pages. antohami bladerf-1.8.0-alt2.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 antohami caffeine-ng-3.4.0-alt3.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/caffeine.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). antohami caffeine-ng-3.4.0-alt3.noarch freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/caffeine.desktop: error: value item "TrayIcon" in key "Categories" in group "Desktop Entry" is a reserved category, so a "OnlyShowIn" key must be included
/usr/share/applications/caffeine.desktop: error: value "Utility;TrayIcon;DesktopUtility;" for key "Categories" in group "Desktop Entry" contains an unregistered value "DesktopUtility"; values extending the format should start with "X-" antohami chirp-20171104-alt1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. antohami converseen-0.9.6.2-alt2.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/converseen.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). antohami cpu-x-3.2.2-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/cpu-x.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt).
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/cpu-x-root.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). antohami cura-3.3.0-alt1.S1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/cura.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). antohami deadbeef-0.7.1-alt4.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/deadbeef.desktop: error: file contains group "Play Shortcut Group", but groups extending the format should start with "X-"
/usr/share/applications/deadbeef.desktop: error: file contains group "Pause Shortcut Group", but groups extending the format should start with "X-"
/usr/share/applications/deadbeef.desktop: error: file contains group "Stop Shortcut Group", but groups extending the format should start with "X-"
/usr/share/applications/deadbeef.desktop: error: file contains group "Next Shortcut Group", but groups extending the format should start with "X-"
/usr/share/applications/deadbeef.desktop: error: file contains group "Prev Shortcut Group", but groups extending the format should start with "X-"
/usr/share/applications/deadbeef.desktop: error: action group "Desktop Action Previous" exists, but there is no matching action "Previous"
/usr/share/applications/deadbeef.desktop: error: action group "Desktop Action Pause" exists, but there is no matching action "Pause"
/usr/share/applications/deadbeef.desktop: error: action group "Desktop Action Play" exists, but there is no matching action "Play"
/usr/share/applications/deadbeef.desktop: error: action group "Desktop Action Next" exists, but there is no matching action "Next"
/usr/share/applications/deadbeef.desktop: error: action group "Desktop Action Stop" exists, but there is no matching action "Stop" antohami faust2appls-0.9.90-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/faust2au antohami firetools-0.9.52-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/firejail-ui.desktop: warning: value "Firejail configuration wizard" for key "Comment" in group "Desktop Entry" looks redundant with value "Firejail Configuration Wizard" of key "Name"
/usr/share/applications/firejail-ui.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 antohami firetools-0.9.52-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. antohami gnuradio-3.7.12.0-alt1.x86_64 bin-permissions info not executable file /usr/bin/gr-ctrlport-monitorc
not executable file /usr/bin/gr-ctrlport-monitoro
not executable file /usr/bin/gr-perf-monitorxc
not executable file /usr/bin/gr-perf-monitorxo antohami gnuradio-3.7.12.0-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/gnuradio-grc.desktop: hint: value item "HamRadio" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Network, or Audio
/usr/share/applications/gnuradio-grc.desktop: hint: value "Development;HamRadio;Science;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu antohami gpredict-2.2.1-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. antohami gpredict-2.2.1-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/gpredict.desktop: hint: value "HamRadio;Science;Astronomy;Education;Network;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
/usr/share/applications/gpredict.desktop: hint: value "HamRadio;Science;Astronomy;Education;Network;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu antohami gpredict-2.2.1-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. antohami gr-osmosdr-0.1.4-alt3.20170612.S1.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 antohami green-recorder-3.1-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/green-recorder.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). antohami green-recorder-3.1-alt1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. antohami guitarix-0.36.1-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. antohami guitarix-0.36.1-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. antohami hackrf-2018.01.1-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 antohami i-nex-7.6.0-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/i-nex.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt).
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/i-nex-library.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). antohami i-nex-7.6.0-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/i-nex.desktop: hint: value "System;Utility;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
desktop-file-validate utility printed the following message(s): /usr/share/applications/i-nex-library.desktop: hint: value "System;Utility;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu antohami image-analyzer-3.1.0-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/image-analyzer.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). antohami image-analyzer-3.1.0-alt1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. antohami itpp-doc-4.3.1-alt1.S1.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. antohami kazam-1.4.5-alt2.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/kazam.desktop: hint: value item "GNOME" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: GTK
/usr/share/applications/kazam.desktop: warning: key "OnlyShowIn" in group "Desktop Action SSF" is deprecated
/usr/share/applications/kazam.desktop: warning: key "OnlyShowIn" in group "Desktop Action SSA" is deprecated
/usr/share/applications/kazam.desktop: warning: key "OnlyShowIn" in group "Desktop Action SSW" is deprecated
/usr/share/applications/kazam.desktop: warning: key "OnlyShowIn" in group "Desktop Action Prefs" is deprecated antohami kicad-4.0.7-alt2.x86_64 bin-permissions info not executable file /usr/bin/_cvpcb.kiface
not executable file /usr/bin/_eeschema.kiface
not executable file /usr/bin/_gerbview.kiface
not executable file /usr/bin/_pcb_calculator.kiface
not executable file /usr/bin/_pcbnew.kiface
not executable file /usr/bin/_pl_editor.kiface antohami kicad-4.0.7-alt2.x86_64 freedesktop-desktop-file-proposed-patch warn Please, apply the repocop patch for /usr/share/applications/kicad.desktop.
Please, apply the repocop patch for /usr/share/applications/eeschema.desktop. antohami libquazip-devel-0.7.3-alt1.x86_64 rpm-filesystem-conflict-symlink-file warn symlink /usr/lib64/libquazip.so is a file in the package qcad-3.20.1.3-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. antohami linuxcnc-2.7.13-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. antohami linuxcnc-2.7.13-alt1.x86_64 init-condrestart warn /etc/rc.d/init.d/realtime: missing condrestart target. Note: alt-specific script %_sbindir/post_service (used in %post_service macro) depends on condrestart. It is wise to add condrestart anyway./etc/rc.d/init.d/realtime: missing condstop target. Note: alt-specific script %_sbindir/preun_service (used in %preun_service macro) depends on condstop. It is wise to add condstop anyway. antohami linuxcnc-2.7.13-alt1.x86_64 init-lsb warn /etc/rc.d/init.d/realtime: strange executable: neither lsb header nor chkconfig header aren't found. See http://www.altlinux.org/Services_Policy for details. antohami lxqt-about-0.12.0-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-about.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-" antohami lxqt-config-0.12.0-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-config-appearance.desktop: error: value "Settings;DesktopSettings;Qt;LXQt;" for key "Categories" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-appearance.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-config-locale.desktop: error: value "Settings;DesktopSettings;Qt;LXQt;" for key "Categories" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-locale.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-config.desktop: error: value "Settings;DesktopSettings;Qt;LXQt;" for key "Categories" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-config-brightness.desktop: error: value "Settings;DesktopSettings;Qt;LXQt;HardwareSettings;" for key "Categories" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-brightness.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-config-monitor.desktop: error: value "Settings;DesktopSettings;Qt;LXQt;HardwareSettings;" for key "Categories" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-monitor.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-monitor.desktop: warning: value "???????" for key "Comment[ja]" in group "Desktop Entry" looks redundant with value "???????" of key "Name[ja]"
desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-config-file-associations.desktop: error: value "Settings;DesktopSettings;Qt;LXQt;" for key "Categories" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-file-associations.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-config-input.desktop: error: value "Qt;Settings;HardwareSettings;DesktopSettings;LXQt;" for key "Categories" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-input.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-" antohami lxqt-globalkeys-0.12.0-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-config-globalkeyshortcuts.desktop: error: value "Settings;DesktopSettings;Qt;LXQt;" for key "Categories" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-globalkeyshortcuts.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-" antohami lxqt-globalkeys-0.12.0-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 antohami lxqt-notificationd-0.12.0-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-config-notificationd.desktop: error: value "Settings;DesktopSettings;Qt;LXQt;" for key "Categories" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-notificationd.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-notificationd.desktop: warning: value "Param?trage des notifications du bureau LXQt" for key "Comment[fr]" in group "Desktop Entry" looks redundant with value "Param?trage des notifications du bureau LXQt" of key "GenericName[fr]" antohami lxqt-powermanagement-0.12.0-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-config-powermanagement.desktop: error: value "Settings;DesktopSettings;Qt;LXQt;" for key "Categories" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-powermanagement.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-powermanagement.desktop: warning: value "LXQt energiakezel?s be?ll?t?sa" for key "Comment[hu]" in group "Desktop Entry" looks redundant with value "LXQt energiakezel?s be?ll?t?sa" of key "GenericName[hu]"
/usr/share/applications/lxqt-config-powermanagement.desktop: warning: value "???????" for key "Comment[ja]" in group "Desktop Entry" looks redundant with value "???????" of key "GenericName[ja]"
/usr/share/applications/lxqt-config-powermanagement.desktop: warning: value "Konfiguracja zarz?dzania energi?" for key "Comment[pl]" in group "Desktop Entry" looks redundant with value "Konfiguracja zarz?dzania energi?" of key "GenericName[pl]"
/usr/share/applications/lxqt-config-powermanagement.desktop: warning: value "Defini??es do gestor de energia" for key "Comment[pt]" in group "Desktop Entry" looks redundant with value "Defini??es do gestor de energia" of key "GenericName[pt]"
/usr/share/applications/lxqt-config-powermanagement.desktop: warning: value "????????? ?????????? ??????????????????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "????????? ?????????? ??????????????????" of key "GenericName[ru]" antohami lxqt-session-0.12.0-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-leave.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-shutdown.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-suspend.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-reboot.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-hibernate.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-lockscreen.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-config-session.desktop: error: value "Settings;DesktopSettings;Qt;LXQt;" for key "Categories" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-session.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-"
/usr/share/applications/lxqt-config-session.desktop: warning: value "Ustawienia sesji LXQt" for key "Comment[pl]" in group "Desktop Entry" looks redundant with value "Ustawienia sesji LXQt" of key "Name[pl]"
/usr/share/applications/lxqt-config-session.desktop: warning: value "Nastavenie rel?cie prostredia LXQt" for key "Comment[sk]" in group "Desktop Entry" looks redundant with value "Nastavenie rel?cie prostredia LXQt" of key "GenericName[sk]"
desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lxqt-logout.desktop: error: value "LXQt;" for key "OnlyShowIn" in group "Desktop Entry" contains an unregistered value "LXQt"; values extending the format should start with "X-" antohami meshlab-2016.12-alt1.S1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. antohami mpir-3.0.0-alt1.S1.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 antohami ngspice-data-27-alt1.noarch big-changelog info Package contains big ChangeLog. Gzip it. antohami nm-sysvinit-0.2-alt1.noarch init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. antohami nm-sysvinit-0.2-alt1.noarch init-condrestart warn /etc/rc.d/init.d/nm-group: missing condrestart target. Note: alt-specific script %_sbindir/post_service (used in %post_service macro) depends on condrestart. It is wise to add condrestart anyway./etc/rc.d/init.d/nm-group: missing condstop target. Note: alt-specific script %_sbindir/preun_service (used in %preun_service macro) depends on condstop. It is wise to add condstop anyway. antohami openscada-Archive.DBArch-0.8.19-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. antohami openscada-Archive.FSArch-0.8.19-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. antohami openscada-DAQ.BFN-0.8.19-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. antohami openscada-DAQ.BlockCalc-0.8.19-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. antohami openscada-DAQ.DAQGate-0.8.19-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. antohami openscada-DAQ.DCON-0.8.19-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. antohami openscada-DAQ.JavaLikeCalc-0.8.19-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. antohami openscada-DAQ.LogicLev-0.8.19-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. antohami openscada-DAQ.ModBus-0.8.19-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. antohami openscada-DAQ.OPC_UA-0.8.19-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. antohami openscada-DAQ.SNMP-0.8.19-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. antohami openscada-DAQ.Siemens-0.8.19-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. antohami openscada-DAQ.SoundCard-0.8.19-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. antohami openscada-DAQ.System-0.8.19-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. antohami openscada-DB.DBF-0.8.19-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. antohami openscada-DB.FireBird-0.8.19-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. antohami openscada-DB.MySQL-0.8.19-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. antohami openscada-DB.PostgreSQL-0.8.19-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. antohami openscada-DB.SQLite-0.8.19-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. antohami openscada-Model.AGLKS-0.8.19-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/openscada_AGLKS.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). antohami openscada-Model.AGLKS-0.8.19-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/openscada_AGLKS.desktop: hint: value "Graphics;Development;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu antohami openscada-Model.Boiler-0.8.19-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/openscada_Boiler antohami openscada-Model.Boiler-0.8.19-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/openscada_Boiler.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). antohami openscada-Model.Boiler-0.8.19-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/openscada_Boiler.desktop: hint: value "Graphics;Development;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu antohami openscada-Protocol.HTTP-0.8.19-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. antohami openscada-Protocol.SelfSystem-0.8.19-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. antohami openscada-Protocol.UserProtocol-0.8.19-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. antohami openscada-Special.FLibComplex1-0.8.19-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. antohami openscada-Special.FLibMath-0.8.19-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. antohami openscada-Special.FLibSYS-0.8.19-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. antohami openscada-Special.SystemTests-0.8.19-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. antohami openscada-Transport.SSL-0.8.19-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. antohami openscada-Transport.Serial-0.8.19-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. antohami openscada-Transport.Sockets-0.8.19-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. antohami openscada-UI.QTCfg-0.8.19-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. antohami openscada-UI.QTStarter-0.8.19-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. antohami openscada-UI.QTStarter-0.8.19-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/openscada.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). antohami openscada-UI.QTStarter-0.8.19-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/openscada.desktop: hint: value "Graphics;Development;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu antohami openscada-UI.VCAEngine-0.8.19-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. antohami openscada-UI.Vision-0.8.19-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. antohami openscada-UI.WebCfg-0.8.19-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. antohami openscada-UI.WebCfgD-0.8.19-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. antohami openscada-UI.WebUser-0.8.19-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. antohami openscada-UI.WebVision-0.8.19-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. antohami openscada-core-0.8.19-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. antohami openscada-core-0.8.19-alt1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it. antohami openscada-core-0.8.19-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. antohami otter-browser-0.9.96-alt1.S1.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. antohami pcmanfm-1.3.0-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/pcmanfm.desktop: hint: value "System;FileTools;FileManager;Utility;Core;GTK;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu antohami qashctl-0.21.0-alt2.S1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/qashctl.desktop: warning: value "ALSA HCTL mixer" for key "Comment" in group "Desktop Entry" looks redundant with value "ALSA HCTL mixer" of key "GenericName"
/usr/share/applications/qashctl.desktop: warning: value "ALSA HCTL mixer" for key "Comment[de]" in group "Desktop Entry" looks redundant with value "ALSA HCTL mixer" of key "GenericName[de]"
/usr/share/applications/qashctl.desktop: warning: value "????? ALSA HCTL" for key "Comment[he]" in group "Desktop Entry" looks redundant with value "????? ALSA HCTL" of key "GenericName[he]"
/usr/share/applications/qashctl.desktop: warning: value "ALSA HCTL mixer" for key "Comment[it]" in group "Desktop Entry" looks redundant with value "ALSA HCTL mixer" of key "GenericName[it]"
/usr/share/applications/qashctl.desktop: warning: value "ALSA HCTL ??????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "ALSA HCTL ??????" of key "GenericName[ru]" antohami qlipper-5.1.1-alt2.S1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/qlipper.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). antohami qmaster-0.2.3-alt2.S1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. antohami qslave-1.0.2-alt1.S1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. antohami rtl-sdr-0.5.3-alt2.20170920.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 antohami rtlsdr-scanner-1.3.0-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/rtlsdr-scanner.desktop: hint: value item "HamRadio" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Network, or Audio antohami screenshot-tool-0.1.4-alt1.S1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/screenshot-tool.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). antohami sddm-config-editor-0.1-alt1.20170916.S1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/sddm-config-editor.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). antohami sddm-config-editor-0.1-alt1.20170916.S1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/sddm-config-editor.desktop: hint: value "Settings;System;Qt;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu antohami spacefm-1.0.6-alt1.S1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/spacefm-find.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). antohami spacefm-1.0.6-alt1.S1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/spacefm-folder-handler.desktop: warning: value "Attais?? mapi" for key "Comment[ltg]" in group "Desktop Entry" looks redundant with value "Attais?? mapi" of key "Name[ltg]"
desktop-file-validate utility printed the following message(s): /usr/share/applications/spacefm.desktop: hint: value "System;FileTools;Utility;Core;GTK;FileManager;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu antohami syncthing-0.14.47-alt1.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts. antohami syncthing-gtk-0.9.3.1-alt1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. antohami trikStudio-data-3.1.4-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/trikStudio.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). antohami trimage-1.0.5-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/trimage.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). antohami uhd-3.11.0.0-alt2.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 antohami zita-convolver-3.1.0-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 antohami zita-resampler-1.3.0-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 aris alacarte-3.11.91-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/alacarte.desktop: hint: value item "GNOME" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: GTK
/usr/share/applications/alacarte.desktop: hint: value "GNOME;Settings;DesktopSettings;Utility;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu aris calf-0.90.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. aris calf-gui-0.90.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. aris calf-gui-0.90.0-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/calf.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). aris calf-gui-0.90.0-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/calf.desktop: error: value "0.90.0" for key "Version" in group "Desktop Entry" is not a known version
/usr/share/applications/calf.desktop: hint: value item "GNOME" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: GTK aris dmraid-1.0.0.rc16-alt2.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 aris gpodder-3.9.5-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/gpodder.desktop: hint: value "AudioVideo;Audio;Network;FileTransfer;News;GTK;Tuner;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu aris gucharmap7-2.32.1-alt1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/etc/gconf/schemas/gucharmap.schemas
/usr/bin/charmap
/usr/bin/gnome-character-map
/usr/bin/gucharmap
/usr/share/applications/gucharmap.desktop
/usr/share/gnome/help/gucharmap/C/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/C/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/C/gucharmap.xml
/usr/share/gnome/help/gucharmap/C/legal.xml
/usr/share/gnome/help/gucharmap/bg/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/bg/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/bg/gucharmap.xml
/usr/share/gnome/help/gucharmap/ca/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/ca/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/ca/gucharmap.xml
/usr/share/gnome/help/gucharmap/cs/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/cs/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/cs/gucharmap.xml
/usr/share/gnome/help/gucharmap/de/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/de/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/de/gucharmap.xml
/usr/share/gnome/help/gucharmap/el/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/el/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/el/gucharmap.xml
/usr/share/gnome/help/gucharmap/en_GB/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/en_GB/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/en_GB/gucharmap.xml
/usr/share/gnome/help/gucharmap/es/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/es/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/es/gucharmap.xml
/usr/share/gnome/help/gucharmap/fi/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/fi/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/fi/gucharmap.xml
/usr/share/gnome/help/gucharmap/fr/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/fr/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/fr/gucharmap.xml
/usr/share/gnome/help/gucharmap/it/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/it/gucharmap.xml
/usr/share/gnome/help/gucharmap/it/legal.xml
/usr/share/gnome/help/gucharmap/ja/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/ja/gucharmap.xml
/usr/share/gnome/help/gucharmap/ja/legal.xml
/usr/share/gnome/help/gucharmap/ko/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/ko/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/ko/gucharmap.xml
/usr/share/gnome/help/gucharmap/oc/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/oc/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/oc/gucharmap.xml
/usr/share/gnome/help/gucharmap/pt_BR/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/pt_BR/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/pt_BR/gucharmap.xml
/usr/share/gnome/help/gucharmap/ru/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/ru/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/ru/gucharmap.xml
/usr/share/gnome/help/gucharmap/sv/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/sv/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/sv/gucharmap.xml
/usr/share/gnome/help/gucharmap/vi/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/vi/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/vi/gucharmap.xml
/usr/share/gnome/help/gucharmap/zh_CN/figures/gucharmap_start_window.png
/usr/share/gnome/help/gucharmap/zh_CN/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/zh_CN/gucharmap.xml
/usr/share/gnome/help/gucharmap/zh_HK/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/zh_HK/gucharmap.xml
/usr/share/gnome/help/gucharmap/zh_HK/legal.xml
/usr/share/gnome/help/gucharmap/zh_TW/figures/gucharmap_window.png
/usr/share/gnome/help/gucharmap/zh_TW/gucharmap.xml
/usr/share/gnome/help/gucharmap/zh_TW/legal.xml
/usr/share/locale/af/LC_MESSAGES/gucharmap.mo
/usr/share/locale/am/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ar/LC_MESSAGES/gucharmap.mo
/usr/share/locale/as/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ast/LC_MESSAGES/gucharmap.mo
/usr/share/locale/az/LC_MESSAGES/gucharmap.mo
/usr/share/locale/be/LC_MESSAGES/gucharmap.mo
/usr/share/locale/be@latin/LC_MESSAGES/gucharmap.mo
/usr/share/locale/bg/LC_MESSAGES/gucharmap.mo
/usr/share/locale/bn/LC_MESSAGES/gucharmap.mo
/usr/share/locale/bn_IN/LC_MESSAGES/gucharmap.mo
/usr/share/locale/br/LC_MESSAGES/gucharmap.mo
/usr/share/locale/bs/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ca/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ca@valencia/LC_MESSAGES/gucharmap.mo
/usr/share/locale/cs/LC_MESSAGES/gucharmap.mo
/usr/share/locale/cy/LC_MESSAGES/gucharmap.mo
/usr/share/locale/da/LC_MESSAGES/gucharmap.mo
/usr/share/locale/de/LC_MESSAGES/gucharmap.mo
/usr/share/locale/dz/LC_MESSAGES/gucharmap.mo
/usr/share/locale/el/LC_MESSAGES/gucharmap.mo
/usr/share/locale/en@shaw/LC_MESSAGES/gucharmap.mo
/usr/share/locale/en_CA/LC_MESSAGES/gucharmap.mo
/usr/share/locale/en_GB/LC_MESSAGES/gucharmap.mo
/usr/share/locale/eo/LC_MESSAGES/gucharmap.mo
/usr/share/locale/es/LC_MESSAGES/gucharmap.mo
/usr/share/locale/et/LC_MESSAGES/gucharmap.mo
/usr/share/locale/eu/LC_MESSAGES/gucharmap.mo
/usr/share/locale/fa/LC_MESSAGES/gucharmap.mo
/usr/share/locale/fi/LC_MESSAGES/gucharmap.mo
/usr/share/locale/fr/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ga/LC_MESSAGES/gucharmap.mo
/usr/share/locale/gl/LC_MESSAGES/gucharmap.mo
/usr/share/locale/gu/LC_MESSAGES/gucharmap.mo
/usr/share/locale/he/LC_MESSAGES/gucharmap.mo
/usr/share/locale/hi/LC_MESSAGES/gucharmap.mo
/usr/share/locale/hr/LC_MESSAGES/gucharmap.mo
/usr/share/locale/hu/LC_MESSAGES/gucharmap.mo
/usr/share/locale/id/LC_MESSAGES/gucharmap.mo
/usr/share/locale/is/LC_MESSAGES/gucharmap.mo
/usr/share/locale/it/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ja/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ka/LC_MESSAGES/gucharmap.mo
/usr/share/locale/kn/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ko/LC_MESSAGES/gucharmap.mo
/usr/share/locale/lt/LC_MESSAGES/gucharmap.mo
/usr/share/locale/lv/LC_MESSAGES/gucharmap.mo
/usr/share/locale/mai/LC_MESSAGES/gucharmap.mo
/usr/share/locale/mi/LC_MESSAGES/gucharmap.mo
/usr/share/locale/mk/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ml/LC_MESSAGES/gucharmap.mo
/usr/share/locale/mn/LC_MESSAGES/gucharmap.mo
/usr/share/locale/mr/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ms/LC_MESSAGES/gucharmap.mo
/usr/share/locale/nb/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ne/LC_MESSAGES/gucharmap.mo
/usr/share/locale/nl/LC_MESSAGES/gucharmap.mo
/usr/share/locale/nn/LC_MESSAGES/gucharmap.mo
/usr/share/locale/oc/LC_MESSAGES/gucharmap.mo
/usr/share/locale/or/LC_MESSAGES/gucharmap.mo
/usr/share/locale/pa/LC_MESSAGES/gucharmap.mo
/usr/share/locale/pl/LC_MESSAGES/gucharmap.mo
/usr/share/locale/pt/LC_MESSAGES/gucharmap.mo
/usr/share/locale/pt_BR/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ro/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ru/LC_MESSAGES/gucharmap.mo
/usr/share/locale/rw/LC_MESSAGES/gucharmap.mo
/usr/share/locale/si/LC_MESSAGES/gucharmap.mo
/usr/share/locale/sk/LC_MESSAGES/gucharmap.mo
/usr/share/locale/sl/LC_MESSAGES/gucharmap.mo
/usr/share/locale/sq/LC_MESSAGES/gucharmap.mo
/usr/share/locale/sr/LC_MESSAGES/gucharmap.mo
/usr/share/locale/sr@latin/LC_MESSAGES/gucharmap.mo
/usr/share/locale/sv/LC_MESSAGES/gucharmap.mo
/usr/share/locale/ta/LC_MESSAGES/gucharmap.mo
/usr/share/locale/te/LC_MESSAGES/gucharmap.mo
/usr/share/locale/th/LC_MESSAGES/gucharmap.mo
/usr/share/locale/tr/LC_MESSAGES/gucharmap.mo
/usr/share/locale/uk/LC_MESSAGES/gucharmap.mo
/usr/share/locale/vi/LC_MESSAGES/gucharmap.mo
/usr/share/locale/wa/LC_MESSAGES/gucharmap.mo
/usr/share/locale/xh/LC_MESSAGES/gucharmap.mo
/usr/share/locale/zh_CN/LC_MESSAGES/gucharmap.mo
/usr/share/locale/zh_HK/LC_MESSAGES/gucharmap.mo
/usr/share/locale/zh_TW/LC_MESSAGES/gucharmap.mo
/usr/share/omf/gucharmap/gucharmap-C.omf
/usr/share/omf/gucharmap/gucharmap-bg.omf
/usr/share/omf/gucharmap/gucharmap-ca.omf
/usr/share/omf/gucharmap/gucharmap-cs.omf
/usr/share/omf/gucharmap/gucharmap-de.omf
/usr/share/omf/gucharmap/gucharmap-el.omf
/usr/share/omf/gucharmap/gucharmap-en_GB.omf
/usr/share/omf/gucharmap/gucharmap-es.omf
/usr/share/omf/gucharmap/gucharmap-fi.omf
/usr/share/omf/gucharmap/gucharmap-fr.omf
/usr/share/omf/gucharmap/gucharmap-it.omf
/usr/share/omf/gucharmap/gucharmap-ja.omf
/usr/share/omf/gucharmap/gucharmap-ko.omf
/usr/share/omf/gucharmap/gucharmap-oc.omf
/usr/share/omf/gucharmap/gucharmap-pt_BR.omf
/usr/share/omf/gucharmap/gucharmap-ru.omf
/usr/share/omf/gucharmap/gucharmap-sv.omf
/usr/share/omf/gucharmap/gucharmap-vi.omf
/usr/share/omf/gucharmap/gucharmap-zh_CN.omf
/usr/share/omf/gucharmap/gucharmap-zh_HK.omf
/usr/share/omf/gucharmap/gucharmap-zh_TW.omf aris gupnp-tools-0.8.14-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gupnp-universal-cp.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt).
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gupnp-av-cp.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt).
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gupnp-network-light.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). aris klavaro-3.03-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/klavaro.desktop: hint: value "Education;Science;ComputerScience;GTK;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu aris libgucharmap7-2.32.1-alt1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it. aris libgucharmap7-2.32.1-alt1.x86_64 missing-url info Missing Url: in a package. aris libgucharmap7-debuginfo-2.32.1-alt1.x86_64 missing-url info Missing Url: in a package. aris libgucharmap7-devel-2.32.1-alt1.x86_64 missing-url info Missing Url: in a package. aris lincity-ng-data-2.9-alt0.2.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. aris orca-3.28.1-alt1.noarch big-changelog info Package contains big ChangeLog. Gzip it. aris python-module-colorlog-3.1.4-alt1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/colorlog/tests/test_colorlog.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/lib/python2.7/site-packages/colorlog/tests/test_colorlog.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/lib/python2.7/site-packages/colorlog/tests/test_colorlog.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/lib/python2.7/site-packages/colorlog/tests/test_config.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/lib/python2.7/site-packages/colorlog/tests/test_config.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/lib/python2.7/site-packages/colorlog/tests/test_config.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/lib/python2.7/site-packages/colorlog/tests/test_escape_codes.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/lib/python2.7/site-packages/colorlog/tests/test_escape_codes.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/lib/python2.7/site-packages/colorlog/tests/test_escape_codes.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/lib/python2.7/site-packages/colorlog/tests/test_example.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/lib/python2.7/site-packages/colorlog/tests/test_example.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/lib/python2.7/site-packages/colorlog/tests/test_example.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/lib/python2.7/site-packages/colorlog/tests/test_exports.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/lib/python2.7/site-packages/colorlog/tests/test_exports.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/lib/python2.7/site-packages/colorlog/tests/test_exports.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/lib/python2.7/site-packages/colorlog/tests/test_logging.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/lib/python2.7/site-packages/colorlog/tests/test_logging.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/lib/python2.7/site-packages/colorlog/tests/test_logging.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. ashen fpc-compiler-3.0.4-alt1.x86_64 buildroot fail found paths to buildroot: /etc/fppkg.cfg: CompilerConfigDir=/usr/src/tmp/fpc-buildroot/etc/fppkg ashen fpc-docs-3.0.4-alt1.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. ashen fpc-utils-3.0.4-alt1.x86_64 bin-permissions info not executable file /usr/bin/makeskel.rsj
not executable file /usr/bin/ptop.rsj ashen xmms-icons-0.1-alt3.noarch missing-url info Missing Url: in a package. ashen xmms-icons-0.1-alt3.noarch rpm-obsolete-self warn The package obsoletes itself. Must be an error in spec file. Please provide Obsoletes: with the valid value. ashen xmms-skins-bigset-0.1-alt1.noarch missing-url info Missing Url: in a package. asy apache2-mod_fcgid-2.3.9-alt2.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. asy apache2-mod_fcgid-2.3.9-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. asy apcupsd-multiups-0.3-alt1.noarch init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. asy clamav-0.99.4-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. asy cyrus-imapd-2.5.11-alt3.1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. asy cyrus-imapd-2.5.11-alt3.1.x86_64 rpm-filesystem-conflict-file-file warn Files /etc/pam.d/imap /usr/share/man/man8/imapd.8.xz conflict with the package courier-imap-4.17.2-alt0.3.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. asy cyrus-sasl2-2.1.26-alt7.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. asy cyrus-sasl2-2.1.26-alt7.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. asy mailutils-debuginfo-3.4-alt1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/bin/Mail.debug is different from the same symlink in the package mailx-debuginfo-8.1.2-alt7.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/bin/mailx.debug is different from the same symlink in the package mailx-debuginfo-8.1.2-alt7.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. asy mc-4.8.20-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. asy nfdump-1.6.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. asy opencpn-data-4.4.0-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/opencpn.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). asy xorp-1.8.6-alt0.20130830.1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/sbin/bgp_xrl_shell_funcs.sh /usr/sbin/fea_xrl_shell_funcs.sh asy xorp-1.8.6-alt0.20130830.1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. asy xymon-4.3.28-alt2.1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. asy xymon-client-4.3.28-alt2.1.noarch init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. asy xymon-common-4.3.28-alt2.1.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. asy zygrib-8.0.1-alt2.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/zyGrib.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). asy zygrib-8.0.1-alt2.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. avm arepo-1-alt10.noarch missing-url info Missing Url: in a package. avm gitosis-0.2-alt1.1.1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/gitosis/test/test_access.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/lib/python2.7/site-packages/gitosis/test/test_access.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/lib/python2.7/site-packages/gitosis/test/test_access.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/lib/python2.7/site-packages/gitosis/test/test_gitdaemon.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/lib/python2.7/site-packages/gitosis/test/test_gitdaemon.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/lib/python2.7/site-packages/gitosis/test/test_gitdaemon.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/lib/python2.7/site-packages/gitosis/test/test_gitweb.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/lib/python2.7/site-packages/gitosis/test/test_gitweb.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/lib/python2.7/site-packages/gitosis/test/test_gitweb.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/lib/python2.7/site-packages/gitosis/test/test_group.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/lib/python2.7/site-packages/gitosis/test/test_group.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/lib/python2.7/site-packages/gitosis/test/test_group.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/lib/python2.7/site-packages/gitosis/test/test_init.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/lib/python2.7/site-packages/gitosis/test/test_init.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/lib/python2.7/site-packages/gitosis/test/test_init.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/lib/python2.7/site-packages/gitosis/test/test_repository.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/lib/python2.7/site-packages/gitosis/test/test_repository.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/lib/python2.7/site-packages/gitosis/test/test_repository.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/lib/python2.7/site-packages/gitosis/test/test_run_hook.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/lib/python2.7/site-packages/gitosis/test/test_run_hook.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/lib/python2.7/site-packages/gitosis/test/test_run_hook.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/lib/python2.7/site-packages/gitosis/test/test_serve.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/lib/python2.7/site-packages/gitosis/test/test_serve.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/lib/python2.7/site-packages/gitosis/test/test_serve.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/lib/python2.7/site-packages/gitosis/test/test_ssh.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/lib/python2.7/site-packages/gitosis/test/test_ssh.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/lib/python2.7/site-packages/gitosis/test/test_ssh.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. avm gsynaptics-0.9.16-alt3.qa1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/gsynaptics.desktop: hint: value item "GNOME" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: GTK avm gsynaptics-0.9.16-alt3.qa1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. avm gsynaptics-0.9.16-alt3.qa1.x86_64 rpm-package-is-obsoleted warn The package is obsoleted by the package gpointing-device-settings-1.5.1-alt5.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 gpointing-device-settings-1.5.1-alt5.x86_64 to remove Obsoletes: tag. avm libmp3splt-0.9.2-alt1.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libmp3splt0/libsplt_flac.so but just /usr/lib64/libmp3splt0/libsplt_flac.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libmp3splt0/libsplt_flac.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libmp3splt0/libsplt_flac.so to \%files of libmp3splt-0.9.2-alt1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libmp3splt0/libsplt_mp3.so but just /usr/lib64/libmp3splt0/libsplt_mp3.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libmp3splt0/libsplt_mp3.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libmp3splt0/libsplt_mp3.so to \%files of libmp3splt-0.9.2-alt1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libmp3splt0/libsplt_ogg.so but just /usr/lib64/libmp3splt0/libsplt_ogg.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libmp3splt0/libsplt_ogg.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libmp3splt0/libsplt_ogg.so to \%files of libmp3splt-0.9.2-alt1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test. azol AlephOne-1.0.1-alt1.2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/AlephOne.desktop: warning: value "First person shooter game" for key "Comment" in group "Desktop Entry" looks redundant with value "First person shooter game" of key "GenericName"
/usr/share/applications/AlephOne.desktop: warning: value "3D-????????? ?? ??????? ????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "3D-????????? ?? ??????? ????" of key "GenericName[ru]" baywind webobjects-5.4.3-alt2.noarch init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. baywind webobjects-5.4.3-alt2.noarch init-lsb fail /etc/rc.d/init.d/womonitor: not systemd compatible: lsb init header missing and womonitor.service is not present. /etc/rc.d/init.d/wotaskd: not systemd compatible: lsb init header missing and wotaskd.service is not present. See http://www.altlinux.org/Services_Policy for details. becase jpcap-0.7-alt4.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libjpcap.so but just /usr/lib64/libjpcap.so.0.7. According to SharedLibs Policy Draft, symlink /usr/lib64/libjpcap.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libjpcap.so to \%files of jpcap-0.7-alt4.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test. becase starboard-preinstall-1.0-alt4.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/sbin/starboard-fix-install-script becase starboard-preinstall-1.0-alt4.noarch missing-url info Missing Url: in a package. bga alt-license-office-server-0.1-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-0.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.
Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-sj-0.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.
Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-sl-0.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.
Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-sm-0.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.
Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-junior-st-0.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.
Files /usr/share/alt-license/license.all.html /usr/share/alt-license/license.ru.html conflict with the package alt-license-server-0.1-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. bga alt-license-office-server-0.1-alt1.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package branding-altlinux-office-server-notes-5.9.9-alt1.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 branding-altlinux-office-server-notes-5.9.9-alt1.noarch to remove Obsoletes: tag. bga fonts-type1-cm-super-0.3.3-alt8.qa1.1.noarch missing-url info Missing Url: in a package. bga fonts-type1-cm-super-0.3.3-alt8.qa1.1.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. bga fonts-type1-cm-super-afm-0.3.3-alt8.qa1.1.noarch missing-url info Missing Url: in a package. bga fonts-type1-cm-super-pfb-0.3.3-alt8.qa1.1.noarch missing-url info Missing Url: in a package. bga fonts-type1-cm-super-pfb-0.3.3-alt8.qa1.1.noarch symlink-extra-slash info /etc/X11/fontpath.d/type1-cm-super:pri=40:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible. bga fonts-type1-cm-super-tex-0.3.3-alt8.qa1.1.noarch missing-url info Missing Url: in a package. bga fonts-type1-cm-super-tex-afm-0.3.3-alt8.qa1.1.noarch missing-url info Missing Url: in a package. bga fonts-type1-cm-super-tex-dvips-0.3.3-alt8.qa1.1.noarch missing-url info Missing Url: in a package. bga fonts-type1-urw-tex-2.0-alt8.noarch invalid-url warn Package has invalid Url:. It looks like a protocol part (http:,ftp:,etc.) is missing. bga fonts-type1-urw-tex-2.0-alt8.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/share/texmf/ChangeLog
/usr/share/texmf/LICENSE
/usr/share/texmf/README
/usr/share/texmf/build.sh
/usr/share/texmf/hehe.pl
/usr/share/texmf/license-motygin
/usr/share/texmf/make_links.sh
/usr/share/texmf/problem
/usr/share/texmf/readme-motygin
/usr/share/texmf/thescript.sh bga fonts-type1-urw-tex-afm-2.0-alt8.noarch invalid-url warn Package has invalid Url:. It looks like a protocol part (http:,ftp:,etc.) is missing. bga fonts-type1-urw-tex-doc-2.0-alt8.noarch invalid-url warn Package has invalid Url:. It looks like a protocol part (http:,ftp:,etc.) is missing. bga gkrellm-alltraxclock2-0.2-alt1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/share/locale/ru/LC_MESSAGES/gkrellm-alltraxclock.mo bga ipw3945d-1.7.22-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. bga ipw3945d-1.7.22-alt1.x86_64 init-lsb fail /etc/rc.d/init.d/ipw3945d: not systemd compatible: lsb init header missing and ipw3945d.service is not present. See http://www.altlinux.org/Services_Policy for details. bga obconf-2.0.4-alt2.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. bga trac-spawn-fcgi-0.2-alt1.qa1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/trac-spawn-fcgi bga trac-spawn-fcgi-0.2-alt1.qa1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. bga trac-spawn-fcgi-0.2-alt1.qa1.x86_64 init-lsb fail /etc/rc.d/init.d/trac-spawn-fcgi: not systemd compatible: lsb init header missing and trac-spawn-fcgi.service is not present. See http://www.altlinux.org/Services_Policy for details. bga trac-spawn-fcgi-0.2-alt1.qa1.x86_64 missing-url info Missing Url: in a package. bga trac-spawn-fcgi-0.2-alt1.qa1.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. bga trac-spawn-fcgi-debuginfo-0.2-alt1.qa1.x86_64 missing-url info Missing Url: in a package. bga ve-proxy-server-0.1-alt2.noarch missing-url info Missing Url: in a package. bga xbill-2.1-alt5.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/xbill.desktop: warning: file contains lines that are not UTF-8 encoded. There is no guarantee the validator will correctly work.
[Invalid UTF-8] /usr/share/applications/xbill.desktop: error: value "\xf0\xcf\xcd\xc5\xdb\xc1\xca\xd4\xc5 \xe2\xc9\xcc\xcc\xd5 \xd0\xcf\xd3\xd4\xc1\xd7\xc9\xd4\xd8 \xd3\xd7\xcf\xc0 \xef\xf3 \xce\xc1 \xd7\xd3\xc5 \xcb\xcf\xcd\xd0\xd8\xc0\xd4\xc5\xd2\xd9" for locale string key "Comment" in group "Desktop Entry" contains invalid UTF-8 characters, locale string values should be encoded in UTF-8 boresexpress bacula7-7.4.7-alt3.S1.src specfile-macros-get_dep-is-deprecated experimental Versioned Requires: foo >= %{get_dep something} using %get_dep and %get_version macros on a library are deprecated by set:versions. You probably should drop %get_dep/%get_version Requires: to avoid RPM database pollution. boresexpress bacula7-bat-7.4.7-alt3.S1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/bat.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). boresexpress bacula7-bat-7.4.7-alt3.S1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/bat.desktop: hint: value "System;Utility;X-Red-Hat-Base;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu boresexpress bacula7-client-7.4.7-alt3.S1.x86_64 init-lsb warn /etc/rc.d/init.d/bacula-fd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. boresexpress bacula7-common-7.4.7-alt3.S1.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. boresexpress bacula7-common-debuginfo-7.4.7-alt3.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libbac.so.debug is different from the same symlink in the package bacula-common-debuginfo-5.2.13-alt11.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libbac.so.debug is different from the same symlink in the package bacula9-common-debuginfo-9.0.6-alt1.S1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libbaccfg.so.debug is different from the same symlink in the package bacula-common-debuginfo-5.2.13-alt11.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libbaccfg.so.debug is different from the same symlink in the package bacula9-common-debuginfo-9.0.6-alt1.S1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libbacfind.so.debug is different from the same symlink in the package bacula-common-debuginfo-5.2.13-alt11.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libbacfind.so.debug is different from the same symlink in the package bacula9-common-debuginfo-9.0.6-alt1.S1.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. boresexpress bacula7-director-common-7.4.7-alt3.S1.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts. boresexpress bacula7-director-common-7.4.7-alt3.S1.x86_64 unsafe-tmp-usage-in-scripts fail 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/bacula7-director-common-7.4.7/updatedb/update_mysql_tables_11_to_12: $ grep -A5 -B5 /tmp/ /usr/share/doc/bacula7-director-common-7.4.7/updatedb/update_mysql_tables_11_to_12 echo " " bindir=/usr/bin PATH="$bindir:$PATH" db_name=${db_name:-bacula} mysql $* -D ${db_name} -e "select VersionId from Version\G" >/tmp/$$ DBVERSION=`sed -n -e 's/^VersionId: \(.*\)$/\1/p' /tmp/$$` if [ $DBVERSION != 11 ] ; then echo " " echo "The existing database is version $DBVERSION !!" echo "This script can only update an existing version 11 database to version 12." echo "Error. Cannot upgrade this database." boresexpress bacula7-director-common-debuginfo-7.4.7-alt3.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libbacsql.so.debug is different from the same symlink in the package bacula-director-common-debuginfo-5.2.13-alt11.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libbacsql.so.debug is different from the same symlink in the package bacula9-director-common-debuginfo-9.0.6-alt1.S1.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. boresexpress bacula7-director-mysql-7.4.7-alt3.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. boresexpress bacula7-director-mysql-7.4.7-alt3.S1.x86_64 init-lsb warn /etc/rc.d/init.d/bacula-dir: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. boresexpress bacula7-director-mysql-7.4.7-alt3.S1.x86_64 rpm-filesystem-conflict-file-file warn File /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-postgresql-5.2.13-alt11.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-sqlite3-5.2.13-alt11.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. boresexpress bacula7-director-mysql-7.4.7-alt3.S1.x86_64 unsafe-tmp-usage-in-scripts fail 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/bacula/scripts/update_mysql_tables: $ grep -A5 -B5 /tmp/ /usr/share/bacula/scripts/update_mysql_tables ARGS=$* getVersion() { mysql $ARGS -D ${db_name} -e "select VersionId from Version LIMIT 1\G" >/tmp/$$ DBVERSION=`sed -n -e 's/^VersionId: \(.*\)$/\1/p' /tmp/$$` } getVersion if [ "x$DBVERSION" = x ]; then boresexpress bacula7-director-mysql-debuginfo-7.4.7-alt3.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libbaccats-mysql.so.debug is different from the same symlink in the package bacula-director-mysql-debuginfo-5.2.13-alt11.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libbaccats-mysql.so.debug is different from the same symlink in the package bacula9-director-mysql-debuginfo-9.0.6-alt1.S1.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. boresexpress bacula7-director-postgresql-7.4.7-alt3.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. boresexpress bacula7-director-postgresql-7.4.7-alt3.S1.x86_64 init-lsb warn /etc/rc.d/init.d/bacula-dir: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. boresexpress bacula7-director-postgresql-7.4.7-alt3.S1.x86_64 rpm-filesystem-conflict-file-file warn File /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-mysql-5.2.13-alt11.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-sqlite3-5.2.13-alt11.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. boresexpress bacula7-director-postgresql-debuginfo-7.4.7-alt3.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libbaccats-postgresql.so.debug is different from the same symlink in the package bacula-director-postgresql-debuginfo-5.2.13-alt11.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libbaccats-postgresql.so.debug is different from the same symlink in the package bacula9-director-postgresql-debuginfo-9.0.6-alt1.S1.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. boresexpress bacula7-director-sqlite3-7.4.7-alt3.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. boresexpress bacula7-director-sqlite3-7.4.7-alt3.S1.x86_64 init-lsb warn /etc/rc.d/init.d/bacula-dir: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. boresexpress bacula7-director-sqlite3-7.4.7-alt3.S1.x86_64 rpm-filesystem-conflict-file-file warn File /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-mysql-5.2.13-alt11.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/rc.d/init.d/bacula-dir conflicts with the package bacula-director-postgresql-5.2.13-alt11.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. boresexpress bacula7-director-sqlite3-debuginfo-7.4.7-alt3.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libbaccats-sqlite3.so.debug is different from the same symlink in the package bacula-director-sqlite3-debuginfo-5.2.13-alt11.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libbaccats-sqlite3.so.debug is different from the same symlink in the package bacula9-director-sqlite3-debuginfo-9.0.6-alt1.S1.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. boresexpress bacula7-storage-7.4.7-alt3.S1.x86_64 init-lsb warn /etc/rc.d/init.d/bacula-sd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. boresexpress djbdns-1.05-alt1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/etc/djbdns/axfrdns/env/IP
/etc/djbdns/axfrdns/env/ROOT boresexpress opie-2.4-alt1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/lib64/libopie.a boyarsh 0ad-0.0.22-alt1.src 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. boyarsh 0ad-0.0.22-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. boyarsh alsaplayer-0.99.80-alt11.3.src requires-ImageMagick info Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell. boyarsh alt-domain-server-0.4-alt1.noarch missing-url info Missing Url: in a package. boyarsh alt-domain-server-0.4-alt1.noarch rpm-obsolete-live-package info The package obsoletes the package installer-feature-setup-openldap-0.3-alt1.noarch, but the package installer-feature-setup-openldap-0.3-alt1.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. boyarsh altsp-test-scripts-1.0-alt1.x86_64 missing-url info Missing Url: in a package. boyarsh altsp-test-scripts-1.0-alt1.x86_64 rpm-obsolete-live-package info The package obsoletes the package spt7-test-scripts-1.4-alt1.x86_64, but the package spt7-test-scripts-1.4-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. boyarsh altsp-test-scripts-debuginfo-1.0-alt1.x86_64 missing-url info Missing Url: in a package. boyarsh branding-altlinux-centaurus-7.0.5-alt1.src requires-ImageMagick info Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell. boyarsh branding-altlinux-centaurus-alterator-7.0.5-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-altlinux-kdesktop-alterator-8.0.0-alt0.6.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-sisyphus-server-light-alterator-1.9.3-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-xalt-kworkstation-alterator-8.2.0-alt3.S1.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 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. boyarsh branding-altlinux-centaurus-alterator-7.0.5-alt1.noarch rpm-filesystem-conflict-symlink-file warn symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/packges.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/packges.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/packges.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/packges.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-xalt-kworkstation-alterator-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. boyarsh branding-altlinux-centaurus-alterator-7.0.5-alt1.noarch rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-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.
value of symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-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.
value of symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-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.
value of symlink /usr/share/alterator/design/images/steps/pkg-groups.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-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.
value of symlink /usr/share/alterator/design/images/steps/root.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-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.
value of symlink /usr/share/alterator/design/images/steps/timezone.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-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. boyarsh branding-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-altlinux-backup-server-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-desktop-indexhtml-5.9.9-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch, for example, /usr/share/applications/indexhtml.desktop (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.
There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/doc/indexhtml/images/altlinux-logo.png (11 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/applications/indexhtml.desktop /usr/share/doc/indexhtml/index-en.html conflict with the package branding-altlinux-spt-indexhtml-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.
There are file conflicts with the package branding-altlinux-tablet-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-informika-schoolmaster-indexhtml-6.0.0-alt47.noarch, for example, /usr/share/applications/indexhtml.desktop (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-simply-linux-indexhtml-8.2.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (11 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-sisyphus-server-light-indexhtml-1.9.3-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-xalt-kworkstation-indexhtml-8.2.0-alt3.S1.noarch, for example, /usr/share/applications/indexhtml.desktop (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. boyarsh branding-altlinux-centaurus-kde4-settings-7.0.5-alt1.noarch rpm-filesystem-conflict-file-file warn File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-alt-sisyphus-kde4-settings-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/skel/.kde4/share/config/default-apps conflicts with the package branding-xalt-kworkstation-kde4-settings-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. boyarsh branding-altlinux-centaurus-notes-7.0.5-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-alt-sisyphus-notes-20170925-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-xalt-kworkstation-notes-8.2.0-alt3.S1.noarch, for example, /usr/share/alt-notes/license.all.html (4 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. boyarsh branding-altlinux-centaurus-release-7.0.5-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 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.
Files /etc/altlinux-release /etc/os-release conflict 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. boyarsh branding-altlinux-spt-7.0.0-alt1.src requires-ImageMagick info Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell. boyarsh branding-altlinux-spt-alterator-7.0.0-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-altlinux-kdesktop-alterator-8.0.0-alt0.6.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-sisyphus-server-light-alterator-1.9.3-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-xalt-kworkstation-alterator-8.2.0-alt3.S1.noarch, for example, /usr/share/alterator/design/images/attention.gif (15 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. boyarsh branding-altlinux-spt-alterator-7.0.0-alt1.noarch rpm-filesystem-conflict-symlink-file warn symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/packges.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/packges.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/packges.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/packges.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-xalt-kworkstation-alterator-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.
symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-sisyphus-server-light-alterator-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.
symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-altlinux-kdesktop-alterator-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.
symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-informika-schoolmaster-alterator-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.
symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-xalt-kworkstation-alterator-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. boyarsh branding-altlinux-spt-alterator-7.0.0-alt1.noarch rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-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.
value of symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-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.
value of symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-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.
value of symlink /usr/share/alterator/design/images/steps/pkg-groups.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-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.
value of symlink /usr/share/alterator/design/images/steps/root.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-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.
value of symlink /usr/share/alterator/design/images/steps/timezone.png is different from the same symlink in the package branding-xalt-kworkstation-alterator-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. boyarsh branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-altlinux-backup-server-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/applications/indexhtml.desktop /usr/share/doc/indexhtml/index-en.html conflict with the package branding-altlinux-centaurus-indexhtml-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.
There are file conflicts with the package branding-altlinux-desktop-indexhtml-5.9.9-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch, for example, /usr/share/applications/indexhtml.desktop (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.
There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-lxdesktop-indexhtml-6.0.0-alt7.noarch, for example, /usr/share/applications/indexhtml.desktop (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-tablet-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-informika-schoolmaster-indexhtml-6.0.0-alt47.noarch, for example, /usr/share/applications/indexhtml.desktop (11 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-simply-linux-indexhtml-8.2.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (11 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-sisyphus-server-light-indexhtml-1.9.3-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-xalt-kworkstation-indexhtml-8.2.0-alt3.S1.noarch, for example, /usr/share/applications/indexhtml.desktop (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. boyarsh branding-altlinux-spt-kde4-settings-7.0.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-alt-sisyphus-kde4-settings-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/skel/.kde4/share/config/default-apps conflicts with the package branding-xalt-kworkstation-kde4-settings-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. boyarsh branding-altlinux-spt-notes-7.0.0-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-alt-sisyphus-notes-20170925-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-xalt-kworkstation-notes-8.2.0-alt3.S1.noarch, for example, /usr/share/alt-notes/license.all.html (4 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. boyarsh branding-altlinux-spt-release-7.0.0-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 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.
Files /etc/altlinux-release /etc/os-release conflict 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. boyarsh branding-altlinux-tablet-6.0.0-alt3.src requires-ImageMagick info Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell. boyarsh branding-altlinux-tablet-alterator-6.0.0-alt3.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-alt-sisyphus-alterator-20170925-alt1.noarch, for example, /usr/share/alterator/design/images/clock-face.png (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.
There are file conflicts with the package branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch, for example, /usr/share/alterator/design/images/clock-face.png (11 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-kdesktop-alterator-8.0.0-alt0.6.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-lxdesktop-alterator-6.0.0-alt7.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (36 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-sisyphus-server-light-alterator-1.9.3-alt1.noarch, for example, /usr/share/alterator/design/images/groups/datetime.png (31 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-xalt-kworkstation-alterator-8.2.0-alt3.S1.noarch, for example, /usr/share/alterator/design/images/close-dialog-button.png (30 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. boyarsh branding-altlinux-tablet-indexhtml-6.0.0-alt3.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-altlinux-backup-server-indexhtml-6.0.0-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-centaurus-indexhtml-7.0.5-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-desktop-indexhtml-5.9.9-alt3.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-kdesktop-indexhtml-8.0.0-alt0.6.noarch, for example, /usr/share/applications/indexhtml.desktop (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/applications/indexhtml.desktop /usr/share/doc/indexhtml/index-en.html /usr/share/doc/indexhtml/index-ru.html conflict with the package branding-altlinux-lxdesktop-indexhtml-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.
There are file conflicts with the package branding-altlinux-office-server-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-spt-indexhtml-7.0.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (12 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-informika-schoolmaster-indexhtml-6.0.0-alt47.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-ivk-chainmail-indexhtml-3.0-alt2.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-school-lite-indexhtml-5.9.9-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-simply-linux-indexhtml-8.2.0-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (11 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-sisyphus-server-light-indexhtml-1.9.3-alt1.noarch, for example, /usr/share/applications/indexhtml.desktop (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-xalt-kworkstation-indexhtml-8.2.0-alt3.S1.noarch, for example, /usr/share/applications/indexhtml.desktop (6 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. boyarsh branding-altlinux-tablet-kde4-settings-6.0.0-alt3.noarch rpm-filesystem-conflict-file-file warn File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-alt-sisyphus-kde4-settings-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/skel/.kde4/share/config/default-apps conflicts with the package branding-altlinux-kdesktop-kde4-settings-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/skel/.kde4/share/config/default-apps conflicts with the package branding-informika-schoolmaster-kde4-settings-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/skel/.kde4/share/config/default-apps conflicts with the package branding-xalt-kworkstation-kde4-settings-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. boyarsh branding-altlinux-tablet-notes-6.0.0-alt3.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-alt-sisyphus-notes-20170925-alt1.noarch, for example, /usr/share/alt-notes/index-en.html (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-backup-server-notes-6.0.0-alt3.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-kdesktop-notes-8.0.0-alt0.6.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-altlinux-lxdesktop-notes-6.0.0-alt7.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-informika-schoolmaster-notes-6.0.0-alt47.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-school-lite-notes-5.9.9-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-sisyphus-server-light-notes-1.9.3-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-xalt-kworkstation-notes-8.2.0-alt3.S1.noarch, for example, /usr/share/alt-notes/index-en.html (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. boyarsh branding-altlinux-tablet-release-6.0.0-alt3.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 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 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-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-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-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-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-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. boyarsh branding-school-junior-7.0.5-alt2.src requires-ImageMagick info Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell. boyarsh branding-school-junior-alterator-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch, but the package branding-altlinux-backup-server-alterator-6.0.0-alt3.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. boyarsh branding-school-junior-indexhtml-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-master-kde4-settings-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. boyarsh branding-school-junior-menu-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-server-menu-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.
There are file conflicts with the package branding-simply-linux-menu-8.2.0-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 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. boyarsh branding-school-junior-notes-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package alt-license-junior-0.1-alt2.x86_64, but the package alt-license-junior-0.1-alt2.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.
The package obsoletes the package alt-notes-junior-0.2-alt1.noarch, but the package alt-notes-junior-0.2-alt1.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. boyarsh branding-school-junior-release-7.0.5-alt2.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 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. boyarsh branding-school-junior-xfce-settings-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package livecd-gnome-nowarn-space-0.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.
Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package xfce-settings-lite-school-0.6-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.
There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 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. boyarsh branding-school-junior-xfce-settings-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package xfce-settings-lite-1.0-alt7.noarch, but the package xfce-settings-lite-1.0-alt7.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. boyarsh branding-school-server-7.0.5-alt2.src requires-ImageMagick info Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell. boyarsh branding-school-server-alterator-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch, but the package branding-altlinux-backup-server-alterator-6.0.0-alt3.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. boyarsh branding-school-server-menu-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-junior-menu-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 /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-master-menu-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 /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-teacher-menu-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.
There are file conflicts with the package branding-simply-linux-menu-8.2.0-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 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. boyarsh branding-school-server-notes-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package alt-notes-school-server-4.1-alt3.noarch, but the package alt-notes-school-server-4.1-alt3.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. boyarsh branding-school-server-release-7.0.5-alt2.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 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. boyarsh branding-school-server-xfce-settings-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package livecd-gnome-nowarn-space-0.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/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package xfce-settings-lite-office-lite-1.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.
There are file conflicts with the package xfce-settings-lite-school-0.6-alt2.noarch, for example, /etc/skel/.config/xfce4/desktop/icons.screen0.rc (4 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.
File /etc/skel/.config/xfce4/panel/launcher-10.rc conflicts with the package xfce-settings-lite-school-network-0.6-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/skel/.config/xfce4/panel/launcher-11888137035.rc conflicts with the package xfce-settings-lite-school-office-lite-0.6-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.
There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 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. boyarsh branding-school-server-xfce-settings-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package xfce-settings-lite-1.0-alt7.noarch, but the package xfce-settings-lite-1.0-alt7.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. boyarsh branding-school-teacher-7.0.5-alt2.src requires-ImageMagick info Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell. boyarsh branding-school-teacher-alterator-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-alt-sisyphus-alterator-20170925-alt1.noarch, for example, /usr/share/alterator/design/images/attention.gif (16 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. boyarsh branding-school-teacher-alterator-7.0.5-alt2.noarch rpm-filesystem-conflict-symlink-file warn symlink /usr/share/alterator/design/images/steps/datetime.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/finish.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/greeting.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/install.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-basesystem.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/install2-preinstall.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/lilo.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/net-eth.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-license.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/notes-release-notes.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/pkg-groups.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/preinstall.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/root.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-base.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-kbd.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/sysconfig-language.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/timezone.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/user.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/users.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/vm.png is a file in the package branding-alt-sisyphus-alterator-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.
symlink /usr/share/alterator/design/images/steps/x11.png is a file in the package branding-alt-sisyphus-alterator-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. boyarsh branding-school-teacher-alterator-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch, but the package branding-altlinux-backup-server-alterator-6.0.0-alt3.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. boyarsh branding-school-teacher-indexhtml-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-master-kde4-settings-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. boyarsh branding-school-teacher-kde4-settings-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /etc/skel/.kde4/share/config/default-apps conflicts with the package branding-alt-sisyphus-kde4-settings-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. boyarsh branding-school-teacher-menu-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-server-menu-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.
There are file conflicts with the package branding-simply-linux-menu-8.2.0-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 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. boyarsh branding-school-teacher-notes-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package alt-notes-school-server-4.1-alt3.noarch, for example, /usr/share/alt-notes/license.all.html (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package branding-alt-sisyphus-notes-20170925-alt1.noarch, for example, /usr/share/alt-notes/license.all.html (4 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. boyarsh branding-school-teacher-release-7.0.5-alt2.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 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. boyarsh branding-school-teacher-xfce-settings-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package branding-alt-sisyphus-xfce-settings-20170925-alt1.noarch, for example, /etc/skel/.config/xfce4/desktop/icons.screen0.rc (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package livecd-gnome-nowarn-space-0.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.
Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package xfce-settings-lite-school-0.6-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.
There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 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. boyarsh branding-school-teacher-xfce-settings-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package xfce-settings-lite-1.0-alt7.noarch, but the package xfce-settings-lite-1.0-alt7.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. boyarsh c-icap-0.5.2-alt3.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. boyarsh c-icap-0.5.2-alt3.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 boyarsh c-icap-0.5.2-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. boyarsh c-icap-0.5.2-alt3.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/c-icap.conf to \%_tmpfilesdir/. boyarsh chrontel-1.0-alt11203.1.4.3.1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. boyarsh chrontel-1.0-alt11203.1.4.3.1.x86_64 init-lsb fail /etc/rc.d/init.d/tiitoo-hdmi-daemon: not systemd compatible: lsb init header missing and tiitoo-hdmi-daemon.service is not present. See http://www.altlinux.org/Services_Policy for details. boyarsh chrontel-1.0-alt11203.1.4.3.1.x86_64 missing-url info Missing Url: in a package. boyarsh chrontel-debuginfo-1.0-alt11203.1.4.3.1.x86_64 missing-url info Missing Url: in a package. boyarsh csync-0.50.6-alt1.x86_64 missing-url info Missing Url: in a package. boyarsh csync-debuginfo-0.50.6-alt1.x86_64 missing-url info Missing Url: in a package. boyarsh dconf-defaults-tablet-0.1-alt2.noarch missing-url info Missing Url: in a package. boyarsh dconf-defaults-tablet-caribou-fullscale-0.1-alt2.noarch missing-url info Missing Url: in a package. boyarsh dconf-defaults-tablet-disable-lightbox-0.1-alt2.noarch missing-url info Missing Url: in a package. boyarsh firmware-chrontel-7036-1.0-alt11203.1.4.3.1.noarch missing-url info Missing Url: in a package. boyarsh firmware-rtl8192-0018.1025-alt1.noarch missing-url info Missing Url: in a package. boyarsh florence-0.6.0-alt2.x86_64 altlinux-find-lang-gnome warn Language specific gnome files in /usr/share/omf should be marked, for example, using %find_lang --with-gnome. See http://www.altlinux.org/FindLangPolicy for details. boyarsh florence-0.6.0-alt2.x86_64 freedesktop-categories fail Main Categories consist of those categories that every conforming desktop environment MUST support.(http://standards.freedesktop.org/menu-spec/latest/apa.html). None found in /usr/share/applications/florence.desktop. please, fix. boyarsh florence-0.6.0-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/florence.desktop: warning: value "Florence Virtual Keyboard" for key "Comment" in group "Desktop Entry" looks redundant with value "Florence Virtual Keyboard" of key "Name"
/usr/share/applications/florence.desktop: warning: value "Clavier virtuel Florence" for key "Comment[fr]" in group "Desktop Entry" looks redundant with value "Clavier virtuel Florence" of key "Name[fr]"
/usr/share/applications/florence.desktop: warning: value "TastieraVirtuale Florence" for key "Comment[it]" in group "Desktop Entry" looks redundant with value "TastieraVirtuale Florence" of key "Name[it]"
/usr/share/applications/florence.desktop: warning: value "??????????? ?????????? Florence" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "??????????? ?????????? Florence" of key "Name[ru]"
/usr/share/applications/florence.desktop: hint: value item "Accessibility" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Settings, or Utility
/usr/share/applications/florence.desktop: hint: value "Accessibility;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu boyarsh florence-0.6.0-alt2.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. boyarsh host2cat-1.01-alt6.x86_64 altlinux-policy-obsolete-httpd2-reload info This package contains httpd2 restart/reload calls in its post/un scripts. But those calls are deprecated by httpd2.filetrigger that activates by files in /etc/httpd2/ or %_libdir/apache2/modules/. It should be safe to remove those calls and rely on the filetrigger instead. boyarsh host2cat-1.01-alt6.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. boyarsh host2cat-1.01-alt6.x86_64 init-lsb fail /etc/rc.d/init.d/host2cat: not systemd compatible: lsb init header missing and host2cat.service is not present. See http://www.altlinux.org/Services_Policy for details. boyarsh host2cat-1.01-alt6.x86_64 invalid-url warn Package has invalid Url:. It looks like a protocol part (http:,ftp:,etc.) is missing. boyarsh host2cat-debuginfo-1.01-alt6.x86_64 invalid-url warn Package has invalid Url:. It looks like a protocol part (http:,ftp:,etc.) is missing. boyarsh hugin-2018.0.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. boyarsh hugin-2018.0.0-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. boyarsh ibus-1.5.18-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/ibus-setup.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). boyarsh ibus-xkbc-1.3.3-alt1.noarch altlinux-find-lang-gnome warn Language specific gnome files in /usr/share/omf should be marked, for example, using %find_lang --with-gnome. See http://www.altlinux.org/FindLangPolicy for details. boyarsh installer-distro-centaurus-stage2-8.2-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package installer-distro-altlinux-desktop-stage2-8.1.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.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.
Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-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.
Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.sh conflict with the package installer-distro-backup-server-stage2-6.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.
There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-school-server-stage2-7.0-alt9.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-server-light-stage2-8.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-tablet-stage2-6.0-alt3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-office-desktop-stage2-5.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.
Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-stage2-0.2-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. boyarsh installer-distro-tablet-stage2-6.0-alt3.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-altlinux-desktop-stage2-8.1.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.
Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.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.
Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-server-stage2-7.0.2-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.
Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.sh conflict with the package installer-distro-backup-server-stage2-6.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.
There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-school-server-stage2-7.0-alt9.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-distro-server-light-stage2-8.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.
Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-simply-linux-stage2-8.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.
Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-token-desktop-stage2-0.1.1-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.
There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-office-desktop-stage2-5.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.
Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-stage2-0.2-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. boyarsh installer-feature-alphabet-profiles-1.0-alt2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/install2/prepkg.d/50-groups.sh conflicts with the package installer-feature-centaurus-profiles-2.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 /usr/share/install2/prepkg.d/50-groups.sh conflicts with the package installer-feature-spt-profiles-0.6-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. boyarsh installer-feature-centaurus-profiles-2.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/install2/prepkg.d/50-groups.sh conflicts with the package installer-feature-alphabet-profiles-1.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 /usr/share/install2/prepkg.d/50-groups.sh conflicts with the package installer-feature-spt-profiles-0.6-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. boyarsh installer-feature-setup-openldap-0.3-alt1.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package alt-domain-server-0.4-alt1.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 alt-domain-server-0.4-alt1.noarch to remove Obsoletes: tag. boyarsh kernel-modules-asix-std-def-4.20.0-alt1.264549.1.x86_64 missing-url info Missing Url: in a package. boyarsh kernel-source-3.10-1.0.0-alt1.noarch missing-url info Missing Url: in a package. boyarsh kernel-source-3.14-1.0.0-alt1.noarch missing-url info Missing Url: in a package. boyarsh kernel-source-3.15-1.0.0-alt1.noarch missing-url info Missing Url: in a package. boyarsh kernel-source-4.1-1.0.0-alt1.noarch missing-url info Missing Url: in a package. boyarsh kernel-source-4.4-1.0.0-alt1.noarch missing-url info Missing Url: in a package. boyarsh kernel-source-LiME-1.7.8-alt1.noarch missing-url info Missing Url: in a package. boyarsh kernel-source-asix-4.20.0-alt1.noarch missing-url info Missing Url: in a package. boyarsh kernel-source-n1k-5.2.1.SK3.2.1-alt1.noarch missing-url info Missing Url: in a package. boyarsh kernel-source-rtl8192-0018.1025-alt1.noarch missing-url info Missing Url: in a package. boyarsh kernel-source-sobol-1-alt1.noarch missing-url info Missing Url: in a package. boyarsh kernel-source-trsec-1.0-alt2.noarch missing-url info Missing Url: in a package. boyarsh lastlog-notification-0.3-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/lastlog-notification-show boyarsh lastlog-notification-0.3-alt1.noarch missing-url info Missing Url: in a package. boyarsh ldap-user-tools-0.9.3-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/sbin/ldap-groupmod /usr/sbin/ldap-userdel /usr/sbin/ldap-passwd /usr/sbin/ldap-useradd boyarsh ldap-user-tools-0.9.3-alt1.noarch missing-url info Missing Url: in a package. boyarsh libcsync-0.50.6-alt1.x86_64 missing-url info Missing Url: in a package. boyarsh libcsync-debuginfo-0.50.6-alt1.x86_64 missing-url info Missing Url: in a package. boyarsh libcsync-devel-0.50.6-alt1.x86_64 missing-url info Missing Url: in a package. boyarsh libmarco-private-1.20.1-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. boyarsh libtclap-1.2.1-alt1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/share/doc/tclap/html/ArgException_8h.html
/usr/share/doc/tclap/html/ArgException_8h_source.html
/usr/share/doc/tclap/html/ArgTraits_8h.html
/usr/share/doc/tclap/html/ArgTraits_8h_source.html
/usr/share/doc/tclap/html/Arg_8h.html
/usr/share/doc/tclap/html/Arg_8h_source.html
/usr/share/doc/tclap/html/CmdLineInterface_8h.html
/usr/share/doc/tclap/html/CmdLineInterface_8h_source.html
/usr/share/doc/tclap/html/CmdLineOutput_8h.html
/usr/share/doc/tclap/html/CmdLineOutput_8h_source.html
/usr/share/doc/tclap/html/CmdLine_8h.html
/usr/share/doc/tclap/html/CmdLine_8h_source.html
/usr/share/doc/tclap/html/Constraint_8h.html
/usr/share/doc/tclap/html/Constraint_8h_source.html
/usr/share/doc/tclap/html/DocBookOutput_8h.html
/usr/share/doc/tclap/html/DocBookOutput_8h_source.html
/usr/share/doc/tclap/html/HelpVisitor_8h.html
/usr/share/doc/tclap/html/HelpVisitor_8h_source.html
/usr/share/doc/tclap/html/IgnoreRestVisitor_8h.html
/usr/share/doc/tclap/html/IgnoreRestVisitor_8h_source.html
/usr/share/doc/tclap/html/MultiArg_8h.html
/usr/share/doc/tclap/html/MultiArg_8h_source.html
/usr/share/doc/tclap/html/MultiSwitchArg_8h.html
/usr/share/doc/tclap/html/MultiSwitchArg_8h_source.html
/usr/share/doc/tclap/html/OptionalUnlabeledTracker_8h.html
/usr/share/doc/tclap/html/OptionalUnlabeledTracker_8h_source.html
/usr/share/doc/tclap/html/StandardTraits_8h.html
/usr/share/doc/tclap/html/StandardTraits_8h_source.html
/usr/share/doc/tclap/html/StdOutput_8h.html
/usr/share/doc/tclap/html/StdOutput_8h_source.html
/usr/share/doc/tclap/html/SwitchArg_8h.html
/usr/share/doc/tclap/html/SwitchArg_8h_source.html
/usr/share/doc/tclap/html/UnlabeledMultiArg_8h.html
/usr/share/doc/tclap/html/UnlabeledMultiArg_8h_source.html
/usr/share/doc/tclap/html/UnlabeledValueArg_8h.html
/usr/share/doc/tclap/html/UnlabeledValueArg_8h_source.html
/usr/share/doc/tclap/html/ValueArg_8h.html
/usr/share/doc/tclap/html/ValueArg_8h_source.html
/usr/share/doc/tclap/html/ValuesConstraint_8h.html
/usr/share/doc/tclap/html/ValuesConstraint_8h_source.html
/usr/share/doc/tclap/html/VersionVisitor_8h.html
/usr/share/doc/tclap/html/VersionVisitor_8h_source.html
/usr/share/doc/tclap/html/Visitor_8h.html
/usr/share/doc/tclap/html/Visitor_8h_source.html
/usr/share/doc/tclap/html/XorHandler_8h.html
/usr/share/doc/tclap/html/XorHandler_8h_source.html
/usr/share/doc/tclap/html/ZshCompletionOutput_8h.html
/usr/share/doc/tclap/html/ZshCompletionOutput_8h_source.html
/usr/share/doc/tclap/html/annotated.html
/usr/share/doc/tclap/html/classTCLAP_1_1Arg-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1Arg.gif
/usr/share/doc/tclap/html/classTCLAP_1_1Arg.html
/usr/share/doc/tclap/html/classTCLAP_1_1ArgException-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1ArgException.gif
/usr/share/doc/tclap/html/classTCLAP_1_1ArgException.html
/usr/share/doc/tclap/html/classTCLAP_1_1ArgParseException-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1ArgParseException.gif
/usr/share/doc/tclap/html/classTCLAP_1_1ArgParseException.html
/usr/share/doc/tclap/html/classTCLAP_1_1CmdLine-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1CmdLine.gif
/usr/share/doc/tclap/html/classTCLAP_1_1CmdLine.html
/usr/share/doc/tclap/html/classTCLAP_1_1CmdLineInterface-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1CmdLineInterface.gif
/usr/share/doc/tclap/html/classTCLAP_1_1CmdLineInterface.html
/usr/share/doc/tclap/html/classTCLAP_1_1CmdLineOutput-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1CmdLineOutput.gif
/usr/share/doc/tclap/html/classTCLAP_1_1CmdLineOutput.html
/usr/share/doc/tclap/html/classTCLAP_1_1CmdLineParseException-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1CmdLineParseException.gif
/usr/share/doc/tclap/html/classTCLAP_1_1CmdLineParseException.html
/usr/share/doc/tclap/html/classTCLAP_1_1Constraint-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1Constraint.gif
/usr/share/doc/tclap/html/classTCLAP_1_1Constraint.html
/usr/share/doc/tclap/html/classTCLAP_1_1DocBookOutput-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1DocBookOutput.gif
/usr/share/doc/tclap/html/classTCLAP_1_1DocBookOutput.html
/usr/share/doc/tclap/html/classTCLAP_1_1ExitException-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1ExitException.html
/usr/share/doc/tclap/html/classTCLAP_1_1HelpVisitor-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1HelpVisitor.gif
/usr/share/doc/tclap/html/classTCLAP_1_1HelpVisitor.html
/usr/share/doc/tclap/html/classTCLAP_1_1IgnoreRestVisitor-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1IgnoreRestVisitor.gif
/usr/share/doc/tclap/html/classTCLAP_1_1IgnoreRestVisitor.html
/usr/share/doc/tclap/html/classTCLAP_1_1MultiArg-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1MultiArg.gif
/usr/share/doc/tclap/html/classTCLAP_1_1MultiArg.html
/usr/share/doc/tclap/html/classTCLAP_1_1MultiSwitchArg-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1MultiSwitchArg.gif
/usr/share/doc/tclap/html/classTCLAP_1_1MultiSwitchArg.html
/usr/share/doc/tclap/html/classTCLAP_1_1OptionalUnlabeledTracker-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1OptionalUnlabeledTracker.html
/usr/share/doc/tclap/html/classTCLAP_1_1SpecificationException-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1SpecificationException.gif
/usr/share/doc/tclap/html/classTCLAP_1_1SpecificationException.html
/usr/share/doc/tclap/html/classTCLAP_1_1StdOutput-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1StdOutput.gif
/usr/share/doc/tclap/html/classTCLAP_1_1StdOutput.html
/usr/share/doc/tclap/html/classTCLAP_1_1SwitchArg-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1SwitchArg.gif
/usr/share/doc/tclap/html/classTCLAP_1_1SwitchArg.html
/usr/share/doc/tclap/html/classTCLAP_1_1UnlabeledMultiArg-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1UnlabeledMultiArg.gif
/usr/share/doc/tclap/html/classTCLAP_1_1UnlabeledMultiArg.html
/usr/share/doc/tclap/html/classTCLAP_1_1UnlabeledValueArg-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1UnlabeledValueArg.gif
/usr/share/doc/tclap/html/classTCLAP_1_1UnlabeledValueArg.html
/usr/share/doc/tclap/html/classTCLAP_1_1ValueArg-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1ValueArg.gif
/usr/share/doc/tclap/html/classTCLAP_1_1ValueArg.html
/usr/share/doc/tclap/html/classTCLAP_1_1ValuesConstraint-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1ValuesConstraint.gif
/usr/share/doc/tclap/html/classTCLAP_1_1ValuesConstraint.html
/usr/share/doc/tclap/html/classTCLAP_1_1VersionVisitor-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1VersionVisitor.gif
/usr/share/doc/tclap/html/classTCLAP_1_1VersionVisitor.html
/usr/share/doc/tclap/html/classTCLAP_1_1Visitor-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1Visitor.gif
/usr/share/doc/tclap/html/classTCLAP_1_1Visitor.html
/usr/share/doc/tclap/html/classTCLAP_1_1XorHandler-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1XorHandler.html
/usr/share/doc/tclap/html/classTCLAP_1_1ZshCompletionOutput-members.html
/usr/share/doc/tclap/html/classTCLAP_1_1ZshCompletionOutput.gif
/usr/share/doc/tclap/html/classTCLAP_1_1ZshCompletionOutput.html
/usr/share/doc/tclap/html/classes.html
/usr/share/doc/tclap/html/doxygen.css
/usr/share/doc/tclap/html/doxygen.png
/usr/share/doc/tclap/html/files.html
/usr/share/doc/tclap/html/functions.html
/usr/share/doc/tclap/html/functions_0x61.html
/usr/share/doc/tclap/html/functions_0x62.html
/usr/share/doc/tclap/html/functions_0x63.html
/usr/share/doc/tclap/html/functions_0x64.html
/usr/share/doc/tclap/html/functions_0x65.html
/usr/share/doc/tclap/html/functions_0x66.html
/usr/share/doc/tclap/html/functions_0x67.html
/usr/share/doc/tclap/html/functions_0x68.html
/usr/share/doc/tclap/html/functions_0x69.html
/usr/share/doc/tclap/html/functions_0x6c.html
/usr/share/doc/tclap/html/functions_0x6d.html
/usr/share/doc/tclap/html/functions_0x6e.html
/usr/share/doc/tclap/html/functions_0x6f.html
/usr/share/doc/tclap/html/functions_0x70.html
/usr/share/doc/tclap/html/functions_0x71.html
/usr/share/doc/tclap/html/functions_0x72.html
/usr/share/doc/tclap/html/functions_0x73.html
/usr/share/doc/tclap/html/functions_0x74.html
/usr/share/doc/tclap/html/functions_0x75.html
/usr/share/doc/tclap/html/functions_0x76.html
/usr/share/doc/tclap/html/functions_0x77.html
/usr/share/doc/tclap/html/functions_0x78.html
/usr/share/doc/tclap/html/functions_0x7a.html
/usr/share/doc/tclap/html/functions_0x7e.html
/usr/share/doc/tclap/html/functions_func.html
/usr/share/doc/tclap/html/functions_func_0x61.html
/usr/share/doc/tclap/html/functions_func_0x62.html
/usr/share/doc/tclap/html/functions_func_0x63.html
/usr/share/doc/tclap/html/functions_func_0x64.html
/usr/share/doc/tclap/html/functions_func_0x65.html
/usr/share/doc/tclap/html/functions_func_0x66.html
/usr/share/doc/tclap/html/functions_func_0x67.html
/usr/share/doc/tclap/html/functions_func_0x68.html
/usr/share/doc/tclap/html/functions_func_0x69.html
/usr/share/doc/tclap/html/functions_func_0x6c.html
/usr/share/doc/tclap/html/functions_func_0x6d.html
/usr/share/doc/tclap/html/functions_func_0x6e.html
/usr/share/doc/tclap/html/functions_func_0x6f.html
/usr/share/doc/tclap/html/functions_func_0x70.html
/usr/share/doc/tclap/html/functions_func_0x71.html
/usr/share/doc/tclap/html/functions_func_0x72.html
/usr/share/doc/tclap/html/functions_func_0x73.html
/usr/share/doc/tclap/html/functions_func_0x74.html
/usr/share/doc/tclap/html/functions_func_0x75.html
/usr/share/doc/tclap/html/functions_func_0x76.html
/usr/share/doc/tclap/html/functions_func_0x77.html
/usr/share/doc/tclap/html/functions_func_0x78.html
/usr/share/doc/tclap/html/functions_func_0x7a.html
/usr/share/doc/tclap/html/functions_func_0x7e.html
/usr/share/doc/tclap/html/functions_type.html
/usr/share/doc/tclap/html/functions_vars.html
/usr/share/doc/tclap/html/globals.html
/usr/share/doc/tclap/html/globals_defs.html
/usr/share/doc/tclap/html/globals_type.html
/usr/share/doc/tclap/html/hierarchy.html
/usr/share/doc/tclap/html/index.html
/usr/share/doc/tclap/html/namespaceTCLAP.html
/usr/share/doc/tclap/html/namespacemembers.html
/usr/share/doc/tclap/html/namespacemembers_func.html
/usr/share/doc/tclap/html/namespacemembers_type.html
/usr/share/doc/tclap/html/namespaces.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01bool_01_4-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01bool_01_4.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01char_01_4-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01char_01_4.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01double_01_4-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01double_01_4.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01float_01_4-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01float_01_4.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01int_01_4-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01int_01_4.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01long_01_4-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01long_01_4.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01short_01_4-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01short_01_4.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01std_1_1string_01_4-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01std_1_1string_01_4.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01unsigned_01char_01_4-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01unsigned_01char_01_4.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01unsigned_01int_01_4-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01unsigned_01int_01_4.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01unsigned_01long_01_4-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01unsigned_01long_01_4.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01unsigned_01short_01_4-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01unsigned_01short_01_4.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01wchar__t_01_4-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ArgTraits_3_01wchar__t_01_4.html
/usr/share/doc/tclap/html/structTCLAP_1_1StringLike-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1StringLike.html
/usr/share/doc/tclap/html/structTCLAP_1_1StringLikeTrait-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1StringLikeTrait.html
/usr/share/doc/tclap/html/structTCLAP_1_1ValueLike-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ValueLike.html
/usr/share/doc/tclap/html/structTCLAP_1_1ValueLikeTrait-members.html
/usr/share/doc/tclap/html/structTCLAP_1_1ValueLikeTrait.html
/usr/share/doc/tclap/html/tab_b.gif
/usr/share/doc/tclap/html/tab_l.gif
/usr/share/doc/tclap/html/tab_r.gif
/usr/share/doc/tclap/html/tabs.css
/usr/share/doc/tclap/index.html
/usr/share/doc/tclap/manual.html
/usr/share/doc/tclap/style.css boyarsh livecd-gnome-nowarn-space-0.3-alt1.noarch missing-url info Missing Url: in a package. boyarsh livecd-gnome-nowarn-space-0.3-alt1.noarch rpm-filesystem-conflict-file-file warn File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package branding-school-junior-xfce-settings-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/skel/.gconf/apps/%gconf.xml conflicts with the package branding-school-master-xfce-settings-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/skel/.gconf/apps/%gconf.xml conflicts with the package branding-school-server-xfce-settings-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/skel/.gconf/apps/%gconf.xml conflicts with the package branding-school-teacher-xfce-settings-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. boyarsh livecd-setauth-0.8-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/livecd-setauth boyarsh livecd-setauth-0.8-alt1.noarch init-condrestart fail /etc/rc.d/init.d/livecd-setauth: missing condrestart target. ERROR: alt-specific script %_sbindir/post_service (used in your %post_service macro) depends on condrestart. Please, fix./etc/rc.d/init.d/livecd-setauth: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix. boyarsh livecd-setauth-0.8-alt1.noarch init-lsb warn /etc/rc.d/init.d/livecd-setauth: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. boyarsh livecd-setauth-0.8-alt1.noarch missing-url info Missing Url: in a package. boyarsh mate-applets-1.20.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. boyarsh mate-control-center-1.20.2-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. boyarsh mate-control-center-1.20.2-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/mate-font-viewer.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). boyarsh mate-default-1.20.0-alt1.noarch missing-url info Missing Url: in a package. boyarsh mate-document-viewer-dvi-1.20.1-alt2.x86_64 rpm-filesystem-conflict-file-file warn Files /usr/lib64/atril/3/backends/dvidocument.atril-backend /usr/lib64/atril/3/backends/libdvidocument.so conflict with the package atril-gtk-dvi-1.16.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. boyarsh mate-file-archiver-1.20.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. boyarsh mate-file-manager-1.20.2-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/caja-browser.desktop: hint: value "GTK;System;Utility;Core;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu boyarsh mate-file-manager-1.20.2-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. boyarsh mate-file-manager-extensions-1.20.2-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 boyarsh mate-image-viewer-1.20.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. boyarsh mate-image-viewer-1.20.0-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/eom.desktop: hint: value item "RasterGraphics" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Graphics;2DGraphics boyarsh mate-maxi-1.20.0-alt1.noarch missing-url info Missing Url: in a package. boyarsh mate-media-1.20.0-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/mate-volume-control.desktop: hint: value item "Mixer" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: AudioVideo;Audio
/usr/share/applications/mate-volume-control.desktop: hint: value "AudioVideo;Mixer;Settings;HardwareSettings;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu boyarsh mate-minimal-1.20.0-alt1.noarch missing-url info Missing Url: in a package. boyarsh mate-panel-1.20.1-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. boyarsh mate-power-manager-1.20.1-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. boyarsh mate-screensaver-1.20.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. boyarsh mate-screensaver-1.20.0-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/screensavers/footlogo-floaters.desktop: hint: value "Screensaver;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu
desktop-file-validate utility printed the following message(s): /usr/share/applications/screensavers/popsquares.desktop: hint: value "Screensaver;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu
desktop-file-validate utility printed the following message(s): /usr/share/applications/screensavers/personal-slideshow.desktop: hint: value "Screensaver;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu
desktop-file-validate utility printed the following message(s): /usr/share/applications/screensavers/gnomelogo-floaters.desktop: hint: value "Screensaver;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu
desktop-file-validate utility printed the following message(s): /usr/share/applications/screensavers/cosmos-slideshow.desktop: hint: value "Screensaver;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu boyarsh mate-screensaver-1.20.0-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. boyarsh mate-search-tool-1.20.0-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. boyarsh mate-system-monitor-1.20.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. boyarsh mate-system-monitor-1.20.0-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. boyarsh mate-terminal-1.20.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. boyarsh mate-terminal-1.20.0-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/mate-terminal.desktop: hint: value "System;GTK;Utility;TerminalEmulator;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu boyarsh mate-text-editor-1.20.1-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. boyarsh mate-user-guide-1.20.0-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/mate-user-guide.desktop: hint: value "GTK;Core;Documentation;" for key "Categories" in group "Desktop Entry" does not contain a registered main category; application might only show up in a "catch-all" section of the application menu boyarsh mirall-1.0.2-alt5.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/bin/owncloud
/usr/share/icons/hicolor/48x48/apps/owncloud.png boyarsh mirall-1.0.2-alt5.x86_64 missing-url info Missing Url: in a package. boyarsh mirall-1.0.2-alt5.x86_64 rpm-package-is-obsoleted warn The package is obsoleted by the package nextcloud-client-2.3.3-alt4.S1.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 nextcloud-client-2.3.3-alt4.S1.x86_64 to remove Obsoletes: tag.
The package is obsoleted by the package owncloud-client-2.4.0-alt4.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 owncloud-client-2.4.0-alt4.x86_64 to remove Obsoletes: tag. boyarsh mirall-debuginfo-1.0.2-alt5.x86_64 missing-url info Missing Url: in a package. boyarsh ocrfeeder-0.7.9-alt4.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/ocrfeeder.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). boyarsh ocrfeeder-0.7.9-alt4.noarch freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/ocrfeeder.desktop: error: value "0.5" for key "Version" in group "Desktop Entry" is not a known version boyarsh opendbx-1.4.3-alt1.2.qa2.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 boyarsh openresolv-host2cat-1.01-alt6.x86_64 invalid-url warn Package has invalid Url:. It looks like a protocol part (http:,ftp:,etc.) is missing. boyarsh os-prober-1.74-alt1.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/os-prober boyarsh owncloud-3rdparty-7.0.9-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package owncloud8-3rdparty-8.0.9-alt1.noarch, for example, /var/www/webapps/owncloud/3rdparty/composer.json (346 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. boyarsh owncloud-apps-7.0.9-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package owncloud8-apps-8.0.9-alt1.noarch, for example, /var/www/webapps/owncloud/apps/external/ajax/setsites.php (46 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. boyarsh owncloud8-3rdparty-8.0.9-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package owncloud-3rdparty-7.0.9-alt1.noarch, for example, /var/www/webapps/owncloud/3rdparty/composer.json (346 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. boyarsh owncloud8-apache2-8.0.9-alt1.noarch altlinux-policy-obsolete-httpd2-reload info This package contains httpd2 restart/reload calls in its post/un scripts. But those calls are deprecated by httpd2.filetrigger that activates by files in /etc/httpd2/ or %_libdir/apache2/modules/. It should be safe to remove those calls and rely on the filetrigger instead. boyarsh owncloud8-apps-8.0.9-alt1.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package owncloud-apps-7.0.9-alt1.noarch, for example, /var/www/webapps/owncloud/apps/external/ajax/setsites.php (46 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. boyarsh paxctl-0.9-alt1.x86_64 missing-url info Missing Url: in a package. boyarsh paxctl-debuginfo-0.9-alt1.x86_64 missing-url info Missing Url: in a package. boyarsh pyneighborhood-settings-desktop-0.1-alt1.noarch missing-url info Missing Url: in a package. boyarsh remount_rw-0.6-alt1.noarch 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. boyarsh remount_rw-0.6-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /etc/rc.d/init.d/remount_rw /etc/rc.d/init.d/livecd-save-state boyarsh remount_rw-0.6-alt1.noarch init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. boyarsh remount_rw-0.6-alt1.noarch init-condrestart warn /etc/rc.d/init.d/remount_rw: missing condrestart target. Note: alt-specific script %_sbindir/post_service (used in %post_service macro) depends on condrestart. It is wise to add condrestart anyway./etc/rc.d/init.d/remount_rw: missing condstop target. Note: alt-specific script %_sbindir/preun_service (used in %preun_service macro) depends on condstop. It is wise to add condstop anyway. boyarsh remount_rw-0.6-alt1.noarch init-lsb warn /etc/rc.d/init.d/livecd-save-state: not systemd compatible: lsb init header missing and livecd-save-state.service is not present. /etc/rc.d/init.d/remount_rw: strange executable: neither lsb header nor chkconfig header aren't found. See http://www.altlinux.org/Services_Policy for details. boyarsh remount_rw-0.6-alt1.noarch missing-url info Missing Url: in a package. boyarsh settime-rfc867-0.4-alt4.noarch init-lsb warn /etc/rc.d/init.d/settime-rfc867: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. boyarsh settime-rfc867-0.4-alt4.noarch missing-url info Missing Url: in a package. boyarsh spt7-test-scripts-1.4-alt1.x86_64 missing-url info Missing Url: in a package. boyarsh spt7-test-scripts-1.4-alt1.x86_64 rpm-package-is-obsoleted warn The package is obsoleted by the package altsp-test-scripts-1.0-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 altsp-test-scripts-1.0-alt1.x86_64 to remove Obsoletes: tag. boyarsh spt7-test-scripts-debuginfo-1.4-alt1.x86_64 missing-url info Missing Url: in a package. boyarsh squid-conf-host2cat-1.01-alt6.x86_64 invalid-url warn Package has invalid Url:. It looks like a protocol part (http:,ftp:,etc.) is missing. boyarsh system-config-printer-1.5.11-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. boyarsh system-config-printer-1.5.11-alt2.x86_64 dbus-xml-not-in-devel info file /usr/share/dbus-1/interfaces/org.fedoraproject.Config.Printing.xml is not used in run time. Move it to the -devel subpackage. boyarsh system-config-printer-1.5.11-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/system-config-printer.desktop: hint: value "System;Settings;HardwareSettings;Printing;GTK;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu boyarsh system-config-printer-udev-1.5.11-alt2.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/system-config-printer.conf to \%_tmpfilesdir/. boyarsh trsec-1.0-alt2.x86_64 missing-url info Missing Url: in a package. boyarsh trsec-debuginfo-1.0-alt2.x86_64 missing-url info Missing Url: in a package. boyarsh volumes-profile-centaurus-0.11-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-cliff-server-0.14-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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.1-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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.7.4-alt1.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.
File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4-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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.4-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. boyarsh volumes-profile-cliff-server-0.14-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-centaurus-0.11-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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-jeos-0.1-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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-kdesktop-0.7.4-alt1.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.
File /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-lite-0.4-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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-master-0.2-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 /usr/share/install2/initinstall.d/10-vm-profile.sh conflicts with the package volumes-profile-regular-0.4-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. boyarsh xorg-conf-right-click-ungrab-0.1-alt1.noarch missing-url info Missing Url: in a package. boyarsh zram-swap-0.2-alt4.noarch init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. boyarsh zram-swap-0.2-alt4.noarch init-lsb fail /etc/rc.d/init.d/zram-swap: not systemd compatible: lsb init header missing and zram-swap.service is not present. See http://www.altlinux.org/Services_Policy for details. boyarsh zram-swap-0.2-alt4.noarch missing-url info Missing Url: in a package. cas 1c-preinstall-full-8.3-alt11.noarch requires-microsoft-fonts-ttf warn Free Software packages should not require @ fonts! But dependency on fonts-ttf-ms is found. cas 389-adminutil-1.1.23-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 cas 389-ds-base-1.3.7.1-alt2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/sbin/db2bak cas 389-ds-base-1.3.7.1-alt2.x86_64 init-lsb warn /etc/rc.d/init.d/dirsrv: not systemd compatible: lsb init header missing and dirsrv.service is not present. /etc/rc.d/init.d/dirsrv-snmp: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. cas LibreOffice-still-common-debuginfo-5.4.7.2-alt1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/.build-id/0f/48c7e95d7565d8ce31632d3d187bb119055519 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/0f/48c7e95d7565d8ce31632d3d187bb119055519.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/13/88859e8ef861bbcda5ea73eefe6ef4c28a800a is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/13/88859e8ef861bbcda5ea73eefe6ef4c28a800a.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/15/d54e6e3797d017da38617706b2ea0bf0627a0a is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/15/d54e6e3797d017da38617706b2ea0bf0627a0a.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/25/e5051d1202c5f7f3d80c4bb30f4cf28ad0dba9 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/25/e5051d1202c5f7f3d80c4bb30f4cf28ad0dba9.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/31/8d32f7b9bdb01be4649399c774e00c06fde5de is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/31/8d32f7b9bdb01be4649399c774e00c06fde5de.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/49/61a49fba8b9a9966805179808a17b814cdd262 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/49/61a49fba8b9a9966805179808a17b814cdd262.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/75/265c1fa6a3a4aa7968ad34833fff04ab177b08 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/75/265c1fa6a3a4aa7968ad34833fff04ab177b08.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/77/0815a13a795c26f3e50b4da1bdbf3756473a40 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/77/0815a13a795c26f3e50b4da1bdbf3756473a40.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/84/155ee703c8678e65a044307d6ef184b3aafb37 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/84/155ee703c8678e65a044307d6ef184b3aafb37.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/88/0b7753a4bbd886382a3def64d1ba1253fa0f2f is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/88/0b7753a4bbd886382a3def64d1ba1253fa0f2f.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/8b/053c1b5d2386e6310402694d9529b4533defbc is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/8b/053c1b5d2386e6310402694d9529b4533defbc.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/a0/f1e8ad0cb818882008fd024f4618cdf31e0e21 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/a0/f1e8ad0cb818882008fd024f4618cdf31e0e21.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/a2/52a1af7fb62b941bf3a0a811ff4902dc92d3fe is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/a2/52a1af7fb62b941bf3a0a811ff4902dc92d3fe.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/fc/e03f456364aa66aca1748a9b9fa83e9cfbe053 is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/fc/e03f456364aa66aca1748a9b9fa83e9cfbe053.debug is different from the same symlink in the package LibreOffice-common-debuginfo-6.0.1.1-alt1.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. cas LibreOffice-still-integrated-5.4.7.2-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. cas LibreOffice-still-integrated-5.4.7.2-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/draw.desktop: hint: value "Office;FlowChart;Graphics;2DGraphics;VectorGraphics;X-Red-Hat-Base;X-MandrivaLinux-Office-Drawing;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
desktop-file-validate utility printed the following message(s): /usr/share/applications/math.desktop: hint: value "Office;Spreadsheet;Education;Science;Math;X-Red-Hat-Base;X-MandrivaLinux-Office-Other;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
/usr/share/applications/math.desktop: hint: value "Office;Spreadsheet;Education;Science;Math;X-Red-Hat-Base;X-MandrivaLinux-Office-Other;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas LibreOffice-still-kde4-debuginfo-5.4.7.2-alt1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/.build-id/01/461bfd0bfd4633259d28d1176a105fec5c2cb4 is different from the same symlink in the package LibreOffice-kde4-debuginfo-6.0.1.1-alt1.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.
value of symlink /usr/lib/debug/.build-id/01/461bfd0bfd4633259d28d1176a105fec5c2cb4.debug is different from the same symlink in the package LibreOffice-kde4-debuginfo-6.0.1.1-alt1.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. cas OCE-draw-0.18.3-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/opencascade-draw.desktop: hint: value "ConsoleOnly;Graphics;3DGraphics;DataVisualization;Education;Science;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
/usr/share/applications/opencascade-draw.desktop: hint: value "ConsoleOnly;Graphics;3DGraphics;DataVisualization;Education;Science;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas OCE-foundation-0.18.3-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 cas OCE-modeling-0.18.3-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 cas OCE-ocaf-0.18.3-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 cas OCE-visualization-0.18.3-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 cas alt-test-1.1.4-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/alt-test-functions cas alterator-ca-0.5.5-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/sbin/ca-sko cas alterator-mass-management-0.1.7-alt1.noarch unsafe-tmp-usage-in-scripts fail 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/lib/alterator/backend3/mass-management: $ grep -A5 -B5 /tmp/ /usr/lib/alterator/backend3/mass-management mkdir -p "$TASKS_DIR/task-$number" cat >"$TASKS_DIR/task-$number.yml" <> /tmp/mode.log echo "$(set|grep -a "in_")" >> /tmp/mode.log case "$in_action" in type) write_type_item hostlist hostname-list #write_type_item add_host hostname ;; cas alterator-rd-0.0.3-alt2.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/rd-profile-info /usr/bin/rd-list-profiles cas alterator-rd-freerdp-0.0.3-alt2.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/rd-freerdp cas alterator-rd-rdesktop-0.0.3-alt2.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/rd-rdesktop cas ananas-0.9.5-alt9.src unmet-dependency-build-missing-package fail build dependency kdepim-devel not found. cas ananas-0.9.5-alt9.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libananas.so but just /usr/lib64/libananas.so.1.0.1. According to SharedLibs Policy Draft, symlink /usr/lib64/libananas.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libananas.so to \%files of ananas-0.9.5-alt9.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test. cas ananas-0.9.5-alt9.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/ananas.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). cas ananas-0.9.5-alt9.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas apache2-mod_auth_token-1.0.5-alt1.x86_64 altlinux-policy-obsolete-httpd2-reload info This package contains httpd2 restart/reload calls in its post/un scripts. But those calls are deprecated by httpd2.filetrigger that activates by files in /etc/httpd2/ or %_libdir/apache2/modules/. It should be safe to remove those calls and rely on the filetrigger instead. cas apache2-mod_ngobjweb-3.2.10-alt2.x86_64 altlinux-policy-obsolete-httpd2-reload info This package contains httpd2 restart/reload calls in its post/un scripts. But those calls are deprecated by httpd2.filetrigger that activates by files in /etc/httpd2/ or %_libdir/apache2/modules/. It should be safe to remove those calls and rely on the filetrigger instead. cas apache2-mod_wsgi-4.6.4-alt1.x86_64 altlinux-policy-obsolete-httpd2-reload info This package contains httpd2 restart/reload calls in its post/un scripts. But those calls are deprecated by httpd2.filetrigger that activates by files in /etc/httpd2/ or %_libdir/apache2/modules/. It should be safe to remove those calls and rely on the filetrigger instead. cas appstream-doc-0.12.0-alt1.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. cas aqbanking-5.7.8-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. cas basic256-0.9.6-alt8.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/basic256.desktop: hint: value "Education;Science;ComputerScience;Development;IDE;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
/usr/share/applications/basic256.desktop: hint: value "Education;Science;ComputerScience;Development;IDE;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas basqet-0.2.0-alt2.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/basqet.desktop: error: value "0.2.0" for key "Version" in group "Desktop Entry" is not a known version cas basqet-0.2.0-alt2.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas bleachbit-2.0-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/bleachbit.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). cas bleachbit-2.0-alt1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas blink-qt-3.0.3-alt2.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas branding-school-master-7.0.5-alt2.src requires-ImageMagick info Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell. cas branding-school-master-alterator-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-altlinux-backup-server-alterator-6.0.0-alt3.noarch, but the package branding-altlinux-backup-server-alterator-6.0.0-alt3.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 branding-informika-schoolmaster-alterator-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-alterator-6.0.0-alt47.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. cas branding-school-master-bootloader-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-bootloader-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-bootloader-6.0.0-alt47.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. cas branding-school-master-bootsplash-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-bootsplash-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-bootsplash-6.0.0-alt47.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. cas branding-school-master-graphics-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-graphics-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-graphics-6.0.0-alt47.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. cas branding-school-master-indexhtml-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-indexhtml-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-indexhtml-6.0.0-alt47.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. cas branding-school-master-kde4-settings-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-altlinux-kdesktop-indexhtml-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 /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-informika-schoolmaster-indexhtml-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 /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-junior-indexhtml-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 /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-school-teacher-indexhtml-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 /usr/share/kde4/apps/kio_desktop/DesktopLinks/indexhtml.desktop conflicts with the package branding-xalt-kworkstation-indexhtml-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. cas branding-school-master-kde4-settings-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-kde4-settings-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-kde4-settings-6.0.0-alt47.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. cas branding-school-master-menu-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /usr/share/slinux-style/applications/dropbox.desktop conflicts with the package branding-school-server-menu-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.
There are file conflicts with the package branding-simply-linux-menu-8.2.0-alt1.noarch, for example, /usr/share/slinux-style/applications/Ri-li.desktop (5 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. cas branding-school-master-notes-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn There are file conflicts with the package alt-notes-school-server-4.1-alt3.noarch, for example, /usr/share/alt-notes/license.all.html (4 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. cas branding-school-master-notes-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-notes-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-notes-6.0.0-alt47.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. cas branding-school-master-release-7.0.5-alt2.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 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. cas branding-school-master-release-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-release-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-release-6.0.0-alt47.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. cas branding-school-master-slideshow-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package branding-informika-schoolmaster-slideshow-6.0.0-alt47.noarch, but the package branding-informika-schoolmaster-slideshow-6.0.0-alt47.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. cas branding-school-master-xfce-settings-7.0.5-alt2.noarch rpm-filesystem-conflict-file-file warn File /etc/skel/.gconf/apps/%gconf.xml conflicts with the package livecd-gnome-nowarn-space-0.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.
Files /etc/skel/.config/xfce4/desktop/icons.screen0.rc /etc/skel/.config/xfce4/helpers.rc conflict with the package xfce-settings-lite-school-0.6-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.
There are file conflicts with the package xfce-settings-simple-1.0-alt6.noarch, for example, /etc/skel/.config/xfce4/Xcursor.xrdb (8 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. cas branding-school-master-xfce-settings-7.0.5-alt2.noarch rpm-obsolete-live-package info The package obsoletes the package xfce-settings-lite-1.0-alt7.noarch, but the package xfce-settings-lite-1.0-alt7.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. cas bsc-4.1.0-alt1.qa1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas bup-web-0.29.1-alt1.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts. cas card-actions-1.10-alt7.noarch missing-url info Missing Url: in a package. cas cfdg-fe-v20061127-alt1.qa2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/cfdg-fe.desktop: hint: value item "VectorGraphics" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Graphics;2DGraphics cas chef-doc-12.15.11-alt1.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package asciidoctor-doc-1.5.6.1-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.
There are file conflicts with the package ohai-doc-14.1.5-alt1.noarch, for example, /usr/share/ri/site/Chef/cdesc-Chef.ri (18 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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-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.
Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package ruby-backports-doc-3.7.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.
There are file conflicts with the package ruby-chef-sugar-doc-3.4.0-alt1.noarch, for example, /usr/share/ri/site/Chef/Node/cdesc-Node.ri (4 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.
File /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-cleanroom-doc-1.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.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 /usr/share/ri/site/Win32/cdesc-Win32.ri conflicts with the package ruby-facter-doc-2.0.1-alt2.1.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt2.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/FFI/Pointer/cdesc-Pointer.ri /usr/share/ri/site/FFI/cdesc-FFI.ri conflict with the package ruby-ffi-doc-1.9.23-alt1.2.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.4.noarch, for example, /usr/share/ri/site/FalseClass/cdesc-FalseClass.ri (5 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.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-http-cookie-doc-1.0.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.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 /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt1.4.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 /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-mail-doc-2.7.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.
Files /usr/share/ri/site/String/cdesc-String.ri /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflict with the package ruby-mcollective-client-doc-2.11.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mechanize-doc-0.9.3-alt1.3.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-mini_portile2-doc-2.3.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 /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-mongo-doc-2.5.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 /usr/share/ri/site/Symbol/cdesc-Symbol.ri conflicts with the package ruby-msgpack-doc-1.1.0-alt1.4.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.
Files /usr/share/ri/site/Net/HTTP/cdesc-HTTP.ri /usr/share/ri/site/Net/cdesc-Net.ri conflict with the package ruby-multipart-post-doc-2.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 /usr/share/ri/site/Net/cdesc-Net.ri conflicts with the package ruby-net-dhcp-doc-1.3.2-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 /usr/share/ri/site/Net/SSH/cdesc-SSH.ri conflicts with the package ruby-net-ssh-doc-4.2.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.
There are file conflicts with the package ruby-net-ssh-multi-doc-1.2.0-alt1.1.noarch, for example, /usr/share/ri/site/Net/SSH/Multi/Server/busy%3f-i.ri (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.6.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.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.
Files /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-rspec-core-doc-3.7.1-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 /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-expectations-doc-3.7.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 /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-mocks-doc-3.7.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 /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-puppet-doc-0.1.6-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 /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflicts with the package ruby-rspec-support-doc-3.7.1-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.
There are file conflicts with the package ruby-sequel-doc-5.5.0-alt1.noarch, for example, /usr/share/ri/site/FalseClass/cdesc-FalseClass.ri (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/Gem/cdesc-Gem.ri /usr/share/ri/site/RSpec/Core/cdesc-Core.ri /usr/share/ri/site/RSpec/cdesc-RSpec.ri conflict with the package ruby-spec_helper-doc-1.0.1-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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.10-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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.6.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. cas cqrlog-2.2.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. cas cqrlog-2.2.0-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/cqrlog.desktop: hint: value item "Database" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Office, or Development, or AudioVideo
/usr/share/applications/cqrlog.desktop: hint: value item "HamRadio" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Network, or Audio cas cuneiform-qt-0.1.2-alt1.qa1.src beehive-log-unpackaged-files-found-x86_64 info warning: Installed (but unpackaged) file(s) found:
/usr/share/pixmaps/cuneiform-qt.png cas cuneiform-qt-0.1.2-alt1.qa1.src requires-ImageMagick info Dependency on ImageMagick (compat package) found. It probably should be replaced with more specific dependency like /usr/bin/convert or ImageMagick-tools, or it can be already autodetected by findreq-shell. cas cuneiform-qt-0.1.2-alt1.qa1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/cuneiform-qt.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). cas cuneiform-qt-0.1.2-alt1.qa1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/cuneiform-qt.desktop: error: file contains key "GenericName[u?]" in group "Desktop Entry", but key names must contain only the characters A-Za-z0-9- (they may have a "[LOCALE]" postfix)
/usr/share/applications/cuneiform-qt.desktop: warning: value "Cuneiform OCR" for key "Comment" in group "Desktop Entry" looks redundant with value "Cuneiform OCR" of key "GenericName"
/usr/share/applications/cuneiform-qt.desktop: warning: value "????????????? ???????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "????????????? ???????" of key "GenericName[ru]" cas davmail-4.8.5-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/davmail.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). cas disable-usb-autosuspend-1.1-alt1.noarch missing-url info Missing Url: in a package. cas eas-0.2.2-alt0.7cvs20070731.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/eas.desktop: warning: value "E/AS Enterprise Automation System" for key "Comment" in group "Desktop Entry" looks redundant with value "E/AS Enterprise Automation System" of key "GenericName" cas eas-server-0.2.2-alt0.7cvs20070731.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. cas eas-server-0.2.2-alt0.7cvs20070731.x86_64 init-condrestart warn /etc/rc.d/init.d/easd: missing condstop target. Note: alt-specific script %_sbindir/preun_service (used in %preun_service macro) depends on condstop. It is wise to add condstop anyway. cas eas-server-0.2.2-alt0.7cvs20070731.x86_64 init-lsb fail /etc/rc.d/init.d/easd: not systemd compatible: lsb init header missing and easd.service is not present. See http://www.altlinux.org/Services_Policy for details. cas easypaint-0.6.0-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas eggdrop-1.8.3-alt1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. cas eggdrop-1.8.3-alt1.x86_64 init-lsb fail /etc/rc.d/init.d/eggdrop: not systemd compatible: lsb init header missing and eggdrop.service is not present. See http://www.altlinux.org/Services_Policy for details. cas eggdrop-1.8.3-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. cas eigen3-docs-3.3.4-alt4.x86_64 arch-dep-package-consists-of-usr-share info The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. cas erubis-doc-2.7.0-alt3.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-backports-doc-3.7.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 /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-em-synchrony-doc-1.0.6-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 /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-highline-doc-1.7.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 /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-json-pure-doc-2.1.0-alt1.4.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 /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package ruby-polyglot-doc-0.3.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 /usr/share/ri/site/Kernel/cdesc-Kernel.ri conflicts with the package yajl-ruby-doc-1.4.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. cas eviacam-2.0.1-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. cas eviacam-2.0.1-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas fldigi-4.0.16-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas freebasic-1.05.0-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. cas freecad-0.17-alt3.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/freecad.desktop: warning: value "??????? ??????????????????? ??????????????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "??????? ??????????????????? ??????????????" of key "GenericName[ru]"
/usr/share/applications/freecad.desktop: hint: value "Graphics;Science;Education;Engineering;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
/usr/share/applications/freecad.desktop: hint: value "Graphics;Science;Education;Engineering;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas freecad-0.17-alt3.x86_64 uncompressed-manpages info Package contains uncompressed manual pages. cas freehep-io-2.2.2-alt3.src unmet-dependency-build-missing-package fail build dependency maven-shared-artifact-resolver not found. cas freehep-vectorgraphics-2.4-alt1.src unmet-dependency-build-missing-package fail build dependency maven-shared-artifact-resolver not found. cas gambas3-runtime-3.10.0-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas gamine-1.5-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. cas gamine-1.5-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gamine.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). cas gamine-1.5-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/gamine.desktop: error: file contains key "comment" in group "Desktop Entry", but keys extending the format should start with "X-"
/usr/share/applications/gamine.desktop: error: file contains key "comment" in group "Desktop Entry", but keys extending the format should start with "X-" cas gcompris-15.10-alt6.1.x86_64 arch-dep-package-has-big-usr-share info The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. cas gcompris-15.10-alt6.1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/gcompris.desktop: hint: value "Education;Game;KidsGame;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
desktop-file-validate utility printed the following message(s): /usr/share/applications/gcompris-edit.desktop: warning: value "????? ??????" for key "Comment[ar]" in group "Desktop Entry" looks redundant with value "????? ??????" of key "Name[ar]"
/usr/share/applications/gcompris-edit.desktop: warning: value "Alministraci?n de gcompris" for key "Comment[ast]" in group "Desktop Entry" looks redundant with value "Alministraci?n de GCompris" of key "Name[ast]"
/usr/share/applications/gcompris-edit.desktop: warning: value "?????????????? ?? GCompris" for key "Comment[bg]" in group "Desktop Entry" looks redundant with value "?????????????? ?? GCompris" of key "Name[bg]"
/usr/share/applications/gcompris-edit.desktop: warning: value "GCompris-Administration" for key "Comment[de]" in group "Desktop Entry" looks redundant with value "GCompris-Administration" of key "Name[de]"
/usr/share/applications/gcompris-edit.desktop: warning: value "Administraci?n de gcompris" for key "Comment[es]" in group "Desktop Entry" looks redundant with value "Administraci?n de GCompris" of key "Name[es]"
/usr/share/applications/gcompris-edit.desktop: warning: value "GCompris-en administrazioa" for key "Comment[eu]" in group "Desktop Entry" looks redundant with value "GCompris-en administrazioa" of key "Name[eu]"
/usr/share/applications/gcompris-edit.desktop: warning: value "Administration de GCompris" for key "Comment[fr]" in group "Desktop Entry" looks redundant with value "Administration de GCompris" of key "Name[fr]"
/usr/share/applications/gcompris-edit.desktop: warning: value "GCompris administravimas" for key "Comment[lt]" in group "Desktop Entry" looks redundant with value "GCompris administravimas" of key "Name[lt]"
/usr/share/applications/gcompris-edit.desktop: warning: value "GCompris administr?cija" for key "Comment[lv]" in group "Desktop Entry" looks redundant with value "GCompris administr?cija" of key "Name[lv]"
/usr/share/applications/gcompris-edit.desktop: warning: value "Administra??o do GCompris" for key "Comment[pt]" in group "Desktop Entry" looks redundant with value "Administra??o do GCompris" of key "Name[pt]"
/usr/share/applications/gcompris-edit.desktop: warning: value "Administra??o do GCompris" for key "Comment[pt_BR]" in group "Desktop Entry" looks redundant with value "Administra??o do GCompris" of key "Name[pt_BR]"
/usr/share/applications/gcompris-edit.desktop: warning: value "gcompris ????" for key "Comment[zh_HK]" in group "Desktop Entry" looks redundant with value "GCompris ????" of key "Name[zh_HK]"
/usr/share/applications/gcompris-edit.desktop: warning: value "gcompris ????" for key "Comment[zh_TW]" in group "Desktop Entry" looks redundant with value "GCompris ????" of key "Name[zh_TW]"
/usr/share/applications/gcompris-edit.desktop: hint: value "Settings;Game;KidsGame;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas gdesklets-0.36.3-alt4.src altlinux-policy-obsolete-buildreq warn Build dependency on menu-devel is obsolete and should be dropped to get rid of menu-devel package. cas gdesklets-0.36.3-alt4.src 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. cas girar-utils-1.5.9-alt1.noarch checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/girar-show cas girar-utils-1.5.9-alt1.noarch missing-url info Missing Url: in a package. cas gmanedit-0.4.2-alt3.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gmanedit.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). cas gmanedit-0.4.2-alt3.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/gmanedit.desktop: warning: file contains lines that are not UTF-8 encoded. There is no guarantee the validator will correctly work.
[Invalid UTF-8] /usr/share/applications/gmanedit.desktop: error: value "Editor de p\xe1ginas man de GNOME" for locale string key "Comment[es]" in group "Desktop Entry" contains invalid UTF-8 characters, locale string values should be encoded in UTF-8
[Invalid UTF-8] /usr/share/applications/gmanedit.desktop: error: value "Editor de p\xe1xinas man de GNOME" for locale string key "Comment[gl]" in group "Desktop Entry" contains invalid UTF-8 characters, locale string values should be encoded in UTF-8 cas gmanedit-0.4.2-alt3.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas gnome-libs-1.4.2-alt11.3.qa2.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. cas gnome-libs-1.4.2-alt11.3.qa2.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 cas gnome-libs-devel-1.4.2-alt11.3.qa2.x86_64 checkbashisms experimental checkbashisms utility found possible bashisms in: /usr/bin/gnome-config cas gnucash-2.6.20-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. cas gost-crypto-gui-0.3-alt0.5.a.git4b7a47a.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/gost-crypto-gui.desktop: hint: value "Qt;HardwareSettings;Settings;System;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas gost-crypto-gui-0.3-alt0.5.a.git4b7a47a.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas gpaint-0.3.3-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/gpaint.desktop: warning: boolean key "Terminal" in group "Desktop Entry" has value "0", which is deprecated: boolean values should be "false" or "true" cas gpaint-0.3.3-alt2.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas gpointing-device-settings-1.5.1-alt5.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gpointing-device-settings.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). cas gpointing-device-settings-1.5.1-alt5.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/gpointing-device-settings.desktop: hint: value item "GNOME" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: GTK cas gpointing-device-settings-1.5.1-alt5.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas gpointing-device-settings-1.5.1-alt5.x86_64 rpm-obsolete-live-package info The package obsoletes the package gsynaptics-0.9.16-alt3.qa1.x86_64, but the package gsynaptics-0.9.16-alt3.qa1.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. cas gpsim-0.30.0-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas grass-7.4.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. cas grass-7.4.0-alt1.x86_64 buildroot fail found paths to buildroot: /usr/lib64/grass-7.4.0/demolocation/.grassrc74: GISDBASE: /usr/src/tmp/grass-buildroot/usr/grass-7.4.0 cas grass-7.4.0-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/grass.desktop: hint: value "Education;Science;Geoscience;Geography;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas grub-customizer-5.0.6-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/grub-customizer.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). cas grub-customizer-5.0.6-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/grub-customizer.desktop: hint: value "System;Settings;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas guake-3.2.1-alt1.noarch freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/guake-prefs.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). cas guake-3.2.1-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/guake.desktop: hint: value "GNOME;GTK;System;Utility;TerminalEmulator;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas guake-3.2.1-alt1.noarch freedesktop-desktop-file-proposed-patch warn Please, apply the repocop patch for /usr/share/applications/guake.desktop. cas guake-3.2.1-alt1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas iceb-18.5-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/i_admint.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt).
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/startxbu.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). cas iceb-18.5-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/i_admint.desktop: warning: value "Ukrainian bookkeeping suite of programs iceB" for key "Comment" in group "Desktop Entry" looks redundant with value "Ukrainian bookkeeping suite of programs iceB" of key "Name"
desktop-file-validate utility printed the following message(s): /usr/share/applications/startxbu.desktop: warning: value "Ukrainian bookkeeping suite of programs iceB" for key "Comment" in group "Desktop Entry" looks redundant with value "Ukrainian bookkeeping suite of programs iceB" of key "Name" cas iceb-18.5-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas iceb-18.5-alt1.x86_64 rpm-filesystem-conflict-file-file warn File /usr/bin/spec conflicts with the package python-module-spec-1.4.0-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives. cas icon-theme-bespin-0.1.0.1658-alt1.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. cas installer-distro-school-server-stage2-7.0-alt9.noarch rpm-filesystem-conflict-file-file warn Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-distro-altlinux-desktop-stage2-8.1.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.
Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps conflict with the package installer-distro-altlinux-generic-stage2-7.0.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.
Files /usr/share/install2/alterator-menu/module-expert-list /usr/share/install2/alterator-menu/module-order-list conflict with the package installer-distro-altlinux-server-stage2-7.0.2-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.
Files /usr/share/install2/alterator-menu/module-order-list /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/20-alterator-menu.sh conflict with the package installer-distro-backup-server-stage2-6.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.
There are file conflicts with the package installer-distro-centaurus-stage2-8.2-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-chainmail-stage2-3.0.0-alt8.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (7 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-desktop-stage2-5.0-alt23.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-junior-stage2-8.1-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-lxdesktop-stage2-6.0-alt5.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (6 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-office-server-stage2-5.0-alt28.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-server-light-stage2-8.0-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-simply-linux-stage2-8.3-alt1.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-tablet-stage2-6.0-alt3.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-token-desktop-stage2-0.1.1-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (4 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
There are file conflicts with the package installer-distro-workbench-stage2-5.0-alt2.noarch, for example, /usr/share/install2/alterator-menu/module-expert-list (5 file conflicts in total). Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/install2/installer-steps /usr/share/install2/preinstall.d/80-setup-user-groups conflict with the package installer-office-desktop-stage2-5.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.
Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-lite-stage2-0.2-alt1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/install2/installer-steps /usr/share/install2/postinstall.d/01-remove-installer-server-pkgs.sh conflict with the package installer-server-stage2-0.2-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. cas jackbeat-0.7.6-alt2.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/jackbeat.desktop: error: value "0.7.6" for key "Version" in group "Desktop Entry" is not a known version
/usr/share/applications/jackbeat.desktop: error: (will be fatal in the future): value item "Audio" in key "Categories" in group "Desktop Entry" requires another category to be present among the following categories: AudioVideo
/usr/share/applications/jackbeat.desktop: hint: value item "Midi" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: AudioVideo;Audio
/usr/share/applications/jackbeat.desktop: hint: value item "Sequencer" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: AudioVideo;Audio
/usr/share/applications/jackbeat.desktop: error: value "Audio;Midi;Sequencer;X-Alsa;X-Jack;Gtk;" for key "Categories" in group "Desktop Entry" contains an unregistered value "Gtk"; values extending the format should start with "X-" cas jitsi-2.11.5553-alt2.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas juffed-0.10-alt2.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libjuff.so but just /usr/lib64/libjuff.so.0.10. According to SharedLibs Policy Draft, symlink /usr/lib64/libjuff.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libjuff.so to \%files of juffed-0.10-alt2.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libjuffed-engine-qsci.so but just /usr/lib64/libjuffed-engine-qsci.so.0.10. According to SharedLibs Policy Draft, symlink /usr/lib64/libjuffed-engine-qsci.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libjuffed-engine-qsci.so to \%files of juffed-0.10-alt2.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test. cas juffed-0.10-alt2.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/juffed.desktop: warning: value "Advanced text editor" for key "Comment" in group "Desktop Entry" looks redundant with value "Advanced text editor" of key "GenericName"
/usr/share/applications/juffed.desktop: warning: value "??????????? ????????? ????????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "??????????? ????????? ????????" of key "GenericName[ru]"
/usr/share/applications/juffed.desktop: warning: value "Zaawansowany edytor tekstu" for key "Comment[pl]" in group "Desktop Entry" looks redundant with value "Zaawansowany edytor tekstu" of key "GenericName[pl]"
/usr/share/applications/juffed.desktop: warning: value "Ein erweiterter Texteditor" for key "Comment[de]" in group "Desktop Entry" looks redundant with value "Ein erweiterter Texteditor" of key "GenericName[de]"
/usr/share/applications/juffed.desktop: warning: value "Un avanc? ?diteur de texte" for key "Comment[fr]" in group "Desktop Entry" looks redundant with value "Un avanc? ?diteur de texte" of key "GenericName[fr]"
/usr/share/applications/juffed.desktop: warning: value "????????" for key "Comment[zh_CN]" in group "Desktop Entry" looks redundant with value "????????" of key "GenericName[zh_CN]"
/usr/share/applications/juffed.desktop: warning: value "Pokro?il? textov? editor" for key "Comment[sk]" in group "Desktop Entry" looks redundant with value "Pokro?il? textov? editor" of key "GenericName[sk]" cas juffed-0.10-alt2.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas juffed-0.10-alt2.x86_64 missing-url info Missing Url: in a package. cas juffed-debuginfo-0.10-alt2.x86_64 missing-url info Missing Url: in a package. cas juffed-devel-0.10-alt2.noarch missing-url info Missing Url: in a package. cas kbookocr-2.1.0-alt2.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/KBookocr.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). cas kbookocr-2.1.0-alt2.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/KBookocr.desktop: error: value "1.4.1" for key "Version" in group "Desktop Entry" is not a known version cas kde4-styles-bespin-0.1.0.1658-alt1.src specfile-macros-get_dep-is-deprecated experimental Versioned Requires: foo >= %{get_dep something} using %get_dep and %get_version macros on a library are deprecated by set:versions. You probably should drop %get_dep/%get_version Requires: to avoid RPM database pollution. cas kde4-styles-bespin-kdm-0.1.0.1658-alt1.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. cas kde4-styles-bespin-ksplash-0.1.0.1658-alt1.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. cas kdvdcreator-0.3.2-alt1.x86_64 desktop-exec-fill-code warn kdvdcreator.desktop: found MimeType= entry, but to handle it properly you have to declare one of %f,%F,%u,%U in Exec= entry. Note that %m is deprecated. See http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-1.0.html#exec-variables cas kdvdcreator-0.3.2-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/kde4/kdvdcreator.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated
/usr/share/applications/kde4/kdvdcreator.desktop: warning: value "Qt;KDE;Application;AudioVideo;Multimedia" for key "Categories" in group "Desktop Entry" contains a deprecated value "Application"
/usr/share/applications/kde4/kdvdcreator.desktop: error: value "Qt;KDE;Application;AudioVideo;Multimedia" for key "Categories" in group "Desktop Entry" contains an unregistered value "Multimedia"; values extending the format should start with "X-" cas kmymoney-5.0.1-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. cas kmymoney-5.0.1-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Personal Finance Manager" for key "Comment" in group "Desktop Entry" looks redundant with value "Personal Finance Manager" of key "GenericName"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "???? ?????? ?????" for key "Comment[ar]" in group "Desktop Entry" looks redundant with value "???? ?????? ?????" of key "GenericName[ar]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Li?nni upravlja? finansija" for key "Comment[bs]" in group "Desktop Entry" looks redundant with value "Li?nni upravlja? finansija" of key "GenericName[bs]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Gestor de les finances personals" for key "Comment[ca]" in group "Desktop Entry" looks redundant with value "Gestor de les finances personals" of key "GenericName[ca]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Gestor de les finances personals" for key "Comment[ca@valencia]" in group "Desktop Entry" looks redundant with value "Gestor de les finances personals" of key "GenericName[ca@valencia]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Styring af privat?konomi" for key "Comment[da]" in group "Desktop Entry" looks redundant with value "Styring af privat?konomi" of key "GenericName[da]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Pers?nliche Finanzenverwaltung" for key "Comment[de]" in group "Desktop Entry" looks redundant with value "Pers?nliche Finanzenverwaltung" of key "GenericName[de]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "?????????? ???????????? ???????????" for key "Comment[el]" in group "Desktop Entry" looks redundant with value "?????????? ???????????? ???????????" of key "GenericName[el]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Personal Finance Manager" for key "Comment[en_GB]" in group "Desktop Entry" looks redundant with value "Personal Finance Manager" of key "GenericName[en_GB]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Gestor de finanzas personales" for key "Comment[es]" in group "Desktop Entry" looks redundant with value "Gestor de finanzas personales" of key "GenericName[es]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Isiklike rahaasjade haldur" for key "Comment[et]" in group "Desktop Entry" looks redundant with value "Isiklike rahaasjade haldur" of key "GenericName[et]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Finantza pertsonalen kudeatzailea" for key "Comment[eu]" in group "Desktop Entry" looks redundant with value "Finantza pertsonalen kudeatzailea" of key "GenericName[eu]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Henkil?kohtainen taloushallinta" for key "Comment[fi]" in group "Desktop Entry" looks redundant with value "Henkil?kohtainen taloushallinta" of key "GenericName[fi]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Gestionnaire de finances personnelles" for key "Comment[fr]" in group "Desktop Entry" looks redundant with value "Gestionnaire de finances personnelles" of key "GenericName[fr]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Xestor das finanzas persoais" for key "Comment[gl]" in group "Desktop Entry" looks redundant with value "Xestor das finanzas persoais" of key "GenericName[gl]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Szem?lyes p?nz?gyi kezel?" for key "Comment[hu]" in group "Desktop Entry" looks redundant with value "Szem?lyes p?nz?gyi kezel?" of key "GenericName[hu]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Gestore delle finanze personali" for key "Comment[it]" in group "Desktop Entry" looks redundant with value "Gestore delle finanze personali" of key "GenericName[it]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "?????? ????? ?????????" for key "Comment[kk]" in group "Desktop Entry" looks redundant with value "?????? ????? ?????????" of key "GenericName[kk]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Asmenini? finans? tvarkytuv?" for key "Comment[lt]" in group "Desktop Entry" looks redundant with value "Asmenini? finans? tvarkytuv?" of key "GenericName[lt]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "???????? ????? ??????????" for key "Comment[mr]" in group "Desktop Entry" looks redundant with value "???????? ????? ??????????" of key "GenericName[mr]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Geldsaken plegen" for key "Comment[nds]" in group "Desktop Entry" looks redundant with value "Geldsaken plegen" of key "GenericName[nds]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Zarz?dzanie finansami osobistymi" for key "Comment[pl]" in group "Desktop Entry" looks redundant with value "Zarz?dzanie finansami osobistymi" of key "GenericName[pl]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Gestor de Finan?as Pessoais" for key "Comment[pt]" in group "Desktop Entry" looks redundant with value "Gestor de Finan?as Pessoais" of key "GenericName[pt]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Gerenciador de Finan?as Pessoais" for key "Comment[pt_BR]" in group "Desktop Entry" looks redundant with value "Gerenciador de Finan?as Pessoais" of key "GenericName[pt_BR]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "???? ????????" for key "Comment[ru]" in group "Desktop Entry" looks redundant with value "???? ????????" of key "GenericName[ru]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Osobn? mana??r financi?" for key "Comment[sk]" in group "Desktop Entry" looks redundant with value "Osobn? mana??r financi?" of key "GenericName[sk]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Hemekonomihantering" for key "Comment[sv]" in group "Desktop Entry" looks redundant with value "Hemekonomihantering" of key "GenericName[sv]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "Ki?isel Finans Y?neticisi" for key "Comment[tr]" in group "Desktop Entry" looks redundant with value "Ki?isel Finans Y?neticisi" of key "GenericName[tr]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "??????? ???????? ????????" for key "Comment[ug]" in group "Desktop Entry" looks redundant with value "??????? ???????? ????????" of key "GenericName[ug]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "???????? ????????? ?????????" for key "Comment[uk]" in group "Desktop Entry" looks redundant with value "???????? ????????? ?????????" of key "GenericName[uk]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "xxPersonal Finance Managerxx" for key "Comment[x-test]" in group "Desktop Entry" looks redundant with value "xxPersonal Finance Managerxx" of key "GenericName[x-test]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "???????" for key "Comment[zh_CN]" in group "Desktop Entry" looks redundant with value "???????" of key "GenericName[zh_CN]"
/usr/share/applications/kf5/org.kde.kmymoney.desktop: warning: value "????????" for key "Comment[zh_TW]" in group "Desktop Entry" looks redundant with value "????????" of key "GenericName[zh_TW]" cas kontakter-0.2-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas kontakter-server-0.2-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas ktoblzcheck-1.49-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 cas laptop-mode-tools-1.72.2-alt1.noarch executable-manpage fail Manual pages are not meant to be executed. cas laptop-mode-tools-1.72.2-alt1.noarch uncompressed-manpages info Package contains uncompressed manual pages. cas lazarus-1.8.2-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/lazarus.desktop: error: file contains group "Property::X-KDE-NativeExtension", but groups extending the format should start with "X-" cas lazarus-1.8.2-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas libarpack-ng-devel-3.5.0-alt1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libarpack.so is different from the same symlink in the package libarpack-devel-96-alt11.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. cas libchipcard-tools-5.0.4-alt3.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. cas libchipcard-tools-5.0.4-alt3.x86_64 init-lsb fail /etc/rc.d/init.d/chipcardd: not systemd compatible: lsb init header missing and chipcardd.service is not present. See http://www.altlinux.org/Services_Policy for details. cas libcwiid-utils-0.6.00-alt2.20100505gitfadf11e.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/wmgui.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). cas libcwiid-utils-0.6.00-alt2.20100505gitfadf11e.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/wmgui.desktop: hint: value "GTK;Utility;System;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas libgnomeprintui-2.18.6-alt2.x86_64 big-changelog info Package contains big ChangeLog. Gzip it. cas libgnucash-2.6.20-alt1.x86_64 altlinux-policy-shared-lib-contains-devel-so info SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libgnc-backend-sql.so but just /usr/lib64/libgnc-backend-sql.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-backend-sql.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libgnc-backend-sql.so to \%files of libgnucash-2.6.20-alt1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libgnc-backend-xml-utils.so but just /usr/lib64/libgnc-backend-xml-utils.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-backend-xml-utils.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libgnc-backend-xml-utils.so to \%files of libgnucash-2.6.20-alt1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libgnc-business-ledger.so but just /usr/lib64/libgnc-business-ledger.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-business-ledger.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libgnc-business-ledger.so to \%files of libgnucash-2.6.20-alt1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libgnc-core-utils.so but just /usr/lib64/libgnc-core-utils.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-core-utils.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libgnc-core-utils.so to \%files of libgnucash-2.6.20-alt1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libgnc-gnome.so but just /usr/lib64/libgnc-gnome.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-gnome.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libgnc-gnome.so to \%files of libgnucash-2.6.20-alt1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libgnc-module.so but just /usr/lib64/libgnc-module.so.0.0.0. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-module.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libgnc-module.so to \%files of libgnucash-2.6.20-alt1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test.
SharedLibs Policy Draft violation: Shared Lib package should not contain symlink /usr/lib64/libgnc-qof.so but just /usr/lib64/libgnc-qof.so.1.0.4. According to SharedLibs Policy Draft, symlink /usr/lib64/libgnc-qof.so should be placed in a special subpackage named lib-devel. If you have already packaged this symlink in lib-devel, just append \%exclude /usr/lib64/libgnc-qof.so to \%files of libgnucash-2.6.20-alt1.x86_64. Otherwise, move the symlink into the subpackage lib-devel. There is a known exception for case the .so file is not a shared lib but a plugin that is never directly linked with. Please report such a case to repocop test. cas libgnucash-devel-2.6.20-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. cas libgpsim-0.30.0-alt1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it. cas libgtk-engines-default-common-2.20.2-alt3.1.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. cas libgtk-engines-default-common-2.20.2-alt3.1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it. cas libisdn-devel-0.0.1-alt1.qa1.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. cas libleatherman-1.4.1-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. cas libmapi-2.4-alt24.zentyal23.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libmapi.so.0 is different from the same symlink in the package zarafa-client-7.1.15-alt19.S1.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. cas libmapi-debuginfo-2.4-alt24.zentyal23.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libmapi.so.0.debug is different from the same symlink in the package zarafa-client-debuginfo-7.1.15-alt19.S1.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. cas libpacemaker-devel-1.1.18-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. cas libpacemaker-devel-1.1.18-alt1.x86_64 unsafe-tmp-usage-in-scripts fail 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/pacemaker/tests/cli/regression.sh: $ grep -A5 -B5 /tmp/ /usr/share/pacemaker/tests/cli/regression.sh desc="Allow CIB erasure with --force" cmd="cibadmin -E --force" test_assert 0 desc="Query CIB" cmd="cibadmin -Q > /tmp/$$.existing.xml" test_assert 0 desc="Set cluster option" cmd="crm_attribute -n cluster-delay -v 60s" test_assert 0 -- desc="Query new cluster option" cmd="cibadmin -Q -o crm_config | grep cib-bootstrap-options-cluster-delay" test_assert 0 desc="Query cluster options" cmd="cibadmin -Q -o crm_config > /tmp/$$.opt.xml" test_assert 0 desc="Set no-quorum policy" cmd="crm_attribute -n no-quorum-policy -v ignore" test_assert 0 -- desc="Delete nvpair" cmd="cibadmin -D -o crm_config --xml-text ''" test_assert 0 desc="Create operaton should fail" cmd="cibadmin -C -o crm_config --xml-file /tmp/$$.opt.xml" test_assert 76 desc="Modify cluster options section" cmd="cibadmin -M -o crm_config --xml-file /tmp/$$.opt.xml" test_assert 0 desc="Query updated cluster option" cmd="cibadmin -Q -o crm_config | grep cib-bootstrap-options-cluster-delay" test_assert 0 -- cmd="cibadmin -Q | cibadmin -5 -p 2>&1 > /dev/null" test_assert 0 # This update will fail because it has version numbers desc="Replace operation should fail" cmd="cibadmin -R --xml-file /tmp/$$.existing.xml" test_assert 205 desc="Default standby value" cmd="crm_standby -N node1 -G" test_assert 0 -- desc="Create a resource meta attribute in the parent" cmd="crm_resource -r test-clone --meta -p is-managed -v true --force" test_assert 0 desc="Copy resources" cmd="cibadmin -Q -o resources > /tmp/$$.resources.xml" test_assert 0 0 desc="Delete resource paremt meta attribute (force)" cmd="crm_resource -r test-clone --meta -d is-managed --force" test_assert 0 desc="Restore duplicates" cmd="cibadmin -R -o resources --xml-file /tmp/$$.resources.xml" test_assert 0 desc="Delete resource child meta attribute" cmd="crm_resource -r test-primitive --meta -d is-managed" test_assert 0 rm -f /tmp/$$.existing.xml /tmp/$$.resources.xml } function test_dates() { desc="2014-01-01 00:30:00 - 1 Hour" cmd="iso8601 -d '2014-01-01 00:30:00Z' -D P-1H -E '2013-12-31 23:30:00Z'" -- export CIB_user=betteridea desc="$CIB_user: Query configuration - explicit deny" cmd="cibadmin -Q" test_assert 0 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin --delete --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql export CIB_user=niceguy desc="$CIB_user: Replace - remove acls" cmd="cibadmin --replace --xml-file /tmp/$$.haxor.xml" test_assert 13 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -C -o resources --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - create resource" cmd="cibadmin --replace --xml-file /tmp/$$.haxor.xml" test_assert 13 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" crm_attribute -n enable-acl -v false CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - modify attribute (deny)" cmd="cibadmin --replace --xml-file /tmp/$$.haxor.xml" test_assert 13 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin --replace --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - delete attribute (deny)" cmd="cibadmin --replace --xml-file /tmp/$$.haxor.xml" test_assert 13 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin --modify --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - create attribute (deny)" cmd="cibadmin --replace --xml-file /tmp/$$.haxor.xml" test_assert 13 0 rm -rf /tmp/$$.haxor.xml CIB_user=bob CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin --modify --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - create attribute (allow)" cmd="cibadmin --replace -o resources --xml-file /tmp/$$.haxor.xml" test_assert 0 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin --modify --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - modify attribute (allow)" cmd="cibadmin --replace -o resources --xml-file /tmp/$$.haxor.xml" test_assert 0 0 CIB_user=root cibadmin -Q > /tmp/$$.haxor.xml CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin --replace -o resources --xml-text '' CIB_user=root CIB_file=/tmp/$$.haxor.xml CIB_shadow="" cibadmin -Ql desc="$CIB_user: Replace - delete attribute (allow)" cmd="cibadmin --replace -o resources --xml-file /tmp/$$.haxor.xml" test_assert 0 0 } function test_acls() { export CIB_shadow_dir=$test_home $VALGRIND_CMD crm_shadow --batch --force --create-empty $shadow --validate-with pacemaker-1.3 2>&1 export CIB_shadow=$shadow cat </tmp/$$.acls.xml -- EOF desc="Configure some ACLs" cmd="cibadmin -M -o acls --xml-file /tmp/$$.acls.xml" test_assert 0 desc="Enable ACLs" cmd="crm_attribute -n enable-acl -v true" test_assert 0 -- export PCMK_stderr=1 cibadmin -C -o resources --xml-text '' cibadmin -C -o resources --xml-text '' cibadmin -C -o constraints --xml-text '' cibadmin -Q > /tmp/$$.good-1.2.xml desc="Try to make resulting CIB invalid (enum violation)" cmd="cibadmin -M -o constraints --xml-text ''" test_assert 203 sed 's|"start"|"break"|' /tmp/$$.good-1.2.xml > /tmp/$$.bad-1.2.xml desc="Run crm_simulate with invalid CIB (enum violation)" cmd="crm_simulate -x /tmp/$$.bad-1.2.xml -S" test_assert 126 0 desc="Try to make resulting CIB invalid (unrecognized validate-with)" cmd="cibadmin -M --xml-text ''" test_assert 203 sed 's|"pacemaker-1.2"|"pacemaker-9999.0"|' /tmp/$$.good-1.2.xml > /tmp/$$.bad-1.2.xml desc="Run crm_simulate with invalid CIB (unrecognized validate-with)" cmd="crm_simulate -x /tmp/$$.bad-1.2.xml -S" test_assert 126 0 desc="Try to make resulting CIB invalid, but possibly recoverable (valid with X.Y+1)" cmd="cibadmin -C -o configuration --xml-text ''" test_assert 203 sed 's||\0|' /tmp/$$.good-1.2.xml > /tmp/$$.bad-1.2.xml desc="Run crm_simulate with invalid, but possibly recoverable CIB (valid with X.Y+1)" cmd="crm_simulate -x /tmp/$$.bad-1.2.xml -S" test_assert 0 0 sed 's|\s\s*validate-with="[^"]*"||' /tmp/$$.good-1.2.xml > /tmp/$$.bad-1.2.xml desc="Make resulting CIB valid, although without validate-with attribute" cmd="cibadmin -R --xml-file /tmp/$$.bad-1.2.xml" test_assert 0 desc="Run crm_simulate with valid CIB, but without validate-with attribute" cmd="crm_simulate -x /tmp/$$.bad-1.2.xml -S" test_assert 0 0 # this will just disable validation and accept the config, outputting # validation errors sed -e 's|\s\s*validate-with="[^"]*"||' \ -e 's|\(\s\s*epoch="[^"]*\)"|\10"|' -e 's|"start"|"break"|' \ /tmp/$$.good-1.2.xml > /tmp/$$.bad-1.2.xml desc="Make resulting CIB invalid, and without validate-with attribute" cmd="cibadmin -R --xml-file /tmp/$$.bad-1.2.xml" test_assert 0 desc="Run crm_simulate with invalid CIB, also without validate-with attribute" cmd="crm_simulate -x /tmp/$$.bad-1.2.xml -S" test_assert 0 0 rm -f /tmp/$$.good-1.2.xml /tmp/$$.bad-1.2.xml } for t in $tests; do echo "Testing $t" test_$t > $test_home/regression.$t.out -- -e 's/Created new pacemaker-.* configuration/Created new pacemaker configuration/'\ -e 's/.*__xml_acl_check/__xml_acl_check/g'\ -e 's/.*__xml_acl_post_process/__xml_acl_post_process/g'\ -e 's/.*error: unpack_resources:/error: unpack_resources:/g'\ -e 's/ last-rc-change=\"[0-9]*\"//'\ -e 's|^/tmp/[0-9][0-9]*\.||'\ -e 's/^Entity: line [0-9][0-9]*: //'\ -e 's/schemas\.c:\([0-9][0-9]*\)/schemas.c:NNN/' \ -e 's/constraints\.:\([0-9][0-9]*\)/constraints.:NNN/' \ -e 's/\(validation ([0-9][0-9]* of \)[0-9][0-9]*\().*\)/\1X\2/' \ $test_home/regression.$t.out cas libsope-devel-3.2.10-alt2.x86_64 rpm-filesystem-conflict-file-file warn There are file conflicts with the package libgnustep-gdl2-devel-0.12.0-alt5.svn20130819.1.x86_64, for example, /usr/include/EOControl/EOArrayDataSource.h (15 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. cas libsope-devel-3.2.10-alt2.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libEOControl.so is different from the same symlink in the package libgnustep-gdl2-devel-0.12.0-alt5.svn20130819.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.
value of symlink /usr/lib64/libWOExtensions.so is different from the same symlink in the package libgnustep-gsweb-devel-1.3.0-alt2.svn20131221.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib64/libXmlRpc.so is different from the same symlink in the package libxmlrpcxx-devel-0.7-alt2.git20100306.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. cas libv8-nodejs-5.1.281.75-alt1.x86_64 big-changelog info Package contains big ChangeLog. Gzip it. cas libwbclient-DC-4.7.7-alt1.S1.x86_64 alt-alternatives-vs-ghost info Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.14 is an alternative in package libwbclient-4.7.7-alt1.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.14.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-4.7.7-alt1.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0.14 is an alternative in package libwbclient-DC-4.7.7-alt1.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.14.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-DC-4.7.7-alt1.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so.0 is an alternative in package libwbclient-sssd-1.16.1-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.0. cas libwbclient-DC-debuginfo-4.7.7-alt1.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.14.debug is different from the same symlink in the package libwbclient-debuginfo-4.7.7-alt1.S1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-debuginfo-4.7.7-alt1.S1.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
value of symlink /usr/lib/debug/usr/lib64/libwbclient.so.0.debug is different from the same symlink in the package libwbclient-sssd-debuginfo-1.16.1-alt5.S1.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. cas libwbclient-DC-devel-4.7.7-alt1.S1.x86_64 alt-alternatives-vs-ghost info Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-DC-devel-4.7.7-alt1.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-devel-4.7.7-alt1.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so.
Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libwbclient.so is an alternative in package libwbclient-sssd-devel-1.16.1-alt5.S1.x86_64. Consider removing the ghost file /usr/lib64/libwbclient.so. cas libwvstreams-devel-doc-4.6.1-alt3.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. cas logisim-2.7.1-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/logisim.desktop: hint: value "Education;Science;ComputerScience;Java;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas logisim-2.7.1-alt1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas luckybackup-0.4.9-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. cas luckybackup-0.4.9-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/luckybackup-gnome-su.desktop. Please add it or report a bug against this test if you already have registered one (not including menu unrelated ones as Core or Qt).
Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/luckybackup.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). cas luckybackup-0.4.9-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas lxde-icon-theme-0.5.1-alt1.noarch obsolete-call-in-post-gtk-update-icon-cache warn gtk-update-icon-cache call in post/postun is deprecated cas mazen-1.0.1-alt2.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas mediaelch-2.4-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/MediaElch.desktop: error: value "2.4" for key "Version" in group "Desktop Entry" is not a known version cas mediaelch-2.4-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas minetest-0.4.16-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. cas minetest-0.4.16-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/minetest.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). cas minetest-server-0.4.16-alt1.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts. cas mint-translations-2018.01.06-alt2.noarch 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. cas modem-manager-gui-0.0.19.1-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. cas modem-manager-gui-0.0.19.1-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/modem-manager-gui.desktop: hint: value "GTK;System;Utility;Network;TelephonyTools;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
/usr/share/applications/modem-manager-gui.desktop: hint: value "GTK;System;Utility;Network;TelephonyTools;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas mpi-selector-1.0.3-alt3.noarch missing-url info Missing Url: in a package. cas netactview-0.6.4-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas netsurf-3.7-alt1.src unmet-dependency-build-missing-package fail build dependency libmozjs-devel not found. cas netsurf-3.7-alt1.x86_64 freedesktop-desktop warn desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/netsurf.desktop: error: file contains key "MultipleArgs" in group "Desktop Entry", but keys extending the format should start with "X-" cas netsurf-3.7-alt1.x86_64 iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas ninja-ide-2.3-alt2.noarch altlinux-python-test-is-packaged experimental /usr/lib/python2.7/site-packages/ninja_tests/core/examples/__init__.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/ninja_tests/core/examples/__init__.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/ninja_tests/core/examples/__init__.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/ninja_tests/core/examples/file_for_tests.py: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/ninja_tests/core/examples/file_for_tests.pyc: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details.
/usr/lib/python2.7/site-packages/ninja_tests/core/examples/file_for_tests.pyo: It is the file in the package whose location matches the format python modules use for examples. It may have been installed by accident. Move it to the -examples or -doc subpackage. See http://www.altlinux.org/Python_Policy for details. cas ninja-ide-2.3-alt2.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas notepadqq-1.4.8-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. cas notepadqq-1.4.8-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/notepadqq.desktop: hint: value "Development;Utility;TextEditor;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
/usr/share/applications/notepadqq.desktop: warning: key "OnlyShowIn" in group "Desktop Action Window" is deprecated
/usr/share/applications/notepadqq.desktop: warning: key "OnlyShowIn" in group "Desktop Action Document" is deprecated cas nss-ldapd-0.9.9-alt1.x86_64 init-lsb warn /etc/rc.d/init.d/nslcd: lsb init header missing. See http://www.altlinux.org/Services_Policy for details. cas nss-ldapd-0.9.9-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. cas nss-ldapd-0.9.9-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/nslcd.conf to \%_tmpfilesdir/. cas octave-4.2.2-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. cas octave-4.2.2-alt1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/www.octave.org-octave.desktop: hint: value "Education;Science;Math;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas odoo-11.0-alt1.20180514.noarch rpm-obsolete-live-package info The package obsoletes the package openerp-7.0-alt4.20140326.noarch, but the package openerp-7.0-alt4.20140326.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 openerp-httpd-fonts-access-7.0-alt4.20140326.noarch, but the package openerp-httpd-fonts-access-7.0-alt4.20140326.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. cas odoo-11.0-alt1.20180514.noarch 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. cas ohai-doc-14.1.5-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/share/ri/site/String/cdesc-String.ri conflicts with the package asciidoctor-doc-1.5.6.1-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.
There are file conflicts with the package chef-doc-12.15.11-alt1.noarch, for example, /usr/share/ri/site/Chef/cdesc-Chef.ri (18 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.
File /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-amqp-doc-1.8.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-azure-core-doc-0.1.14-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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-backports-doc-3.7.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.
Files /usr/share/ri/site/Chef/cdesc-Chef.ri /usr/share/ri/site/String/cdesc-String.ri conflict with the package ruby-chef-sugar-doc-3.4.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 /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-dalli-doc-2.7.6-alt1.1.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-em-http-request-doc-1.1.5-alt1.1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.
Files /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri /usr/share/ri/site/Win32/cdesc-Win32.ri conflict with the package ruby-facter-doc-2.0.1-alt2.1.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-fast_gettext-doc-1.1.0-alt2.2.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-ffi-yajl-doc-2.3.1-alt1.4.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-highline-doc-1.7.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-http-cookie-doc-1.0.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-httpclient-doc-2.8.2.4-alt1.1.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-mcollective-client-doc-2.11.0-alt1.1.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-oj-doc-3.6.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-puppet-lint-doc-3.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-sequel-doc-5.5.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 /usr/share/ri/site/RbConfig/cdesc-RbConfig.ri conflicts with the package ruby-spoon-doc-0.0.6-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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-temple-doc-0.8.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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-treetop-doc-1.6.10-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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package ruby-unf-doc-0.1.4-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 /usr/share/ri/site/String/cdesc-String.ri conflicts with the package taskjuggler-3.6.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. cas omnibus-software-4.0.0-alt1.gita5aef20.src unmet-dependency-build-missing-package fail build dependency omnibus not found. cas onboard-1.4.1-alt1.1.x86_64 arch-dep-package-has-big-usr-share info The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere. cas onboard-1.4.1-alt1.1.x86_64 freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/onboard-settings.desktop: hint: value "Settings;Accessibility;Utility;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas opencc-1.0.5-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. cas opencc-doc-1.0.5-alt1.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. cas openchange-devel-2.4-alt24.zentyal23.S1.x86_64 rpm-filesystem-conflict-symlink-symlink warn value of symlink /usr/lib64/libmapi.so is different from the same symlink in the package monetdb-common-11.27.11-alt1.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.
value of symlink /usr/lib64/libmapi.so is different from the same symlink in the package zarafa-devel-7.1.15-alt19.S1.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. cas openchange-ocsmanager-2.4-alt24.zentyal23.S1.x86_64 init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. cas openerp-7.0-alt4.20140326.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/openerp/addons/account/test/test_edi_invoice.yml: 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/lib/python2.7/site-packages/openerp/addons/account/test/test_parent_structure.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/lib/python2.7/site-packages/openerp/addons/account/test/test_parent_structure.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/lib/python2.7/site-packages/openerp/addons/account/test/test_parent_structure.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/lib/python2.7/site-packages/openerp/addons/account/test/test_parent_structure.yml: 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/lib/python2.7/site-packages/openerp/addons/account/tests/test_search.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/lib/python2.7/site-packages/openerp/addons/account/tests/test_search.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/lib/python2.7/site-packages/openerp/addons/account/tests/test_search.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/lib/python2.7/site-packages/openerp/addons/account/tests/test_tax.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/lib/python2.7/site-packages/openerp/addons/account/tests/test_tax.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/lib/python2.7/site-packages/openerp/addons/account/tests/test_tax.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/lib/python2.7/site-packages/openerp/addons/account_followup/tests/test_account_followup.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/lib/python2.7/site-packages/openerp/addons/account_followup/tests/test_account_followup.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/lib/python2.7/site-packages/openerp/addons/account_followup/tests/test_account_followup.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/lib/python2.7/site-packages/openerp/addons/base/test/test_auth.yml: 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/lib/python2.7/site-packages/openerp/addons/base/test/test_context.xml: 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/lib/python2.7/site-packages/openerp/addons/base/test/test_ir_rule.yml: 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/lib/python2.7/site-packages/openerp/addons/base/test/test_osv_expression.yml: 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/lib/python2.7/site-packages/openerp/addons/base/tests/test_base.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_base.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_base.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_expression.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_expression.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_expression.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_ir_attachment.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_ir_attachment.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_ir_attachment.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_ir_values.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_ir_values.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_ir_values.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_menu.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_menu.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_menu.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_search.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_search.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_search.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_views.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_views.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/lib/python2.7/site-packages/openerp/addons/base/tests/test_views.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/lib/python2.7/site-packages/openerp/addons/base_calendar/test/test_crm_recurrent_meeting_case2.yml: 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/lib/python2.7/site-packages/openerp/addons/base_import/tests/test_cases.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/lib/python2.7/site-packages/openerp/addons/base_import/tests/test_cases.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/lib/python2.7/site-packages/openerp/addons/base_import/tests/test_cases.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/lib/python2.7/site-packages/openerp/addons/email_template/tests/test_mail.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/lib/python2.7/site-packages/openerp/addons/email_template/tests/test_mail.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/lib/python2.7/site-packages/openerp/addons/email_template/tests/test_mail.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/lib/python2.7/site-packages/openerp/addons/hr_contract/test/test_hr_contract.yml: 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/lib/python2.7/site-packages/openerp/addons/hr_evaluation/test/test_hr_evaluation.yml: 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/lib/python2.7/site-packages/openerp/addons/hr_holidays/test/test_hr_holiday.yml: 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/lib/python2.7/site-packages/openerp/addons/hr_timesheet/test/test_hr_timesheet.yml: 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/lib/python2.7/site-packages/openerp/addons/hr_timesheet_invoice/test/test_hr_timesheet_invoice.yml: 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/lib/python2.7/site-packages/openerp/addons/hr_timesheet_invoice/test/test_hr_timesheet_invoice_no_prod_tax.yml: 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/lib/python2.7/site-packages/openerp/addons/hr_timesheet_sheet/test/test_hr_timesheet_sheet.yml: 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/lib/python2.7/site-packages/openerp/addons/lunch/tests/test_lunch.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/lib/python2.7/site-packages/openerp/addons/lunch/tests/test_lunch.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/lib/python2.7/site-packages/openerp/addons/lunch/tests/test_lunch.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_invite.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_invite.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_invite.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_base.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_base.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_base.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_features.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_features.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_features.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_gateway.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_gateway.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_gateway.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_message.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_message.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_mail_message.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_message_read.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_message_read.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/lib/python2.7/site-packages/openerp/addons/mail/tests/test_message_read.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/lib/python2.7/site-packages/openerp/addons/membership/test/test_membership.yml: 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/lib/python2.7/site-packages/openerp/addons/mrp/tests/test_multicompany.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/lib/python2.7/site-packages/openerp/addons/mrp/tests/test_multicompany.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/lib/python2.7/site-packages/openerp/addons/mrp/tests/test_multicompany.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/lib/python2.7/site-packages/openerp/addons/mrp_repair/test/test_mrp_repair_afterinv.yml: 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/lib/python2.7/site-packages/openerp/addons/mrp_repair/test/test_mrp_repair_b4inv.yml: 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/lib/python2.7/site-packages/openerp/addons/mrp_repair/test/test_mrp_repair_cancel.yml: 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/lib/python2.7/site-packages/openerp/addons/mrp_repair/test/test_mrp_repair_fee.yml: 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/lib/python2.7/site-packages/openerp/addons/mrp_repair/test/test_mrp_repair_noneinv.yml: 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/lib/python2.7/site-packages/openerp/addons/note/tests/test_note.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/lib/python2.7/site-packages/openerp/addons/note/tests/test_note.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/lib/python2.7/site-packages/openerp/addons/note/tests/test_note.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/lib/python2.7/site-packages/openerp/addons/portal/tests/test_portal.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/lib/python2.7/site-packages/openerp/addons/portal/tests/test_portal.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/lib/python2.7/site-packages/openerp/addons/portal/tests/test_portal.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/lib/python2.7/site-packages/openerp/addons/portal_project/tests/test_access_rights.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/lib/python2.7/site-packages/openerp/addons/portal_project/tests/test_access_rights.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/lib/python2.7/site-packages/openerp/addons/portal_project/tests/test_access_rights.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/lib/python2.7/site-packages/openerp/addons/portal_project_issue/tests/test_access_rights.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/lib/python2.7/site-packages/openerp/addons/portal_project_issue/tests/test_access_rights.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/lib/python2.7/site-packages/openerp/addons/portal_project_issue/tests/test_access_rights.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/lib/python2.7/site-packages/openerp/addons/product/tests/test_uom.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/lib/python2.7/site-packages/openerp/addons/product/tests/test_uom.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/lib/python2.7/site-packages/openerp/addons/product/tests/test_uom.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/lib/python2.7/site-packages/openerp/addons/stock/tests/test_multicompany.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/lib/python2.7/site-packages/openerp/addons/stock/tests/test_multicompany.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/lib/python2.7/site-packages/openerp/addons/stock/tests/test_multicompany.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/lib/python2.7/site-packages/openerp/addons/web/tests/test_dataset.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/lib/python2.7/site-packages/openerp/addons/web/tests/test_dataset.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/lib/python2.7/site-packages/openerp/addons/web/tests/test_dataset.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/lib/python2.7/site-packages/openerp/addons/web/tests/test_js.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/lib/python2.7/site-packages/openerp/addons/web/tests/test_js.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/lib/python2.7/site-packages/openerp/addons/web/tests/test_js.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/lib/python2.7/site-packages/openerp/addons/web/tests/test_menu.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/lib/python2.7/site-packages/openerp/addons/web/tests/test_menu.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/lib/python2.7/site-packages/openerp/addons/web/tests/test_menu.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/lib/python2.7/site-packages/openerp/addons/web/tests/test_serving_base.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/lib/python2.7/site-packages/openerp/addons/web/tests/test_serving_base.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/lib/python2.7/site-packages/openerp/addons/web/tests/test_serving_base.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/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/__openerp__.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/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/__openerp__.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/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/__openerp__.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/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/ir.model.access.csv: 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/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/models.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/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/models.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/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/models.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/lib/python2.7/site-packages/openerp/tests/addons/test_exceptions/view.xml: 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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/__openerp__.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/__openerp__.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/__openerp__.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/ir.model.access.csv: 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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/models.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/models.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/models.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/contacts.json: 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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/contacts_big.json: 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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_export.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_export.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_export.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_import.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_import.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_import.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_load.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_load.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/lib/python2.7/site-packages/openerp/tests/addons/test_impex/tests/test_load.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/lib/python2.7/site-packages/openerp/tests/addons/test_limits/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_limits/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_limits/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_limits/__openerp__.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/lib/python2.7/site-packages/openerp/tests/addons/test_limits/__openerp__.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/lib/python2.7/site-packages/openerp/tests/addons/test_limits/__openerp__.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/lib/python2.7/site-packages/openerp/tests/addons/test_limits/ir.model.access.csv: 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/lib/python2.7/site-packages/openerp/tests/addons/test_limits/models.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/lib/python2.7/site-packages/openerp/tests/addons/test_limits/models.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/lib/python2.7/site-packages/openerp/tests/addons/test_limits/models.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/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/__init__.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/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/__openerp__.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/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/__openerp__.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/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/__openerp__.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/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/ir.model.access.csv: 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/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/models.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/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/models.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/lib/python2.7/site-packages/openerp/tests/addons/test_uninstall/models.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/lib/python2.7/site-packages/openerp/tests/test_acl.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/lib/python2.7/site-packages/openerp/tests/test_acl.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/lib/python2.7/site-packages/openerp/tests/test_acl.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/lib/python2.7/site-packages/openerp/tests/test_basecase.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/lib/python2.7/site-packages/openerp/tests/test_basecase.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/lib/python2.7/site-packages/openerp/tests/test_basecase.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/lib/python2.7/site-packages/openerp/tests/test_db_cursor.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/lib/python2.7/site-packages/openerp/tests/test_db_cursor.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/lib/python2.7/site-packages/openerp/tests/test_db_cursor.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/lib/python2.7/site-packages/openerp/tests/test_expression.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/lib/python2.7/site-packages/openerp/tests/test_expression.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/lib/python2.7/site-packages/openerp/tests/test_expression.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/lib/python2.7/site-packages/openerp/tests/test_fields.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/lib/python2.7/site-packages/openerp/tests/test_fields.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/lib/python2.7/site-packages/openerp/tests/test_fields.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/lib/python2.7/site-packages/openerp/tests/test_ir_filters.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/lib/python2.7/site-packages/openerp/tests/test_ir_filters.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/lib/python2.7/site-packages/openerp/tests/test_ir_filters.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/lib/python2.7/site-packages/openerp/tests/test_ir_sequence.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/lib/python2.7/site-packages/openerp/tests/test_ir_sequence.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/lib/python2.7/site-packages/openerp/tests/test_ir_sequence.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/lib/python2.7/site-packages/openerp/tests/test_mail.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/lib/python2.7/site-packages/openerp/tests/test_misc.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/lib/python2.7/site-packages/openerp/tests/test_misc.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/lib/python2.7/site-packages/openerp/tests/test_misc.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/lib/python2.7/site-packages/openerp/tests/test_orm.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/lib/python2.7/site-packages/openerp/tests/test_orm.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/lib/python2.7/site-packages/openerp/tests/test_orm.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/lib/python2.7/site-packages/openerp/tests/test_osv.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/lib/python2.7/site-packages/openerp/tests/test_osv.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/lib/python2.7/site-packages/openerp/tests/test_osv.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/lib/python2.7/site-packages/openerp/tests/test_translate.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/lib/python2.7/site-packages/openerp/tests/test_translate.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/lib/python2.7/site-packages/openerp/tests/test_translate.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/lib/python2.7/site-packages/openerp/tests/test_uninstall.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/lib/python2.7/site-packages/openerp/tests/test_uninstall.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/lib/python2.7/site-packages/openerp/tests/test_uninstall.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/lib/python2.7/site-packages/openerp/tests/test_view_validation.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/lib/python2.7/site-packages/openerp/tests/test_view_validation.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/lib/python2.7/site-packages/openerp/tests/test_view_validation.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/lib/python2.7/site-packages/openerp/tests/test_xmlrpc.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/lib/python2.7/site-packages/openerp/tests/test_xmlrpc.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/lib/python2.7/site-packages/openerp/tests/test_xmlrpc.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. cas openerp-7.0-alt4.20140326.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package odoo-11.0-alt1.20180514.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 odoo-11.0-alt1.20180514.noarch to remove Obsoletes: tag. cas openerp-7.0-alt4.20140326.noarch 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. cas openerp-httpd-fonts-access-7.0-alt4.20140326.noarch rpm-package-is-obsoleted warn The package is obsoleted by the package odoo-11.0-alt1.20180514.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 odoo-11.0-alt1.20180514.noarch to remove Obsoletes: tag. cas openerp-risk-management-7.0-alt4.20140326.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/openerp/addons/risk_management/test/test_risk_management.yml: 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/lib/python2.7/site-packages/openerp/addons/risk_management/tests/test_risks.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/lib/python2.7/site-packages/openerp/addons/risk_management/tests/test_risks.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/lib/python2.7/site-packages/openerp/addons/risk_management/tests/test_risks.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. cas osync-1.2-alt1.noarch init-condrestart fail /etc/rc.d/init.d/osync-srv: missing condstop target. ERROR: alt-specific script %_sbindir/preun_service (used in your %preun_service macro) depends on condstop. Please, fix. cas pacemaker-cli-1.1.18-alt1.x86_64 systemd-but-no-native-init warn The package have native systemd file(s) but no SysV init scripts. cas pcsc-tools-gui-1.5.3-alt1.x86_64 freedesktop-categories warn Menu-related Additional Categories (http://standards.freedesktop.org/menu-spec/latest/apa.html) not found in /usr/share/applications/gscriptor.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). cas plater-1.6.0-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/plater.desktop: hint: value "GNOME;GTK;Utility;Graphics;3DGraphics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas pology-0.12-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. cas postgis-2.4.4-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. cas postgresql10-postgis-2.4.4-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. cas postgrey-1.37-alt1.noarch init-but-no-native-systemd info The package have SysV init script(s) but no native systemd files. cas postgrey-1.37-alt1.noarch init-lsb fail /etc/rc.d/init.d/postgrey: not systemd compatible: lsb init header missing and postgrey.service is not present. See http://www.altlinux.org/Services_Policy for details. cas postgrey-1.37-alt1.noarch 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. cas pronsole-1.6.0-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/pronsole.desktop: hint: value "Utility;Graphics;3DGraphics;ConsoleOnly;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas pronsole-1.6.0-alt1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas pronterface-1.6.0-alt1.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/pronterface.desktop: hint: value "GNOME;GTK;Utility;Graphics;3DGraphics;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas pronterface-1.6.0-alt1.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas pronterface-1.6.0-alt1.noarch symlink-extra-slash info /usr/share/pronterface/locale:This symlink contains two successive slashes (//) or ends with a slash (/). symlinks should be as short as possible. cas py3c-devel-1.0-alt1.x86_64 buildroot fail found paths to buildroot: /usr/share/pkgconfig/py3c.pc: includedir=/usr/src/tmp/py3c-buildroot/usr/include cas pysycache-3.1-alt2.noarch freedesktop-desktop info desktop-file-validate utility printed the following message(s): /usr/share/applications/pysycachenf.desktop: hint: value "Game;KidsGame;Education;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
desktop-file-validate utility printed the following message(s): /usr/share/applications/pysycache.desktop: hint: value "Game;KidsGame;Education;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu
desktop-file-validate utility printed the following message(s): /usr/share/applications/pysycache-admin.desktop: hint: value "Game;KidsGame;Education;" for key "Categories" in group "Desktop Entry" contains more than one main category; application might appear more than once in the application menu cas pysycache-3.1-alt2.noarch iconsdir experimental Please, move pixmaps from /usr/share/pixmaps to %_liconsdir, %_niconsdir, %_miconsdir according to their size. See http://www.altlinux.org/IconPathsPolicy. cas python-module-PyQwt-devel-5.2.0-alt3.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. cas python-module-nose2-0.6.5-alt1.1.noarch altlinux-python-test-is-packaged info /usr/lib/python2.7/site-packages/nose2/tests/functional/test_attrib_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_attrib_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_attrib_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_collect_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_collect_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_collect_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_coverage.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/lib/python2.7/site-packages/nose2/tests/functional/test_coverage.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/lib/python2.7/site-packages/nose2/tests/functional/test_coverage.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/lib/python2.7/site-packages/nose2/tests/functional/test_decorators.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/lib/python2.7/site-packages/nose2/tests/functional/test_decorators.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/lib/python2.7/site-packages/nose2/tests/functional/test_decorators.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/lib/python2.7/site-packages/nose2/tests/functional/test_discovery_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/lib/python2.7/site-packages/nose2/tests/functional/test_discovery_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/lib/python2.7/site-packages/nose2/tests/functional/test_discovery_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/lib/python2.7/site-packages/nose2/tests/functional/test_doctests_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_doctests_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_doctests_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_dundertest_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_dundertest_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_dundertest_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_eggdiscovery_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/lib/python2.7/site-packages/nose2/tests/functional/test_eggdiscovery_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/lib/python2.7/site-packages/nose2/tests/functional/test_eggdiscovery_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/lib/python2.7/site-packages/nose2/tests/functional/test_junitxml_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_junitxml_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_junitxml_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_layers_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_layers_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_layers_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_loading.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/lib/python2.7/site-packages/nose2/tests/functional/test_loading.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/lib/python2.7/site-packages/nose2/tests/functional/test_loading.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/lib/python2.7/site-packages/nose2/tests/functional/test_loadtests_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_loadtests_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_loadtests_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_logcapture_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_logcapture_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_logcapture_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_main.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/lib/python2.7/site-packages/nose2/tests/functional/test_main.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/lib/python2.7/site-packages/nose2/tests/functional/test_main.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/lib/python2.7/site-packages/nose2/tests/functional/test_mp_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_mp_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_mp_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_printhooks_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_printhooks_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_printhooks_plugin.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/lib/python2.7/site-packages/nose2/tests/functional/test_session.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/lib/python2.7/site-packages/nose2/tests/functional/test_session.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/lib/python2.7/site-packages/nose2/tests/functional/test_session.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/lib/python2.7/site-packages/nose2/tests/functional/test_such_dsl.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/lib/python2.7/site-packages/nose2/tests/functional/test_such_dsl.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/lib/python2.7/site-packages/nose2/tests/functional/test_such_dsl.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/lib/python2.7/site-packages/nose2/tests/functional/test_util.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/lib/python2.7/site-packages/nose2/tests/functional/test_util.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/lib/python2.7/site-packages/nose2/tests/functional/test_util.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/lib/python2.7/site-packages/nose2/tests/unit/test_attrib_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_attrib_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_attrib_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_buffer_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_buffer_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_buffer_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_collect_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_collect_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_collect_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_collector.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/lib/python2.7/site-packages/nose2/tests/unit/test_collector.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/lib/python2.7/site-packages/nose2/tests/unit/test_collector.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/lib/python2.7/site-packages/nose2/tests/unit/test_config.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/lib/python2.7/site-packages/nose2/tests/unit/test_config.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/lib/python2.7/site-packages/nose2/tests/unit/test_config.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/lib/python2.7/site-packages/nose2/tests/unit/test_debugger_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_debugger_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_debugger_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_decorators.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/lib/python2.7/site-packages/nose2/tests/unit/test_decorators.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/lib/python2.7/site-packages/nose2/tests/unit/test_decorators.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/lib/python2.7/site-packages/nose2/tests/unit/test_doctest_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_doctest_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_doctest_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_dundertest_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_dundertest_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_dundertest_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_failfast.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/lib/python2.7/site-packages/nose2/tests/unit/test_failfast.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/lib/python2.7/site-packages/nose2/tests/unit/test_failfast.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/lib/python2.7/site-packages/nose2/tests/unit/test_functions_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/lib/python2.7/site-packages/nose2/tests/unit/test_functions_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/lib/python2.7/site-packages/nose2/tests/unit/test_functions_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/lib/python2.7/site-packages/nose2/tests/unit/test_generators_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_generators_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_generators_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_junitxml.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/lib/python2.7/site-packages/nose2/tests/unit/test_junitxml.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/lib/python2.7/site-packages/nose2/tests/unit/test_junitxml.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/lib/python2.7/site-packages/nose2/tests/unit/test_layers_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_layers_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_layers_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/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/lib/python2.7/site-packages/nose2/tests/unit/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/lib/python2.7/site-packages/nose2/tests/unit/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/lib/python2.7/site-packages/nose2/tests/unit/test_logcapture_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_logcapture_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_logcapture_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_mp_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_mp_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_mp_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_outcomes_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_outcomes_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_outcomes_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_params_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_params_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_params_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_plugin_api.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/lib/python2.7/site-packages/nose2/tests/unit/test_plugin_api.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/lib/python2.7/site-packages/nose2/tests/unit/test_plugin_api.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/lib/python2.7/site-packages/nose2/tests/unit/test_printhooks_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_printhooks_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_printhooks_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_prof_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_prof_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_prof_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/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/lib/python2.7/site-packages/nose2/tests/unit/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/lib/python2.7/site-packages/nose2/tests/unit/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/lib/python2.7/site-packages/nose2/tests/unit/test_session.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/lib/python2.7/site-packages/nose2/tests/unit/test_session.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/lib/python2.7/site-packages/nose2/tests/unit/test_session.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/lib/python2.7/site-packages/nose2/tests/unit/test_testcase_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/lib/python2.7/site-packages/nose2/tests/unit/test_testcase_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/lib/python2.7/site-packages/nose2/tests/unit/test_testcase_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/lib/python2.7/site-packages/nose2/tests/unit/test_testclass_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/lib/python2.7/site-packages/nose2/tests/unit/test_testclass_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/lib/python2.7/site-packages/nose2/tests/unit/test_testclass_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/lib/python2.7/site-packages/nose2/tests/unit/test_testid_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_testid_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_testid_plugin.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/lib/python2.7/site-packages/nose2/tests/unit/test_util.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/lib/python2.7/site-packages/nose2/tests/unit/test_util.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/lib/python2.7/site-packages/nose2/tests/unit/test_util.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. cas python-module-openchange-2.4-alt24.zentyal23.S1.x86_64 altlinux-python-test-is-packaged info /usr/lib64/python2.7/site-packages/openchange/tests/test_mailbox.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/site-packages/openchange/tests/test_mailbox.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/site-packages/openchange/tests/test_mailbox.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/site-packages/openchange/tests/test_migration.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/site-packages/openchange/tests/test_migration.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/site-packages/openchange/tests/test_migration.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/site-packages/openchange/tests/test_provision.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/site-packages/openchange/tests/test_provision.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/site-packages/openchange/tests/test_provision.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. cas python-module-service_identity-17.0.0-alt1.noarch rpm-filesystem-conflict-file-file warn File /usr/lib/python2.7/site-packages/service_identity-17.0.0-py2.7.egg-info/PKG-INFO conflicts with the package python-module-service-identity-17.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.