GASNet-debuginfo-1.16.0-alt3.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package berkeley_upc-debuginfo-2.12.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.; 
Scientific-mpi-debuginfo-2.9.1-alt1.x86_64	buildroot	fail	found paths to buildroot:  /usr/lib/debug/usr/bin/mpipython.debug: Двоичный файл /usr/lib/debug/usr/bin/mpipython.debug совпадает /usr/lib/debug/.build-id/5d/96d08c25c82089613b780f2069f23a73a12f87.debug: Двоичный файл /usr/lib/debug/.build-id/5d/96d08c25c82089613b780f2069f23a73a12f87.debug совпадает; 
afepack-complex-templates-debuginfo-1.8-alt5.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/.build-id/02/9b0118388c746e9aa264f91d610f939685bc63 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/02/9b0118388c746e9aa264f91d610f939685bc63.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/02/dd017d9c747e7988f5b0a5f53e5178d87a246a is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/02/dd017d9c747e7988f5b0a5f53e5178d87a246a.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/15/08ab3a738a016cac9ed92acd993df984402942 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/15/08ab3a738a016cac9ed92acd993df984402942.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/1a/6c133a7bae800b6872da1382bad1588c76725f is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/1a/6c133a7bae800b6872da1382bad1588c76725f.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/1b/302bf434ce12b912cdf41c82013186c6b2d328 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/1b/302bf434ce12b912cdf41c82013186c6b2d328.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/1c/be26aae20a91348c2e5130f459af23114a26f4 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/1c/be26aae20a91348c2e5130f459af23114a26f4.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/23/5a44c526d71b2f7db403e9578377abff94d57d is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/23/5a44c526d71b2f7db403e9578377abff94d57d.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/24/e327d548907f68684625b01ab3223fdf16867f is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/24/e327d548907f68684625b01ab3223fdf16867f.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/28/28c82377e472a757752aa7d6daf6615d5e6736 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/28/28c82377e472a757752aa7d6daf6615d5e6736.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/2a/dab670729a8ea83c72635ed17bb6c40ff84ef4 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/2a/dab670729a8ea83c72635ed17bb6c40ff84ef4.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/2d/3aa6fdbde63fec206eaf203ff9f9dc098c6fac is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/2d/3aa6fdbde63fec206eaf203ff9f9dc098c6fac.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/2e/3bdef7abcc4958de3b159ba477db18887f5a0b is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/2e/3bdef7abcc4958de3b159ba477db18887f5a0b.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/39/4f36418f4e9d9c801de2f62b5e6921433aa188 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/39/4f36418f4e9d9c801de2f62b5e6921433aa188.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/45/1d542dbf0bb27718b689dabc80ece51e4a14f3 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/45/1d542dbf0bb27718b689dabc80ece51e4a14f3.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/4e/6d3b574c3cbf3ddbf075129c7814d54ac52078 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/4e/6d3b574c3cbf3ddbf075129c7814d54ac52078.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/56/58ab7990c9f78d3953b525ea7907d92ecf66ab is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/56/58ab7990c9f78d3953b525ea7907d92ecf66ab.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/57/653a30509264430b7de7ef08890bb1a807266c is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/57/653a30509264430b7de7ef08890bb1a807266c.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/5d/c18488ddf8fd1c52769ca02cd22b5e8ad7989a is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/5d/c18488ddf8fd1c52769ca02cd22b5e8ad7989a.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/68/120f20428be9e65aa0ac29d43dc9f31a8212e3 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/68/120f20428be9e65aa0ac29d43dc9f31a8212e3.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/75/6aa2420173ce20bee3eae16ef95aea98371433 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/75/6aa2420173ce20bee3eae16ef95aea98371433.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/77/bc92c7d1d9ece17c764977b879cf4eb2ebda47 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/77/bc92c7d1d9ece17c764977b879cf4eb2ebda47.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/82/24cee836e7a2481a694baaeec758698c7aa50a is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/82/24cee836e7a2481a694baaeec758698c7aa50a.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/82/90c39008f7697411bef0ff7dfe1ada08e09d7d is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/82/90c39008f7697411bef0ff7dfe1ada08e09d7d.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/83/2fb48e6a7410033df7373aa486cf2410862a24 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/83/2fb48e6a7410033df7373aa486cf2410862a24.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/86/155d9dd067e8596d91996aaf126961e82e9daa is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/86/155d9dd067e8596d91996aaf126961e82e9daa.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/96/6c320dd9883bbeaa55b0457ad44d93e1d782a8 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/96/6c320dd9883bbeaa55b0457ad44d93e1d782a8.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/98/9f6e0fb9e524550225e9c2e6ed8cdd36762592 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/98/9f6e0fb9e524550225e9c2e6ed8cdd36762592.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/9d/580c8ef34dff91bb47454cd67ef543dda35994 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/9d/580c8ef34dff91bb47454cd67ef543dda35994.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/a5/14b19a369fff905374546f9804a1100769572e is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/a5/14b19a369fff905374546f9804a1100769572e.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/a6/f1adfe77b90ca848d147caf441825288ef245a is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/a6/f1adfe77b90ca848d147caf441825288ef245a.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/a7/d6fd2aab204d3999995358e5e1d585da8eac58 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/a7/d6fd2aab204d3999995358e5e1d585da8eac58.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/ad/e3fbded3e2a516cbfe31f2c132bdbebc1ef283 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/ad/e3fbded3e2a516cbfe31f2c132bdbebc1ef283.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/b4/efc49910fb0d7edb1d1046988ca2c4770ab8a0 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/b4/efc49910fb0d7edb1d1046988ca2c4770ab8a0.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/b8/68dbf73ee1e2bc3106e4a280beba59c2d54c64 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/b8/68dbf73ee1e2bc3106e4a280beba59c2d54c64.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/cf/ddfc7195664434429c9ebf91734340a077b08b is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/cf/ddfc7195664434429c9ebf91734340a077b08b.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/d8/4ff4807da59446ed02d203f05427dfa52886fe is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/d8/4ff4807da59446ed02d203f05427dfa52886fe.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/d8/b94937f90b98e9cfb9c941788baa4419bc055e is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/d8/b94937f90b98e9cfb9c941788baa4419bc055e.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/eb/69504446f4140c0590dc8b41495599776f74a9 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/eb/69504446f4140c0590dc8b41495599776f74a9.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/ec/e9f1efff4f48e58317a9484bf46e81bd9f4c58 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/ec/e9f1efff4f48e58317a9484bf46e81bd9f4c58.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/fb/1ff7bbb92d275e10d46c1e33b0246d323a3c09 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/fb/1ff7bbb92d275e10d46c1e33b0246d323a3c09.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/fd/ead29ff81a8ea33b7007362123f818623b36c7 is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/fd/ead29ff81a8ea33b7007362123f818623b36c7.debug is different from the same symlink in the package afepack-real-templates-debuginfo-1.8-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.; 
afepack-devel-doc-1.8-alt5.noarch	uncompressed-manpages	info	Package contains uncompressed manual pages.; 
afepack-real-templates-debuginfo-1.8-alt5.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/.build-id/02/9b0118388c746e9aa264f91d610f939685bc63 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/02/9b0118388c746e9aa264f91d610f939685bc63.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/02/dd017d9c747e7988f5b0a5f53e5178d87a246a is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/02/dd017d9c747e7988f5b0a5f53e5178d87a246a.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/15/08ab3a738a016cac9ed92acd993df984402942 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/15/08ab3a738a016cac9ed92acd993df984402942.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/1a/6c133a7bae800b6872da1382bad1588c76725f is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/1a/6c133a7bae800b6872da1382bad1588c76725f.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/1b/302bf434ce12b912cdf41c82013186c6b2d328 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/1b/302bf434ce12b912cdf41c82013186c6b2d328.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/1c/be26aae20a91348c2e5130f459af23114a26f4 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/1c/be26aae20a91348c2e5130f459af23114a26f4.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/23/5a44c526d71b2f7db403e9578377abff94d57d is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/23/5a44c526d71b2f7db403e9578377abff94d57d.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/24/e327d548907f68684625b01ab3223fdf16867f is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/24/e327d548907f68684625b01ab3223fdf16867f.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/28/28c82377e472a757752aa7d6daf6615d5e6736 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/28/28c82377e472a757752aa7d6daf6615d5e6736.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/2a/dab670729a8ea83c72635ed17bb6c40ff84ef4 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/2a/dab670729a8ea83c72635ed17bb6c40ff84ef4.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/2d/3aa6fdbde63fec206eaf203ff9f9dc098c6fac is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/2d/3aa6fdbde63fec206eaf203ff9f9dc098c6fac.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/2e/3bdef7abcc4958de3b159ba477db18887f5a0b is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/2e/3bdef7abcc4958de3b159ba477db18887f5a0b.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/39/4f36418f4e9d9c801de2f62b5e6921433aa188 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/39/4f36418f4e9d9c801de2f62b5e6921433aa188.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/45/1d542dbf0bb27718b689dabc80ece51e4a14f3 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/45/1d542dbf0bb27718b689dabc80ece51e4a14f3.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/4e/6d3b574c3cbf3ddbf075129c7814d54ac52078 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/4e/6d3b574c3cbf3ddbf075129c7814d54ac52078.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/56/58ab7990c9f78d3953b525ea7907d92ecf66ab is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/56/58ab7990c9f78d3953b525ea7907d92ecf66ab.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/57/653a30509264430b7de7ef08890bb1a807266c is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/57/653a30509264430b7de7ef08890bb1a807266c.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/5d/c18488ddf8fd1c52769ca02cd22b5e8ad7989a is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/5d/c18488ddf8fd1c52769ca02cd22b5e8ad7989a.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/68/120f20428be9e65aa0ac29d43dc9f31a8212e3 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/68/120f20428be9e65aa0ac29d43dc9f31a8212e3.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/75/6aa2420173ce20bee3eae16ef95aea98371433 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/75/6aa2420173ce20bee3eae16ef95aea98371433.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/77/bc92c7d1d9ece17c764977b879cf4eb2ebda47 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/77/bc92c7d1d9ece17c764977b879cf4eb2ebda47.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/82/24cee836e7a2481a694baaeec758698c7aa50a is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/82/24cee836e7a2481a694baaeec758698c7aa50a.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/82/90c39008f7697411bef0ff7dfe1ada08e09d7d is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/82/90c39008f7697411bef0ff7dfe1ada08e09d7d.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/83/2fb48e6a7410033df7373aa486cf2410862a24 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/83/2fb48e6a7410033df7373aa486cf2410862a24.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/86/155d9dd067e8596d91996aaf126961e82e9daa is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/86/155d9dd067e8596d91996aaf126961e82e9daa.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/96/6c320dd9883bbeaa55b0457ad44d93e1d782a8 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/96/6c320dd9883bbeaa55b0457ad44d93e1d782a8.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/98/9f6e0fb9e524550225e9c2e6ed8cdd36762592 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/98/9f6e0fb9e524550225e9c2e6ed8cdd36762592.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/9d/580c8ef34dff91bb47454cd67ef543dda35994 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/9d/580c8ef34dff91bb47454cd67ef543dda35994.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/a5/14b19a369fff905374546f9804a1100769572e is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/a5/14b19a369fff905374546f9804a1100769572e.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/a6/f1adfe77b90ca848d147caf441825288ef245a is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/a6/f1adfe77b90ca848d147caf441825288ef245a.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/a7/d6fd2aab204d3999995358e5e1d585da8eac58 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/a7/d6fd2aab204d3999995358e5e1d585da8eac58.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/ad/e3fbded3e2a516cbfe31f2c132bdbebc1ef283 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/ad/e3fbded3e2a516cbfe31f2c132bdbebc1ef283.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/b4/efc49910fb0d7edb1d1046988ca2c4770ab8a0 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/b4/efc49910fb0d7edb1d1046988ca2c4770ab8a0.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/b8/68dbf73ee1e2bc3106e4a280beba59c2d54c64 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/b8/68dbf73ee1e2bc3106e4a280beba59c2d54c64.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/cf/ddfc7195664434429c9ebf91734340a077b08b is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/cf/ddfc7195664434429c9ebf91734340a077b08b.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/d8/4ff4807da59446ed02d203f05427dfa52886fe is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/d8/4ff4807da59446ed02d203f05427dfa52886fe.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/d8/b94937f90b98e9cfb9c941788baa4419bc055e is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/d8/b94937f90b98e9cfb9c941788baa4419bc055e.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/eb/69504446f4140c0590dc8b41495599776f74a9 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/eb/69504446f4140c0590dc8b41495599776f74a9.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/ec/e9f1efff4f48e58317a9484bf46e81bd9f4c58 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/ec/e9f1efff4f48e58317a9484bf46e81bd9f4c58.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/fb/1ff7bbb92d275e10d46c1e33b0246d323a3c09 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/fb/1ff7bbb92d275e10d46c1e33b0246d323a3c09.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/fd/ead29ff81a8ea33b7007362123f818623b36c7 is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; value of symlink /usr/lib/debug/.build-id/fd/ead29ff81a8ea33b7007362123f818623b36c7.debug is different from the same symlink in the package afepack-complex-templates-debuginfo-1.8-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.; 
bamg-debuginfo-0.60-alt3.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package freefemxx-debuginfo-3.12-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
berkeley_upc-debuginfo-2.12.1-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package GASNet-debuginfo-1.16.0-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
cgns-devel-doc-3.1.3-alt1.svn20110503.noarch	pkg-contains-cvs-or-svn-control-dir	warn	The package contains a CVS/.svn/.git/.hg/.bzr/_MTN directory of revision control system.; It was most likely included by accident since CVS/.svn/.hg/... etc. directories usually don't belong in releases. ; When packaging a CVS/SVN snapshot, export from CVS/SVN rather than use a checkout.; ; 
dapl2-utils-2.0.30-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libdapl-1.2.16-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.; 
dapl2-utils-2.0.30-alt2.x86_64	uncompressed-manpages	info	Package contains uncompressed manual pages.; 
dealii-complex-debuginfo-7.1-alt1.pre.svn20110331.3.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/.build-id/ec/b6abd0db5f47d087051cbe83602d692f93d8c8 is different from the same symlink in the package dealii-real-debuginfo-7.1-alt1.pre.svn20110331.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.; value of symlink /usr/lib/debug/.build-id/ec/b6abd0db5f47d087051cbe83602d692f93d8c8.debug is different from the same symlink in the package dealii-real-debuginfo-7.1-alt1.pre.svn20110331.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.; 
dealii-real-debuginfo-7.1-alt1.pre.svn20110331.3.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/.build-id/ec/b6abd0db5f47d087051cbe83602d692f93d8c8 is different from the same symlink in the package dealii-complex-debuginfo-7.1-alt1.pre.svn20110331.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.; value of symlink /usr/lib/debug/.build-id/ec/b6abd0db5f47d087051cbe83602d692f93d8c8.debug is different from the same symlink in the package dealii-complex-debuginfo-7.1-alt1.pre.svn20110331.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.; 
fastbit-examples-debuginfo-ibis1.2.0.2-alt1.svn20100924.5.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package ibutils-debuginfo-1.5.4-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
fi_lib-examples-debuginfo-1.2-alt4.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package filibpp-examples-debuginfo-3.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.; 
filibpp-examples-debuginfo-3.0.1-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package fi_lib-examples-debuginfo-1.2-alt4.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
firmware-iwl1000-128.50.3.1-alt1.noarch	rpm-package-is-obsoleted	warn	The package is  obsoleted by the package firmware-linux-20110819-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 firmware-linux-20110819-alt1.noarch to remove Obsoletes: tag.; 
free-cad-0.12.2237-alt1.svn20110501.x86_64	freedesktop-desktop	warn	X-Thumbnailer file /usr/share/applications/fcstd-thumbnailer.desktop should be installed to /usr/share/thumbnailers, not to /usr/share/applications.; 
freefem3d-1.0pre10-alt1.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
freefemxx-debuginfo-3.12-alt4.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package bamg-debuginfo-0.60-alt3.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
gnofract4d-3.13-alt5.qa1.x86_64	freedesktop-desktop	warn	desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/gnofract4d.desktop: error: (will be fatal in the future): value "GNOME" in key "Categories" in group "Desktop Entry" requires another category to be present among the following categories: GTK; 
ibutils-debuginfo-1.5.4-alt3.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package fastbit-examples-debuginfo-ibis1.2.0.2-alt1.svn20100924.5.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.; 
judy-1.0.5-alt1.x86_64	bin-permissions	info	not executable file /usr/bin/jhton; 
kde4-kio-sysinfo-2.0-alt4.1.src	specfile-macros-get_dep-is-deprecated	info	Versioned Requires: foo >= %{get_dep something} using %get_dep and %get_version macros on a library are deprecated by set:versions. You should drop %get_dep/%get_version versioning, see generated patch. But if you know what you are doing, please, report an exeption.; 
ksocrat-3.2.1-alt13.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.; 
libCoinCsdp-debuginfo-6.1.1-alt1.svn20101110.3.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libmpeg4ip-debuginfo-1.5.0.1-alt12.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.; 
libberkeley_upc-devel-2.12.1-alt1.x86_64	library-pkgnames-static	warn	package contains static library which has the same name as a shared library in the repository, but neither package name ends with -devel-static according to http://altlinux.org/Drafts/SharedLibs nor the package explicitly conflicts with the package with .so library; 
libcca-spec-babel-j-0.8.6-alt2.svn20090721.9.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.; 
libcca-spec-neo-debuginfo-0.2.8-alt9.x86_64	buildroot	fail	found paths to buildroot:  /usr/lib/debug/usr/lib64/libSimpleStamper-0.9.0.so.debug: Двоичный файл /usr/lib/debug/usr/lib64/libSimpleStamper-0.9.0.so.debug совпадает /usr/lib/debug/usr/lib64/libSimpleStamper-0.9.0.so.0.debug: Двоичный файл /usr/lib/debug/usr/lib64/libSimpleStamper-0.9.0.so.0.debug совпадает /usr/lib/debug/usr/lib64/libSimpleStamper-0.9.0.so.0.0.0.debug: Двоичный файл /usr/lib/debug/usr/lib64/libSimpleStamper-0.9.0.so.0.0.0.debug совпадает /usr/lib/debug/usr/lib64/libParameter-0.1.0.so.debug: Двоичный файл /usr/lib/debug/usr/lib64/libParameter-0.1.0.so.debug совпадает /usr/lib/debug/usr/lib64/libParameter-0.1.0.so.0.debug: Двоичный файл /usr/lib/debug/usr/lib64/libParameter-0.1.0.so.0.debug совпадает /usr/lib/debug/usr/lib64/libParameter-0.1.0.so.0.0.0.debug: Двоичный файл /usr/lib/debug/usr/lib64/libParameter-0.1.0.so.0.0.0.debug совпадает /usr/lib/debug/usr/lib64/libGo-0.1.0.so.debug: Двоичный файл /usr/lib/debug/usr/lib64/libGo-0.1.0.so.debug совпадает /usr/lib/debug/usr/lib64/libGo-0.1.0.so.0.debug: Двоичный файл /usr/lib/debug/usr/lib64/libGo-0.1.0.so.0.debug совпадает /usr/lib/debug/usr/lib64/libGo-0.1.0.so.0.0.0.debug: Двоичный файл /usr/lib/debug/usr/lib64/libGo-0.1.0.so.0.0.0.debug совпадает /usr/lib/debug/.build-id/72/ee13b562037437b3559dfc10239fe82392f0c3.debug: Двоичный файл /usr/lib/debug/.build-id/72/ee13b562037437b3559dfc10239fe82392f0c3.debug совпадает /usr/lib/debug/.build-id/34/8d53334f1adbb52aa5ba586d04d359a4c553c3.debug: Двоичный файл /usr/lib/debug/.build-id/34/8d53334f1adbb52aa5ba586d04d359a4c553c3.debug совпадает /usr/lib/debug/.build-id/1f/d1c11efa317a42374e2799814bfb3954b30417.debug: Двоичный файл /usr/lib/debug/.build-id/1f/d1c11efa317a42374e2799814bfb3954b30417.debug совпадает; 
libcca-spec-neo-devel-static-0.2.8-alt9.x86_64	buildroot	fail	found paths to buildroot:  /usr/lib64/libSimpleStamper-0.9.0.a: Двоичный файл /usr/lib64/libSimpleStamper-0.9.0.a совпадает /usr/lib64/libParameter-0.1.0.a: Двоичный файл /usr/lib64/libParameter-0.1.0.a совпадает /usr/lib64/libGo-0.1.0.a: Двоичный файл /usr/lib64/libGo-0.1.0.a совпадает; 
libcgns-mpi-debuginfo-3.1.3-alt1.svn20110503.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libcgns-seq-debuginfo-3.1.3-alt1.svn20110503.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.; 
libcgns-seq-debuginfo-3.1.3-alt1.svn20110503.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libcgns-mpi-debuginfo-3.1.3-alt1.svn20110503.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.; 
libfftw3-mpi-devel-debuginfo-3.2.2-alt4.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libfftw3-devel-debuginfo-3.2.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.; 
libhdf5-6-mpi-1.8.6-alt1.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/libhdf5.so.6 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5.so.6 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5.so.6.0.5 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5.so.6.0.5 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_fortran.so.6 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_fortran.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_fortran.so.6 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_fortran.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_fortran.so.6.0.5 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_fortran.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_fortran.so.6.0.5 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_fortran.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_hl.so.6 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_hl.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_hl.so.6 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_hl.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_hl.so.6.0.5 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_hl.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_hl.so.6.0.5 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_hl.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5hl_fortran.so.6 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5hl_fortran.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5hl_fortran.so.6 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5hl_fortran.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5hl_fortran.so.6.0.5 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5hl_fortran.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5hl_fortran.so.6.0.5 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5hl_fortran.so.6.0.5.; 
libhdf5-6-mpi-debuginfo-1.8.6-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libhdf5-6-seq-debuginfo-1.8.6-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.; 
libhdf5-6-mpi-debuginfo-1.8.6-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libhdf5.so.6.0.5.debug is different from the same symlink in the package libhdf5-6-seq-debuginfo-1.8.6-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/libhdf5.so.6.debug is different from the same symlink in the package libhdf5-6-seq-debuginfo-1.8.6-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/libhdf5_fortran.so.6.0.5.debug is different from the same symlink in the package libhdf5-6-seq-debuginfo-1.8.6-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/libhdf5_fortran.so.6.debug is different from the same symlink in the package libhdf5-6-seq-debuginfo-1.8.6-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/libhdf5_hl.so.6.0.5.debug is different from the same symlink in the package libhdf5-6-seq-debuginfo-1.8.6-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/libhdf5_hl.so.6.debug is different from the same symlink in the package libhdf5-6-seq-debuginfo-1.8.6-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/libhdf5hl_fortran.so.6.0.5.debug is different from the same symlink in the package libhdf5-6-seq-debuginfo-1.8.6-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/libhdf5hl_fortran.so.6.debug is different from the same symlink in the package libhdf5-6-seq-debuginfo-1.8.6-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.; 
libhdf5-6-seq-1.8.6-alt1.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/libhdf5.so.6 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5.so.6 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5.so.6.0.5 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5.so.6.0.5 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_cpp.so.6 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_cpp.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_cpp.so.6.0.5 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_cpp.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_fortran.so.6 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_fortran.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_fortran.so.6 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_fortran.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_fortran.so.6.0.5 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_fortran.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_fortran.so.6.0.5 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_fortran.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_hl.so.6 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_hl.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_hl.so.6 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_hl.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_hl.so.6.0.5 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_hl.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_hl.so.6.0.5 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_hl.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_hl_cpp.so.6 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_hl_cpp.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5_hl_cpp.so.6.0.5 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5_hl_cpp.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5hl_fortran.so.6 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5hl_fortran.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5hl_fortran.so.6 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5hl_fortran.so.6.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5hl_fortran.so.6.0.5 is an alternative in package libhdf5-6-mpi-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5hl_fortran.so.6.0.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libhdf5hl_fortran.so.6.0.5 is an alternative in package libhdf5-6-seq-1.8.6-alt1.x86_64. Consider removing the ghost file /usr/lib64/libhdf5hl_fortran.so.6.0.5.; 
libhdf5-6-seq-debuginfo-1.8.6-alt1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libhdf5-6-mpi-debuginfo-1.8.6-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.; 
libhdf5-6-seq-debuginfo-1.8.6-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libhdf5.so.6.0.5.debug is different from the same symlink in the package libhdf5-6-mpi-debuginfo-1.8.6-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/libhdf5.so.6.debug is different from the same symlink in the package libhdf5-6-mpi-debuginfo-1.8.6-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/libhdf5_fortran.so.6.0.5.debug is different from the same symlink in the package libhdf5-6-mpi-debuginfo-1.8.6-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/libhdf5_fortran.so.6.debug is different from the same symlink in the package libhdf5-6-mpi-debuginfo-1.8.6-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/libhdf5_hl.so.6.0.5.debug is different from the same symlink in the package libhdf5-6-mpi-debuginfo-1.8.6-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/libhdf5_hl.so.6.debug is different from the same symlink in the package libhdf5-6-mpi-debuginfo-1.8.6-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/libhdf5hl_fortran.so.6.0.5.debug is different from the same symlink in the package libhdf5-6-mpi-debuginfo-1.8.6-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/libhdf5hl_fortran.so.6.debug is different from the same symlink in the package libhdf5-6-mpi-debuginfo-1.8.6-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.; 
liblti-debuginfo-1.9.16-alt5.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libltir.so.debug is different from the same symlink in the package libltilib2-debuginfo-2.110410-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.; 
libltilib2-debuginfo-2.110410-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libltir.so.debug is different from the same symlink in the package liblti-debuginfo-1.9.16-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.; 
libmesh-doc-0.7.0.3-alt1.svn20101117.5.noarch	uncompressed-manpages	info	Package contains uncompressed manual pages.; 
libnetcdf-cxx-4-4.1.2-alt2.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/libnetcdf_c++.so.4 is an alternative in package libnetcdf-cxx-4-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++.so.4.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf_c++.so.4 is an alternative in package libnetcdf-cxx-4-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++.so.4.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf_c++.so.4.1.0 is an alternative in package libnetcdf-cxx-4-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++.so.4.1.0.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf_c++.so.4.1.0 is an alternative in package libnetcdf-cxx-4-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++.so.4.1.0.; 
libnetcdf-cxx-4-debuginfo-4.1.2-alt2.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++.so.4.1.0.debug is different from the same symlink in the package libnetcdf-cxx-4-mpi-debuginfo-4.1.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.; value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++.so.4.debug is different from the same symlink in the package libnetcdf-cxx-4-mpi-debuginfo-4.1.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.; 
libnetcdf-cxx-4-mpi-4.1.2-alt1.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/libnetcdf_c++.so.4 is an alternative in package libnetcdf-cxx-4-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++.so.4.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf_c++.so.4 is an alternative in package libnetcdf-cxx-4-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++.so.4.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf_c++.so.4.1.0 is an alternative in package libnetcdf-cxx-4-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++.so.4.1.0.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf_c++.so.4.1.0 is an alternative in package libnetcdf-cxx-4-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++.so.4.1.0.; 
libnetcdf-cxx-4-mpi-debuginfo-4.1.2-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++.so.4.1.0.debug is different from the same symlink in the package libnetcdf-cxx-4-debuginfo-4.1.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.; value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++.so.4.debug is different from the same symlink in the package libnetcdf-cxx-4-debuginfo-4.1.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.; 
libnetcdf-cxx4-1-4.1.2-alt2.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/libnetcdf_c++4.so.1 is an alternative in package libnetcdf-cxx4-1-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++4.so.1.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf_c++4.so.1 is an alternative in package libnetcdf-cxx4-1-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++4.so.1.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf_c++4.so.1.0.1 is an alternative in package libnetcdf-cxx4-1-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++4.so.1.0.1.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf_c++4.so.1.0.1 is an alternative in package libnetcdf-cxx4-1-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++4.so.1.0.1.; 
libnetcdf-cxx4-1-debuginfo-4.1.2-alt2.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++4.so.1.0.1.debug is different from the same symlink in the package libnetcdf-cxx4-1-mpi-debuginfo-4.1.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.; value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++4.so.1.debug is different from the same symlink in the package libnetcdf-cxx4-1-mpi-debuginfo-4.1.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.; 
libnetcdf-cxx4-1-mpi-4.1.2-alt1.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/libnetcdf_c++4.so.1 is an alternative in package libnetcdf-cxx4-1-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++4.so.1.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf_c++4.so.1 is an alternative in package libnetcdf-cxx4-1-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++4.so.1.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf_c++4.so.1.0.1 is an alternative in package libnetcdf-cxx4-1-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++4.so.1.0.1.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf_c++4.so.1.0.1 is an alternative in package libnetcdf-cxx4-1-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf_c++4.so.1.0.1.; 
libnetcdf-cxx4-1-mpi-debuginfo-4.1.2-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++4.so.1.0.1.debug is different from the same symlink in the package libnetcdf-cxx4-1-debuginfo-4.1.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.; value of symlink /usr/lib/debug/usr/lib64/libnetcdf_c++4.so.1.debug is different from the same symlink in the package libnetcdf-cxx4-1-debuginfo-4.1.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.; 
libnetcdf-fortran-5-4.1.2-alt2.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/libnetcdff.so.5 is an alternative in package libnetcdf-fortran-5-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdff.so.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdff.so.5 is an alternative in package libnetcdf-fortran-5-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdff.so.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdff.so.5.1.0 is an alternative in package libnetcdf-fortran-5-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdff.so.5.1.0.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdff.so.5.1.0 is an alternative in package libnetcdf-fortran-5-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdff.so.5.1.0.; 
libnetcdf-fortran-5-debuginfo-4.1.2-alt2.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libnetcdff.so.5.1.0.debug is different from the same symlink in the package libnetcdf-fortran-5-mpi-debuginfo-4.1.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.; value of symlink /usr/lib/debug/usr/lib64/libnetcdff.so.5.debug is different from the same symlink in the package libnetcdf-fortran-5-mpi-debuginfo-4.1.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.; 
libnetcdf-fortran-5-mpi-4.1.2-alt1.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/libnetcdff.so.5 is an alternative in package libnetcdf-fortran-5-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdff.so.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdff.so.5 is an alternative in package libnetcdf-fortran-5-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdff.so.5.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdff.so.5.1.0 is an alternative in package libnetcdf-fortran-5-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdff.so.5.1.0.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdff.so.5.1.0 is an alternative in package libnetcdf-fortran-5-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdff.so.5.1.0.; 
libnetcdf-fortran-5-mpi-debuginfo-4.1.2-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libnetcdff.so.5.1.0.debug is different from the same symlink in the package libnetcdf-fortran-5-debuginfo-4.1.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.; value of symlink /usr/lib/debug/usr/lib64/libnetcdff.so.5.debug is different from the same symlink in the package libnetcdf-fortran-5-debuginfo-4.1.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.; 
libnetcdf7-mpi-4.1.2-alt1.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/libnetcdf.so.7 is an alternative in package libnetcdf7-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf.so.7.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf.so.7 is an alternative in package libnetcdf7-seq-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf.so.7.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf.so.7.0.1 is an alternative in package libnetcdf7-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf.so.7.0.1.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf.so.7.0.1 is an alternative in package libnetcdf7-seq-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf.so.7.0.1.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libudunits2.so.0 is an alternative in package libnetcdf7-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libudunits2.so.0.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libudunits2.so.0 is an alternative in package libnetcdf7-seq-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libudunits2.so.0.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libudunits2.so.0.0.0 is an alternative in package libnetcdf7-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libudunits2.so.0.0.0.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libudunits2.so.0.0.0 is an alternative in package libnetcdf7-seq-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libudunits2.so.0.0.0.; 
libnetcdf7-mpi-debuginfo-4.1.2-alt1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libnetcdf.so.7.0.1.debug is different from the same symlink in the package libnetcdf7-seq-debuginfo-4.1.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.; value of symlink /usr/lib/debug/usr/lib64/libnetcdf.so.7.debug is different from the same symlink in the package libnetcdf7-seq-debuginfo-4.1.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.; value of symlink /usr/lib/debug/usr/lib64/libudunits2.so.0.0.0.debug is different from the same symlink in the package libnetcdf7-seq-debuginfo-4.1.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.; value of symlink /usr/lib/debug/usr/lib64/libudunits2.so.0.debug is different from the same symlink in the package libnetcdf7-seq-debuginfo-4.1.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.; 
libnetcdf7-seq-4.1.2-alt2.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/libnetcdf.so.7 is an alternative in package libnetcdf7-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf.so.7.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf.so.7 is an alternative in package libnetcdf7-seq-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf.so.7.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf.so.7.0.1 is an alternative in package libnetcdf7-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf.so.7.0.1.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libnetcdf.so.7.0.1 is an alternative in package libnetcdf7-seq-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libnetcdf.so.7.0.1.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libudunits2.so.0 is an alternative in package libnetcdf7-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libudunits2.so.0.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libudunits2.so.0 is an alternative in package libnetcdf7-seq-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libudunits2.so.0.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libudunits2.so.0.0.0 is an alternative in package libnetcdf7-mpi-4.1.2-alt1.x86_64. Consider removing the ghost file /usr/lib64/libudunits2.so.0.0.0.; Since alternatives 0.4 the practice to own alternative symlinks as ghost files is deprecated. the ghost file /usr/lib64/libudunits2.so.0.0.0 is an alternative in package libnetcdf7-seq-4.1.2-alt2.x86_64. Consider removing the ghost file /usr/lib64/libudunits2.so.0.0.0.; 
libnetcdf7-seq-debuginfo-4.1.2-alt2.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libnetcdf.so.7.0.1.debug is different from the same symlink in the package libnetcdf7-mpi-debuginfo-4.1.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.; value of symlink /usr/lib/debug/usr/lib64/libnetcdf.so.7.debug is different from the same symlink in the package libnetcdf7-mpi-debuginfo-4.1.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.; value of symlink /usr/lib/debug/usr/lib64/libudunits2.so.0.0.0.debug is different from the same symlink in the package libnetcdf7-mpi-debuginfo-4.1.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.; value of symlink /usr/lib/debug/usr/lib64/libudunits2.so.0.debug is different from the same symlink in the package libnetcdf7-mpi-debuginfo-4.1.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.; 
libomniORB-names-4.2.0-alt3.x86_64	init-lsb	warn	/etc/rc.d/init.d//omninames: lsb init header missing.  See http://www.altlinux.org/Services_Policy for details.; 
liboski-complex-debuginfo-1.0.1h-alt5.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/oski/liboski.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_Tid.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_Tiz.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_heur_mregblock_Tid.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_heur_mregblock_Tiz.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_heur_regprof_Tid.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_heur_regprof_Tiz.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_heur_symmrb_Tid.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_heur_symmrb_Tiz.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_BCSR_Tid.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_BCSR_Tiz.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_CB_Tid.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_CB_Tiz.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_CSC_Tid.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_CSC_Tiz.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_CSR_Tid.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_CSR_Tiz.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_DENSE_Tid.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_DENSE_Tiz.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_GCSR_Tid.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_GCSR_Tiz.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_MBCSR_Tid.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_MBCSR_Tiz.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_VBR_Tid.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_VBR_Tiz.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_util.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_util_Tid.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_util_Tiz.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboskilt.so.debug is different from the same symlink in the package liboski-real-debuginfo-1.0.1h-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.; 
liboski-real-debuginfo-1.0.1h-alt5.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/oski/liboski.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_Tid.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_Tiz.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_heur_mregblock_Tid.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_heur_mregblock_Tiz.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_heur_regprof_Tid.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_heur_regprof_Tiz.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_heur_symmrb_Tid.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_heur_symmrb_Tiz.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_BCSR_Tid.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_BCSR_Tiz.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_CB_Tid.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_CB_Tiz.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_CSC_Tid.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_CSC_Tiz.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_CSR_Tid.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_CSR_Tiz.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_DENSE_Tid.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_DENSE_Tiz.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_GCSR_Tid.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_GCSR_Tiz.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_MBCSR_Tid.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_MBCSR_Tiz.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_VBR_Tid.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_mat_VBR_Tiz.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_util.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_util_Tid.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboski_util_Tiz.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; value of symlink /usr/lib/debug/usr/lib64/oski/liboskilt.so.debug is different from the same symlink in the package liboski-complex-debuginfo-1.0.1h-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.; 
libpastix-devel-3184-alt1.x86_64	buildroot	fail	found paths to buildroot:  /usr/bin/pastix-conf: LIBS="-L/usr/src/tmp/pastix-buildroot/usr/lib64 -lpastix -lgfortran -lm -lrt -Wl,-R/usr/lib/openmpi/lib -L/usr/lib/metis/lib -lmetis  -L/usr/lib -lscotch -lscotcherrexit    -L/usr/lib -lptscotch -lscotcherrexit -lpthread";; 
libqd-debuginfo-2.3.11-alt4.x86_64	buildroot	fail	found paths to buildroot:  /usr/lib/debug/usr/lib64/libqd_f_main.so.debug: Двоичный файл /usr/lib/debug/usr/lib64/libqd_f_main.so.debug совпадает /usr/lib/debug/usr/lib64/libqd_f_main.so.2.debug: Двоичный файл /usr/lib/debug/usr/lib64/libqd_f_main.so.2.debug совпадает /usr/lib/debug/usr/lib64/libqd_f_main.so.2.3.11.debug: Двоичный файл /usr/lib/debug/usr/lib64/libqd_f_main.so.2.3.11.debug совпадает /usr/lib/debug/.build-id/60/209e64b7a998e2003c6a878da2a33e32e836bb.debug: Двоичный файл /usr/lib/debug/.build-id/60/209e64b7a998e2003c6a878da2a33e32e836bb.debug совпадает; 
libqwt6-debuginfo-6.0.0-alt1.svn20101008.1.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/usr/lib64/libqwt.so.debug is different from the same symlink in the package libqwt-debuginfo-5.2.0-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.; 
libqwt6-qt4-designer-plugin-debuginfo-6.0.0-alt1.svn20101008.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libqwt-debuginfo-5.2.0-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.; 
libtau-debuginfo-2.19.2-alt12.x86_64	buildroot	fail	found paths to buildroot:  /usr/lib/debug/usr/lib64/shared-memory-callpath-param-depthlimit-papi-mpi-pdt-openmp-opari-profile-trace-mpitrace/libTAU.so.2.19.2.debug: Двоичный файл /usr/lib/debug/usr/lib64/shared-memory-callpath-param-depthlimit-papi-mpi-pdt-openmp-opari-profile-trace-mpitrace/libTAU.so.2.19.2.debug совпадает /usr/lib/debug/usr/lib64/libtau.so.debug: Двоичный файл /usr/lib/debug/usr/lib64/libtau.so.debug совпадает /usr/lib/debug/usr/lib64/libTAUsh-memory-callpath-param-depthlimit-papi-mpi-pdt-openmp-opari-profile-trace-mpitrace.so.2.19.2.debug: Двоичный файл /usr/lib/debug/usr/lib64/libTAUsh-memory-callpath-param-depthlimit-papi-mpi-pdt-openmp-opari-profile-trace-mpitrace.so.2.19.2.debug совпадает /usr/lib/debug/usr/lib64/libTAU.so.debug: Двоичный файл /usr/lib/debug/usr/lib64/libTAU.so.debug совпадает /usr/lib/debug/usr/lib64/libTAU.so.2.debug: Двоичный файл /usr/lib/debug/usr/lib64/libTAU.so.2.debug совпадает /usr/lib/debug/usr/lib64/libTAU.so.2.19.2.debug: Двоичный файл /usr/lib/debug/usr/lib64/libTAU.so.2.19.2.debug совпадает /usr/lib/debug/.build-id/63/0ad7c92e013fc8ed72bc5eeaafc3794cf978db.debug: Двоичный файл /usr/lib/debug/.build-id/63/0ad7c92e013fc8ed72bc5eeaafc3794cf978db.debug совпадает; 
libtau-devel-static-2.19.2-alt12.x86_64	buildroot	fail	found paths to buildroot:  /usr/lib64/libTauMpi.a: Двоичный файл /usr/lib64/libTauMpi.a совпадает /usr/lib64/libTauMpi-memory-callpath-param-depthlimit-papi-mpi-pdt-openmp-opari-profile-trace-mpitrace.a: Двоичный файл /usr/lib64/libTauMpi-memory-callpath-param-depthlimit-papi-mpi-pdt-openmp-opari-profile-trace-mpitrace.a совпадает /usr/lib64/libTAU_traceinput-memory-callpath-param-depthlimit-papi-mpi-pdt-openmp-opari-profile-trace-mpitrace.a: Двоичный файл /usr/lib64/libTAU_traceinput-memory-callpath-param-depthlimit-papi-mpi-pdt-openmp-opari-profile-trace-mpitrace.a совпадает /usr/lib64/libTAU_tf.a: Двоичный файл /usr/lib64/libTAU_tf.a совпадает; 
libtrilinos10-devel-doc-10.6.4-alt4.noarch	uncompressed-manpages	info	Package contains uncompressed manual pages.; 
linuxdoc-tools-0.9.66-alt2.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.; 
linuxdoc-tools-0.9.66-alt2.x86_64	uncompressed-manpages	info	Package contains uncompressed manual pages.; 
lush-2.0.1-alt1.x86_64	buildroot	fail	found paths to buildroot:  /usr/lib64/lush/share/lush2/sys/stdenv.dump: Двоичный файл /usr/lib64/lush/share/lush2/sys/stdenv.dump совпадает /usr/lib64/lush/share/lush2/lsh/libstd/C/x86_64-alt-linux-gnu/iterator_classes.o: Двоичный файл /usr/lib64/lush/share/lush2/lsh/libstd/C/x86_64-alt-linux-gnu/iterator_classes.o совпадает /usr/lib64/lush/share/lush2/lsh/libstd/C/x86_64-alt-linux-gnu/iterator_base_class.o: Двоичный файл /usr/lib64/lush/share/lush2/lsh/libstd/C/x86_64-alt-linux-gnu/iterator_base_class.o совпадает; 
mct-2.6.0-alt4.x86_64	arch-dep-package-has-big-usr-share	info	The package has a significant amount of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.; 
mkvmerge-gui-4.8.0-alt0.M60T.1.x86_64	freedesktop-desktop	warn	desktop-file-validate utility exited abnormally with the following message(s): /usr/share/applications/mkvmerge-gui.desktop: error: (will be fatal in the future): value "GNOME" in key "Categories" in group "Desktop Entry" requires another category to be present among the following categories: GTK; 
openfoam-1.7.1-alt0.4.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package mithraen-build-utils-0.1.8-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-module-Zope2-2.13.7-alt2.noarch	altlinux-python-test-is-packaged	experimental	/usr/lib/python2.6/site-packages/Products/PageTemplates/examples/index.xml: It is the file in the package whose location matches the format python modules use for examples. It 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.6/site-packages/Products/PageTemplates/examples/zpt_examples.zexp: It is the file in the package whose location matches the format python modules use for examples. 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-module-numpy-debuginfo-2.0.0-alt2.git20110715.1.x86_64	buildroot	fail	found paths to buildroot:  /usr/lib/debug/usr/lib64/python2.6/site-packages/numpyx.so.debug: Двоичный файл /usr/lib/debug/usr/lib64/python2.6/site-packages/numpyx.so.debug совпадает /usr/lib/debug/usr/lib64/python2.6/site-packages/floatint/floatint.so.debug: Двоичный файл /usr/lib/debug/usr/lib64/python2.6/site-packages/floatint/floatint.so.debug совпадает /usr/lib/debug/.build-id/3b/995c0578d7b2a5aee0b2c847ac92b30b10c96e.debug: Двоичный файл /usr/lib/debug/.build-id/3b/995c0578d7b2a5aee0b2c847ac92b30b10c96e.debug совпадает /usr/lib/debug/.build-id/1d/6a5a91b2ec441cec972fd3d57af71c72ca1132.debug: Двоичный файл /usr/lib/debug/.build-id/1d/6a5a91b2ec441cec972fd3d57af71c72ca1132.debug совпадает; 
python-module-numpy-tests-debuginfo-2.0.0-alt2.git20110715.1.x86_64	buildroot	fail	found paths to buildroot:  /usr/lib/debug/usr/lib64/python2.6/site-packages/testnumpydistutils/gen_ext/fib3.so.debug: Двоичный файл /usr/lib/debug/usr/lib64/python2.6/site-packages/testnumpydistutils/gen_ext/fib3.so.debug совпадает /usr/lib/debug/usr/lib64/python2.6/site-packages/testnumpydistutils/f2py_ext/fib2.so.debug: Двоичный файл /usr/lib/debug/usr/lib64/python2.6/site-packages/testnumpydistutils/f2py_ext/fib2.so.debug совпадает /usr/lib/debug/usr/lib64/python2.6/site-packages/gen_ext/fib3.so.debug: Двоичный файл /usr/lib/debug/usr/lib64/python2.6/site-packages/gen_ext/fib3.so.debug совпадает /usr/lib/debug/usr/lib64/python2.6/site-packages/f2py_ext/fib2.so.debug: Двоичный файл /usr/lib/debug/usr/lib64/python2.6/site-packages/f2py_ext/fib2.so.debug совпадает /usr/lib/debug/.build-id/8c/e5065cab57559dd5365b83a388c3e2c1f1d510.debug: Двоичный файл /usr/lib/debug/.build-id/8c/e5065cab57559dd5365b83a388c3e2c1f1d510.debug совпадает /usr/lib/debug/.build-id/78/0287343ea2a421d9af845e337730c5e35d0023.debug: Двоичный файл /usr/lib/debug/.build-id/78/0287343ea2a421d9af845e337730c5e35d0023.debug совпадает /usr/lib/debug/.build-id/38/d27ce4f409beb769f7ac55bfcc60b8675df266.debug: Двоичный файл /usr/lib/debug/.build-id/38/d27ce4f409beb769f7ac55bfcc60b8675df266.debug совпадает /usr/lib/debug/.build-id/32/86d07dc9a37d3946aefe55c42bef77f716e4f4.debug: Двоичный файл /usr/lib/debug/.build-id/32/86d07dc9a37d3946aefe55c42bef77f716e4f4.debug совпадает; 
python-module-pymol-1.2_b3-alt2.svn20090726.3.x86_64	altlinux-python-test-is-packaged	experimental	/usr/lib64/python2.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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-module-scipy-doc-html-0.10.0-alt1.git20110716.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-module-scipy-doc-pdf-0.10.0-alt1.git20110716.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.; 
qhull-debuginfo-2011.1-alt1.x86_64	rpm-filesystem-conflict-symlink-file	warn	symlink /usr/lib/debug/usr/bin/qdelaunay.debug is a file in the package labplot1.6-debuginfo-1.6.0.2-alt2.qa3.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.; 
racket-5.1-alt1.x86_64	buildroot	fail	found paths to buildroot:  /usr/lib64/racket/collects/tests/slatex/compiled/test_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/slatex/compiled/test_rkt.zo совпадает /usr/lib64/racket/collects/tests/scribble/compiled/reader_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/scribble/compiled/reader_rkt.zo совпадает /usr/lib64/racket/collects/tests/scribble/compiled/preprocessor_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/scribble/compiled/preprocessor_rkt.zo совпадает /usr/lib64/racket/collects/tests/scribble/compiled/collect_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/scribble/compiled/collect_rkt.zo совпадает /usr/lib64/racket/collects/tests/racklog/compiled/unit_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/racklog/compiled/unit_rkt.zo совпадает /usr/lib64/racket/collects/tests/racklog/compiled/run-all_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/racklog/compiled/run-all_rkt.zo совпадает /usr/lib64/racket/collects/tests/racklog/compiled/mapcol_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/racklog/compiled/mapcol_rkt.zo совпадает /usr/lib64/racket/collects/tests/racklog/compiled/lang_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/racklog/compiled/lang_rkt.zo совпадает /usr/lib64/racket/collects/tests/racklog/compiled/houses_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/racklog/compiled/houses_rkt.zo совпадает /usr/lib64/racket/collects/tests/racklog/compiled/holland_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/racklog/compiled/holland_rkt.zo совпадает /usr/lib64/racket/collects/tests/racklog/compiled/fac_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/racklog/compiled/fac_rkt.zo совпадает /usr/lib64/racket/collects/tests/profile/compiled/topsort_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/profile/compiled/topsort_rkt.zo совпадает /usr/lib64/racket/collects/tests/profile/compiled/main_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/profile/compiled/main_rkt.zo совпадает /usr/lib64/racket/collects/tests/net/compiled/websocket_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/net/compiled/websocket_rkt.zo совпадает /usr/lib64/racket/collects/tests/net/compiled/url_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/net/compiled/url_rkt.zo совпадает /usr/lib64/racket/collects/tests/net/compiled/url-port_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/net/compiled/url-port_rkt.zo совпадает /usr/lib64/racket/collects/tests/net/compiled/uri-codec_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/net/compiled/uri-codec_rkt.zo совпадает /usr/lib64/racket/collects/tests/net/compiled/head_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/net/compiled/head_rkt.zo совпадает /usr/lib64/racket/collects/tests/net/compiled/ftp_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/net/compiled/ftp_rkt.zo совпадает /usr/lib64/racket/collects/tests/net/compiled/encoders_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/net/compiled/encoders_rkt.zo совпадает /usr/lib64/racket/collects/tests/net/compiled/cookie_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/net/compiled/cookie_rkt.zo совпадает /usr/lib64/racket/collects/tests/net/compiled/cgi_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/net/compiled/cgi_rkt.zo совпадает /usr/lib64/racket/collects/tests/lazy/compiled/promise_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/lazy/compiled/promise_rkt.zo совпадает /usr/lib64/racket/collects/tests/lazy/compiled/lang_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/lazy/compiled/lang_rkt.zo совпадает /usr/lib64/racket/collects/tests/lazy/compiled/forcers_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/lazy/compiled/forcers_rkt.zo совпадает /usr/lib64/racket/collects/tests/frtime/compiled/mailbox_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/frtime/compiled/mailbox_rkt.zo совпадает /usr/lib64/racket/collects/tests/frtime/compiled/heap_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/frtime/compiled/heap_rkt.zo совпадает /usr/lib64/racket/collects/tests/frtime/compiled/erl_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/frtime/compiled/erl_rkt.zo совпадает /usr/lib64/racket/collects/tests/frtime/compiled/dv_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/frtime/compiled/dv_rkt.zo совпадает /usr/lib64/racket/collects/tests/file/compiled/md5_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/file/compiled/md5_rkt.zo совпадает /usr/lib64/racket/collects/tests/file/compiled/gzip_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/file/compiled/gzip_rkt.zo совпадает /usr/lib64/racket/collects/tests/drracket/compiled/get-defs-test_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/drracket/compiled/get-defs-test_rkt.zo совпадает /usr/lib64/racket/collects/tests/datalog/compiled/racket_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/datalog/compiled/racket_rkt.zo совпадает /usr/lib64/racket/collects/tests/data/compiled/queue_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/data/compiled/queue_rkt.zo совпадает /usr/lib64/racket/collects/tests/data/compiled/gvector_rkt.zo: Двоичный файл /usr/lib64/racket/collects/tests/data/compiled/gvector_rkt.zo совпадает /usr/lib64/racket/collects/stepper/private/compiled/reconstruct_rkt.zo: Двоичный файл /usr/lib64/racket/collects/stepper/private/compiled/reconstruct_rkt.zo совпадает /usr/lib64/racket/collects/scribblings/tools/compiled/unit_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/tools/compiled/unit_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/tools/compiled/tools_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/tools/compiled/tools_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/tools/compiled/tool-lib-extracts_rkt.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/tools/compiled/tool-lib-extracts_rkt.zo совпадает /usr/lib64/racket/collects/scribblings/tools/compiled/rep_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/tools/compiled/rep_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/tools/compiled/module-language_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/tools/compiled/module-language_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/tools/compiled/module-language-tools_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/tools/compiled/module-language-tools_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/tools/compiled/modes_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/tools/compiled/modes_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/tools/compiled/language_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/tools/compiled/language_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/tools/compiled/language-configuration_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/tools/compiled/language-configuration_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/tools/compiled/help-desk_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/tools/compiled/help-desk_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/tools/compiled/get-slash-extend_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/tools/compiled/get-slash-extend_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/tools/compiled/eval_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/tools/compiled/eval_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/tools/compiled/debug_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/tools/compiled/debug_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/version_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/version_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/text_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/text_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/test_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/test_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/scheme_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/scheme_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/preferences_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/preferences_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/preferences-text_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/preferences-text_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/path-utils_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/path-utils_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/panel_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/panel_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/number-snip_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/number-snip_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/main-extracts_rkt.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/main-extracts_rkt.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/keymap_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/keymap_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/icon_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/icon_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/handler_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/handler_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/gui-utils_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/gui-utils_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/group_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/group_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/frame_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/frame_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/finder_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/finder_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/exit_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/exit_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/editor_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/editor_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/color-prefs_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/color-prefs_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/color-model_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/color-model_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/autosave_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/autosave_scrbl.zo совпадает /usr/lib64/racket/collects/scribblings/framework/compiled/application_scrbl.zo: Двоичный файл /usr/lib64/racket/collects/scribblings/framework/compiled/application_scrbl.zo совпадает /usr/lib64/racket/collects/redex/tests/compiled/tl-test_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/tests/compiled/tl-test_rkt.zo совпадает /usr/lib64/racket/collects/redex/tests/compiled/term-test_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/tests/compiled/term-test_rkt.zo совпадает /usr/lib64/racket/collects/redex/tests/compiled/rg-test_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/tests/compiled/rg-test_rkt.zo совпадает /usr/lib64/racket/collects/redex/tests/compiled/pict-test_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/tests/compiled/pict-test_rkt.zo совпадает /usr/lib64/racket/collects/redex/tests/compiled/lw-test_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/tests/compiled/lw-test_rkt.zo совпадает /usr/lib64/racket/collects/redex/tests/compiled/keyword-macros-test_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/tests/compiled/keyword-macros-test_rkt.zo совпадает /usr/lib64/racket/collects/redex/tests/compiled/hole-test_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/tests/compiled/hole-test_rkt.zo совпадает /usr/lib64/racket/collects/redex/tests/compiled/core-layout-test_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/tests/compiled/core-layout-test_rkt.zo совпадает /usr/lib64/racket/collects/redex/tests/compiled/color-test_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/tests/compiled/color-test_rkt.zo совпадает /usr/lib64/racket/collects/redex/tests/compiled/bitmap-test_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/tests/compiled/bitmap-test_rkt.zo совпадает /usr/lib64/racket/collects/redex/private/compiler/compiled/match_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/private/compiler/compiled/match_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/racket-machine/compiled/verification_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/racket-machine/compiled/verification_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/racket-machine/compiled/util_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/racket-machine/compiled/util_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/racket-machine/compiled/reduction_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/racket-machine/compiled/reduction_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/racket-machine/compiled/randomized-tests_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/racket-machine/compiled/randomized-tests_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/r6rs/compiled/r6rs_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/r6rs/compiled/r6rs_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/delim-cont/compiled/reduce_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/delim-cont/compiled/reduce_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/delim-cont/compiled/randomized-tests_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/delim-cont/compiled/randomized-tests_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/delim-cont/compiled/meta_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/delim-cont/compiled/meta_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/types_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/types_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/threads_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/threads_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/subst_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/subst_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/subject-reduction_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/subject-reduction_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/semaphores_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/semaphores_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/pi-calculus_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/pi-calculus_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/omega_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/omega_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/letrec_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/letrec_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/contracts_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/contracts_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/compatible-closure_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/compatible-closure_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/combinators_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/combinators_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/church_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/church_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/beginner_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/beginner_rkt.zo совпадает /usr/lib64/racket/collects/redex/examples/compiled/arithmetic_rkt.zo: Двоичный файл /usr/lib64/racket/collects/redex/examples/compiled/arithmetic_rkt.zo совпадает /usr/lib64/racket/collects/rackunit/private/gui/compiled/model_rkt.zo: Двоичный файл /usr/lib64/racket/collects/rackunit/private/gui/compiled/model_rkt.zo совпадает /usr/lib64/racket/collects/lang/private/compiled/teach-shared_rkt.zo: Двоичный файл /usr/lib64/racket/collects/lang/private/compiled/teach-shared_rkt.zo совпадает; 
racket-doc-5.1-alt1.noarch	buildroot	fail	found paths to buildroot:  /usr/share/doc/racket-5.1/xml/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/xml/in.sxref совпадает /usr/share/doc/racket-5.1/web-server-internal/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/web-server-internal/in.sxref совпадает /usr/share/doc/racket-5.1/web-server/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/web-server/in.sxref совпадает /usr/share/doc/racket-5.1/version/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/version/in.sxref совпадает /usr/share/doc/racket-5.1/unstable/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/unstable/in.sxref совпадает /usr/share/doc/racket-5.1/turtles/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/turtles/in.sxref совпадает /usr/share/doc/racket-5.1/ts-reference/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/ts-reference/in.sxref совпадает /usr/share/doc/racket-5.1/ts-guide/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/ts-guide/in.sxref совпадает /usr/share/doc/racket-5.1/trace/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/trace/in.sxref совпадает /usr/share/doc/racket-5.1/tools/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/tools/in.sxref совпадает /usr/share/doc/racket-5.1/test-engine/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/test-engine/in.sxref совпадает /usr/share/doc/racket-5.1/test-box-recovery/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/test-box-recovery/in.sxref совпадает /usr/share/doc/racket-5.1/syntax-color/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/syntax-color/in.sxref совпадает /usr/share/doc/racket-5.1/syntax/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/syntax/in.sxref совпадает /usr/share/doc/racket-5.1/swindle/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/swindle/in.sxref совпадает /usr/share/doc/racket-5.1/string-constants/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/string-constants/in.sxref совпадает /usr/share/doc/racket-5.1/slatex-wrap/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/slatex-wrap/in.sxref совпадает /usr/share/doc/racket-5.1/sgl/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/sgl/in.sxref совпадает /usr/share/doc/racket-5.1/search/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/search/in.sxref совпадает /usr/share/doc/racket-5.1/scriblib/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/scriblib/in.sxref совпадает /usr/share/doc/racket-5.1/scribble/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/scribble/in.sxref совпадает /usr/share/doc/racket-5.1/scheme/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/scheme/in.sxref совпадает /usr/share/doc/racket-5.1/reference/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/reference/in.sxref совпадает /usr/share/doc/racket-5.1/reference/dicts.html: (through a tail call) with no arguments to produce the result.</p></li><li><p>Otherwise, <span class="RktVar">failure-result</span> is returned as the result.</p></li></ul><p><table cellspacing="0"><tr><td><p>Examples:</p></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._racket/dict..rkt)._dict-ref))" class="RktValLink" pltdoc="x">dict-ref</a></span><span class="hspace">&nbsp;</span><span class="RktVal">#hash</span><span class="RktVal">(</span><span class="RktVal">(</span><span class="RktVal">a</span><span class="hspace">&nbsp;</span><span class="RktVal">. </span><span class="RktVal">"apple"</span><span class="RktVal">)</span><span class="hspace">&nbsp;</span><span class="RktVal">(</span><span class="RktVal">b</span><span class="hspace">&nbsp;</span><span class="RktVal">. </span><span class="RktVal">"beer"</span><span class="RktVal">)</span><span class="RktVal">)</span><span class="hspace">&nbsp;</span><span class="RktVal">'</span><span class="RktVal">a</span><span class="RktPn">)</span></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktRes">"apple"</span></p></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._racket/dict..rkt)._dict-ref))" class="RktValLink" pltdoc="x">dict-ref</a></span><span class="hspace">&nbsp;</span><span class="RktVal">#hash</span><span class="RktVal">(</span><span class="RktVal">(</span><span class="RktVal">a</span><span class="hspace">&nbsp;</span><span class="RktVal">. </span><span class="RktVal">"apple"</span><span class="RktVal">)</span><span class="hspace">&nbsp;</span><span class="RktVal">(</span><span class="RktVal">b</span><span class="hspace">&nbsp;</span><span class="RktVal">. </span><span class="RktVal">"beer"</span><span class="RktVal">)</span><span class="RktVal">)</span><span class="hspace">&nbsp;</span><span class="RktVal">'</span><span class="RktVal">c</span><span class="RktPn">)</span></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">hash-ref: no value found for key: 'c</span></p></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._racket/dict..rkt)._dict-ref))" class="RktValLink" pltdoc="x">dict-ref</a></span><span class="hspace">&nbsp;</span><span class="RktVal">#hash</span><span class="RktVal">(</span><span class="RktVal">(</span><span class="RktVal">a</span><span class="hspace">&nbsp;</span><span class="RktVal">. </span><span class="RktVal">"apple"</span><span class="RktVal">)</span><span class="hspace">&nbsp;</span><span class="RktVal">(</span><span class="RktVal">b</span><span class="hspace">&nbsp;</span><span class="RktVal">. </span><span class="RktVal">"beer"</span><span class="RktVal">)</span><span class="RktVal">)</span><span class="hspace">&nbsp;</span><span class="RktVal">'</span><span class="RktVal">c</span><span class="hspace">&nbsp;</span><span class="RktVal">#f</span><span class="RktPn">)</span></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktRes">#f</span></p></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._racket/dict..rkt)._dict-ref))" class="RktValLink" pltdoc="x">dict-ref</a></span><span class="hspace">&nbsp;</span><span class="RktVal">'</span><span class="RktVal">(</span><span class="RktVal">(</span><span class="RktVal">a</span><span class="hspace">&nbsp;</span><span class="RktVal">. </span><span class="RktVal">"apple"</span><span class="RktVal">)</span><span class="hspace">&nbsp;</span><span class="RktVal">(</span><span class="RktVal">b</span><span class="hspace">&nbsp;</span><span class="RktVal">. </span><span class="RktVal">"banana"</span><span class="RktVal">)</span><span class="RktVal">)</span><span class="hspace">&nbsp;</span><span class="RktVal">'</span><span class="RktVal">b</span><span class="RktPn">)</span></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktRes">"banana"</span></p></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._racket/dict..rkt)._dict-ref))" class="RktValLink" pltdoc="x">dict-ref</a></span><span class="hspace">&nbsp;</span><span class="RktVal">#</span><span class="RktVal">(</span><span class="RktVal">"apple"</span><span class="hspace">&nbsp;</span><span class="RktVal">"banana"</span><span class="RktVal">)</span><span class="hspace">&nbsp;</span><span class="RktVal">1</span><span class="RktPn">)</span></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktRes">"banana"</span></p></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._racket/dict..rkt)._dict-ref))" class="RktValLink" pltdoc="x">dict-ref</a></span><span class="hspace">&nbsp;</span><span class="RktVal">#</span><span class="RktVal">(</span><span class="RktVal">"apple"</span><span class="hspace">&nbsp;</span><span class="RktVal">"banana"</span><span class="RktVal">)</span><span class="hspace">&nbsp;</span><span class="RktVal">3</span><span class="hspace">&nbsp;</span><span class="RktVal">#f</span><span class="RktPn">)</span></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktRes">#f</span></p></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._racket/dict..rkt)._dict-ref))" class="RktValLink" pltdoc="x">dict-ref</a></span><span class="hspace">&nbsp;</span><span class="RktVal">#</span><span class="RktVal">(</span><span class="RktVal">"apple"</span><span class="hspace">&nbsp;</span><span class="RktVal">"banana"</span><span class="RktVal">)</span><span class="hspace">&nbsp;</span><span class="RktVal"><span class="nobreak">-3</span></span><span class="hspace">&nbsp;</span><span class="RktVal">#f</span><span class="RktPn">)</span></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">contract violation: expected &lt;exact-nonnegative-integer?&gt;,</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">given: -3</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">contract on dict-ref from </span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">(file</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">/usr/src/tmp/racket-buildroot/usr/lib/racket/collects/racket</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">/dict.rkt)</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">blaming top-level</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">contract: </span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">(-&gt;i</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"> </span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">((d dict?) (k (d) ...))</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"> </span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">((default any/c))</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"> </span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">any)</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">at: &lt;collects&gt;/racket/dict.rkt:147.2</span></p></td></tr></table></p><p><div class="SIntrapara"><table cellspacing="0" class="boxed"><tr><td><span class="RktPn">(</span><a name="(dep._((lib._racket/dict..rkt)._dict-ref!))"></a><a name="(def._((lib._racket/dict..rkt)._dict-ref!))"></a><span title="Provided from: racket/dict, racket"><span class="RktSym"><a href="#(def._((lib._racket/dict..rkt)._dict-ref!))" class="RktValLink" pltdoc="x">dict-ref!</a></span></span><span class="hspace">&nbsp;</span><span class="RktVar">dict</span><span class="hspace">&nbsp;</span><span class="RktVar">key</span><span class="hspace">&nbsp;</span><span class="RktVar">to-set</span><span class="RktPn">)</span><span class="hspace">&nbsp;</span>&rarr;<span class="hspace">&nbsp;</span><span class="RktSym"><a href="Data-structure_Contracts.html#(form._((lib._racket/contract/private/guts..rkt)._any))" class="RktStxLink" pltdoc="x">any</a></span></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="RktVar">dict</span><span class="hspace">&nbsp;</span>:<span class="hspace">&nbsp;</span><span class="RktSym"><a href="#(def._((lib._racket/dict..rkt)._dict~3f))" class="RktValLink" pltdoc="x">dict?</a></span></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="RktVar">key</span><span class="hspace">&nbsp;</span>:<span class="hspace">&nbsp;</span><span class="RktSym"><a href="Data-structure_Contracts.html#(def._((lib._racket/contract/private/guts..rkt)._any/c))" class="RktValLink" pltdoc="x">any/c</a></span></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="RktVar">to-set</span><span class="hspace">&nbsp;</span>:<span class="hspace">&nbsp;</span><span class="RktSym"><a href="Data-structure_Contracts.html#(def._((lib._racket/contract/private/guts..rkt)._any/c))" class="RktValLink" pltdoc="x">any/c</a></span></td></tr></table></div><div class="SIntrapara">Returns the value for <span class="RktVar">key</span> in <span class="RktVar">dict</span>. If no value /usr/share/doc/racket-5.1/redex/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/redex/in.sxref совпадает /usr/share/doc/racket-5.1/readline/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/readline/in.sxref совпадает /usr/share/doc/racket-5.1/raco/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/raco/in.sxref совпадает /usr/share/doc/racket-5.1/rackunit/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/rackunit/in.sxref совпадает /usr/share/doc/racket-5.1/racklog/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/racklog/in.sxref совпадает /usr/share/doc/racket-5.1/r6rs/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/r6rs/in.sxref совпадает /usr/share/doc/racket-5.1/r5rs/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/r5rs/in.sxref совпадает /usr/share/doc/racket-5.1/quick/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/quick/in.sxref совпадает /usr/share/doc/racket-5.1/profile/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/profile/in.sxref совпадает /usr/share/doc/racket-5.1/preprocessor/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/preprocessor/in.sxref совпадает /usr/share/doc/racket-5.1/plot/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/plot/in.sxref совпадает /usr/share/doc/racket-5.1/planet/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/planet/in.sxref совпадает /usr/share/doc/racket-5.1/plai/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/plai/in.sxref совпадает /usr/share/doc/racket-5.1/picturing-programs/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/picturing-programs/in.sxref совпадает /usr/share/doc/racket-5.1/parser-tools/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/parser-tools/in.sxref совпадает /usr/share/doc/racket-5.1/openssl/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/openssl/in.sxref совпадает /usr/share/doc/racket-5.1/net/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/net/in.sxref совпадает /usr/share/doc/racket-5.1/mzscheme/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/mzscheme/in.sxref совпадает /usr/share/doc/racket-5.1/mzlib/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/mzlib/in.sxref совпадает /usr/share/doc/racket-5.1/mzcom/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/mzcom/in.sxref совпадает /usr/share/doc/racket-5.1/mysterx/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/mysterx/in.sxref совпадает /usr/share/doc/racket-5.1/mrlib/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/mrlib/in.sxref совпадает /usr/share/doc/racket-5.1/more/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/more/in.sxref совпадает /usr/share/doc/racket-5.1/make/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/make/in.sxref совпадает /usr/share/doc/racket-5.1/macro-debugger/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/macro-debugger/in.sxref совпадает /usr/share/doc/racket-5.1/lazy/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/lazy/in.sxref совпадает /usr/share/doc/racket-5.1/inside/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/inside/in.sxref совпадает /usr/share/doc/racket-5.1/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/in.sxref совпадает /usr/share/doc/racket-5.1/html/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/html/in.sxref совпадает /usr/share/doc/racket-5.1/htdp-lib/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/htdp-lib/in.sxref совпадает /usr/share/doc/racket-5.1/htdp-langs/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/htdp-langs/in.sxref совпадает /usr/share/doc/racket-5.1/honu/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/honu/in.sxref совпадает /usr/share/doc/racket-5.1/guide/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/guide/in.sxref совпадает /usr/share/doc/racket-5.1/gui/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/gui/in.sxref совпадает /usr/share/doc/racket-5.1/graphics/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/graphics/in.sxref совпадает /usr/share/doc/racket-5.1/gl-board-game/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/gl-board-game/in.sxref совпадает /usr/share/doc/racket-5.1/getting-started/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/getting-started/in.sxref совпадает /usr/share/doc/racket-5.1/games/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/games/in.sxref совпадает /usr/share/doc/racket-5.1/frtime/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/frtime/in.sxref совпадает /usr/share/doc/racket-5.1/framework/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/framework/in.sxref совпадает /usr/share/doc/racket-5.1/foreign/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/foreign/in.sxref совпадает /usr/share/doc/racket-5.1/file/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/file/in.sxref совпадает /usr/share/doc/racket-5.1/errortrace/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/errortrace/in.sxref совпадает /usr/share/doc/racket-5.1/eopl/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/eopl/in.sxref совпадает /usr/share/doc/racket-5.1/embedded-gui/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/embedded-gui/in.sxref совпадает /usr/share/doc/racket-5.1/dynext/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/dynext/in.sxref совпадает /usr/share/doc/racket-5.1/drracket/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/drracket/in.sxref совпадает /usr/share/doc/racket-5.1/deinprogramm/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/deinprogramm/in.sxref совпадает /usr/share/doc/racket-5.1/datalog/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/datalog/in.sxref совпадает /usr/share/doc/racket-5.1/data/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/data/in.sxref совпадает /usr/share/doc/racket-5.1/data/Splay_Trees.html: combined with <span class="RktVar">key-contract</span> to check keys.</div></p><p><table cellspacing="0"><tr><td><p>Examples:</p></td></tr><tr><td><table cellspacing="0" class="RktBlk"><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="../reference/define.html#(form._((lib._racket/private/base..rkt)._define))" class="RktStxLink" pltdoc="x">define</a></span><span class="hspace">&nbsp;</span><span class="RktSym">splay-tree</span></td></tr><tr><td><span class="RktPlain"><span class="hspace">&nbsp;&nbsp;&nbsp;&nbsp;</span></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._data/splay-tree..rkt)._make-splay-tree))" class="RktValLink" pltdoc="x">make-splay-tree</a></span><span class="hspace">&nbsp;</span><span class="RktPn">(</span><span class="RktSym"><a href="Orders_and_Ordered_Dictionaries.html#(def._((lib._data/order..rkt)._order))" class="RktValLink" pltdoc="x">order</a></span><span class="hspace">&nbsp;</span><span class="RktVal">'</span><span class="RktVal">string-order</span><span class="hspace">&nbsp;</span><span class="RktSym"><a href="../reference/strings.html#(def._((quote._~23~25kernel)._string~3f))" class="RktValLink" pltdoc="x">string?</a></span><span class="hspace">&nbsp;</span><span class="RktSym"><a href="../reference/strings.html#(def._((quote._~23~25kernel)._string~3d~3f))" class="RktValLink" pltdoc="x">string=?</a></span><span class="hspace">&nbsp;</span><span class="RktSym"><a href="../reference/strings.html#(def._((quote._~23~25kernel)._string~3c~3f))" class="RktValLink" pltdoc="x">string&lt;?</a></span><span class="RktPn">)</span><span class="RktPn">)</span><span class="RktPn">)</span></td></tr></table></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._data/splay-tree..rkt)._splay-tree-set!))" class="RktValLink" pltdoc="x">splay-tree-set!</a></span><span class="hspace">&nbsp;</span><span class="RktSym">splay-tree</span><span class="hspace">&nbsp;</span><span class="RktVal">"dot"</span><span class="hspace">&nbsp;</span><span class="RktVal">10</span><span class="RktPn">)</span></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._data/splay-tree..rkt)._splay-tree-set!))" class="RktValLink" pltdoc="x">splay-tree-set!</a></span><span class="hspace">&nbsp;</span><span class="RktSym">splay-tree</span><span class="hspace">&nbsp;</span><span class="RktVal">"cherry"</span><span class="hspace">&nbsp;</span><span class="RktVal">500</span><span class="RktPn">)</span></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="../reference/dicts.html#(def._((lib._racket/dict..rkt)._dict-map))" class="RktValLink" pltdoc="x">dict-map</a></span><span class="hspace">&nbsp;</span><span class="RktSym">splay-tree</span><span class="hspace">&nbsp;</span><span class="RktSym"><a href="../reference/pairs.html#(def._((quote._~23~25kernel)._list))" class="RktValLink" pltdoc="x">list</a></span><span class="RktPn">)</span></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktRes">'(("cherry"<span class="stt"> </span>500)<span class="stt"> </span>("dot"<span class="stt"> </span>10))</span></p></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._data/splay-tree..rkt)._splay-tree-ref))" class="RktValLink" pltdoc="x">splay-tree-ref</a></span><span class="hspace">&nbsp;</span><span class="RktSym">splay-tree</span><span class="hspace">&nbsp;</span><span class="RktVal">"dot"</span><span class="RktPn">)</span></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktRes">10</span></p></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._data/splay-tree..rkt)._splay-tree-remove!))" class="RktValLink" pltdoc="x">splay-tree-remove!</a></span><span class="hspace">&nbsp;</span><span class="RktSym">splay-tree</span><span class="hspace">&nbsp;</span><span class="RktVal">"cherry"</span><span class="RktPn">)</span></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._data/splay-tree..rkt)._splay-tree-count))" class="RktValLink" pltdoc="x">splay-tree-count</a></span><span class="hspace">&nbsp;</span><span class="RktSym">splay-tree</span><span class="RktPn">)</span></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktRes">1</span></p></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="stt">&gt; </span><span class="RktPn">(</span><span class="RktSym"><a href="#(def._((lib._data/splay-tree..rkt)._splay-tree-set!))" class="RktValLink" pltdoc="x">splay-tree-set!</a></span><span class="hspace">&nbsp;</span><span class="RktSym">splay-tree</span><span class="hspace">&nbsp;</span><span class="RktVal">'</span><span class="RktVal">pear</span><span class="hspace">&nbsp;</span><span class="RktVal">3</span><span class="RktPn">)</span></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">contract violation: expected &lt;string?&gt;, given: 'pear</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">contract on splay-tree-set! from </span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">(file</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">/usr/src/tmp/racket-buildroot/usr/lib/racket/collects/data/s</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">play-tree.rkt)</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">blaming top-level</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">contract: </span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">(-&gt;i</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"> </span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">((s splay-tree?) (key (s) ...) (v (s) ...))</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"> </span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">(_r void?))</span></p></td></tr><tr><td><p><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr"></span><span class="hspace">&nbsp;&nbsp;</span><span class="RktErr">at: &lt;collects&gt;/data/splay-tree.rkt:1112.2</span></p></td></tr></table></p><p><div class="SIntrapara"><table cellspacing="0" class="boxed"><tr><td><table cellspacing="0" class="prototype"><tr><td><span class="RktPn">(</span><a name="(dep._((lib._data/splay-tree..rkt)._make-adjustable-splay-tree))"></a><a name="(def._((lib._data/splay-tree..rkt)._make-adjustable-splay-tree))"></a><span title="Provided from: data/splay-tree"><span class="RktSym"><a href="#(def._((lib._data/splay-tree..rkt)._make-adjustable-splay-tree))" class="RktValLink" pltdoc="x">make-adjustable-splay-tree</a></span></span></td><td><span class="hspace">&nbsp;</span>[</td><td><span class="RktPn">#:key-contract</span><span class="hspace">&nbsp;</span><span class="RktVar">key-contract</span></td><td><span class="hspace">&nbsp;</span></td></tr><tr><td><span class="hspace">&nbsp;</span></td><td><span class="hspace">&nbsp;</span></td><td><span class="RktPn">#:value-contract</span><span class="hspace">&nbsp;</span><span class="RktVar">value-contract</span>]<span class="RktPn">)</span></td><td><span class="hspace">&nbsp;</span></td></tr></table></td></tr><tr><td><span class="hspace">&nbsp;</span>&rarr;<span class="hspace">&nbsp;</span><span class="RktSym"><a href="#(def._((lib._data/splay-tree..rkt)._splay-tree~3f))" class="RktValLink" pltdoc="x">splay-tree?</a></span></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="RktVar">key-contract</span><span class="hspace">&nbsp;</span>:<span class="hspace">&nbsp;</span><span class="RktSym"><a href="../reference/Contract_Utilities.html#(def._((lib._racket/contract/private/guts..rkt)._contract~3f))" class="RktValLink" pltdoc="x">contract?</a></span><span class="hspace">&nbsp;</span>=<span class="hspace">&nbsp;</span><span class="RktSym"><a href="../reference/Data-structure_Contracts.html#(def._((lib._racket/contract/private/guts..rkt)._any/c))" class="RktValLink" pltdoc="x">any/c</a></span></td></tr><tr><td><span class="hspace">&nbsp;&nbsp;</span><span class="RktVar">value-contract</span><span class="hspace">&nbsp;</span>:<span class="hspace">&nbsp;</span><span class="RktSym"><a href="../reference/Contract_Utilities.html#(def._((lib._racket/contract/private/guts..rkt)._contract~3f))" class="RktValLink" pltdoc="x">contract?</a></span><span class="hspace">&nbsp;</span>=<span class="hspace">&nbsp;</span><span class="RktSym"><a href="../reference/Data-structure_Contracts.html#(def._((lib._racket/contract/private/guts..rkt)._any/c))" class="RktValLink" pltdoc="x">any/c</a></span></td></tr></table></div><div class="SIntrapara">Makes a new empty splay-tree that permits only exact integers as keys /usr/share/doc/racket-5.1/continue/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/continue/in.sxref совпадает /usr/share/doc/racket-5.1/config/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/config/in.sxref совпадает /usr/share/doc/racket-5.1/cffi/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/cffi/in.sxref совпадает /usr/share/doc/racket-5.1/cards/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/cards/in.sxref совпадает /usr/share/doc/racket-5.1/browser/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/browser/in.sxref совпадает /usr/share/doc/racket-5.1/algol60/in.sxref: Двоичный файл /usr/share/doc/racket-5.1/algol60/in.sxref совпадает; 
raptor-debuginfo-1.4.21-alt2.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package raptor2-debuginfo-2.0.4-alt0.M60P.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.; 
scotch-5.1.10-alt1.svn20101007.2.x86_64	uncompressed-manpages	info	Package contains uncompressed manual pages.; 
scribus-1.4.0-alt1.rc3.x86_64	freedesktop-desktop	info	desktop-file-validate utility printed the following message(s): /usr/share/applications/scribus.desktop: warning: value "Werkskerm Publisering" for key "Comment[af]" in group "Desktop Entry" looks redundant with value "Werkskerm Publisering" of key "GenericName[af]"; /usr/share/applications/scribus.desktop: warning: value "?????????? ????????" for key "Comment[bg]" in group "Desktop Entry" looks redundant with value "?????????? ????????" of key "GenericName[bg]"; /usr/share/applications/scribus.desktop: warning: value "Stono izdava?tvo (DTP)" for key "Comment[bs]" in group "Desktop Entry" looks redundant with value "Stono izdava?tvo (DTP)" of key "GenericName[bs]"; /usr/share/applications/scribus.desktop: warning: value "Publicaci? d'escriptori" for key "Comment[ca]" in group "Desktop Entry" looks redundant with value "Publicaci? d'escriptori" of key "GenericName[ca]"; /usr/share/applications/scribus.desktop: warning: value "Publika?n? syst?m (DTP)" for key "Comment[cs]" in group "Desktop Entry" looks redundant with value "Publika?n? syst?m (DTP)" of key "GenericName[cs]"; /usr/share/applications/scribus.desktop: warning: value "Cyhoeddi Penbwrdd" for key "Comment[cy]" in group "Desktop Entry" looks redundant with value "Cyhoeddi Penbwrdd" of key "GenericName[cy]"; /usr/share/applications/scribus.desktop: warning: value "Dtp" for key "Comment[da]" in group "Desktop Entry" looks redundant with value "Dtp" of key "GenericName[da]"; /usr/share/applications/scribus.desktop: warning: value "DTP-programo" for key "Comment[eo]" in group "Desktop Entry" looks redundant with value "DTP-programo" of key "GenericName[eo]"; /usr/share/applications/scribus.desktop: warning: value "Publicaci?n de escritorio" for key "Comment[es]" in group "Desktop Entry" looks redundant with value "Publicaci?n de escritorio" of key "GenericName[es]"; /usr/share/applications/scribus.desktop: warning: value "K?ljendusrakendus" for key "Comment[et]" in group "Desktop Entry" looks redundant with value "K?ljendusrakendus" of key "GenericName[et]"; /usr/share/applications/scribus.desktop: warning: value "Julkaisuohjelma" for key "Comment[fi]" in group "Desktop Entry" looks redundant with value "Julkaisuohjelma" of key "GenericName[fi]"; /usr/share/applications/scribus.desktop: warning: value "Publication assist?e par ordinateur (PAO)" for key "Comment[fr]" in group "Desktop Entry" looks redundant with value "Publication assist?e par ordinateur (PAO)" of key "GenericName[fr]"; /usr/share/applications/scribus.desktop: warning: value "????? ???? ???????" for key "Comment[he]" in group "Desktop Entry" looks redundant with value "????? ???? ???????" of key "GenericName[he]"; /usr/share/applications/scribus.desktop: warning: value "Stolno izdava?tvo" for key "Comment[hr]" in group "Desktop Entry" looks redundant with value "Stolno izdava?tvo" of key "GenericName[hr]"; /usr/share/applications/scribus.desktop: warning: value "Kiadv?nyszerkeszt?s" for key "Comment[hu]" in group "Desktop Entry" looks redundant with value "Kiadv?nyszerkeszt?s" of key "GenericName[hu]"; /usr/share/applications/scribus.desktop: warning: value "Pubblicazioni" for key "Comment[it]" in group "Desktop Entry" looks redundant with value "Pubblicazioni" of key "GenericName[it]"; /usr/share/applications/scribus.desktop: warning: value "?????????????" for key "Comment[ja]" in group "Desktop Entry" looks redundant with value "?????????????" of key "GenericName[ja]"; /usr/share/applications/scribus.desktop: warning: value "????????????????" for key "Comment[lo]" in group "Desktop Entry" looks redundant with value "????????????????" of key "GenericName[lo]"; /usr/share/applications/scribus.desktop: warning: value "Darbastalio leidykla" for key "Comment[lt]" in group "Desktop Entry" looks redundant with value "Darbastalio leidykla" of key "GenericName[lt]"; /usr/share/applications/scribus.desktop: warning: value "Datatrykkeprogram" for key "Comment[nb]" in group "Desktop Entry" looks redundant with value "Datatrykkeprogram" of key "GenericName[nb]"; /usr/share/applications/scribus.desktop: warning: value "Datatrykk" for key "Comment[nn]" in group "Desktop Entry" looks redundant with value "Datatrykk" of key "GenericName[nn]"; /usr/share/applications/scribus.desktop: warning: value "Kwalakwatso ya Desktop" for key "Comment[nso]" in group "Desktop Entry" looks redundant with value "Kwalakwatso ya Desktop" of key "GenericName[nso]"; /usr/share/applications/scribus.desktop: warning: value "Program do sk?adu tekstu" for key "Comment[pl]" in group "Desktop Entry" looks redundant with value "Program do sk?adu tekstu" of key "GenericName[pl]"; /usr/share/applications/scribus.desktop: warning: value "Edi??o electr?nica" for key "Comment[pt]" in group "Desktop Entry" looks redundant with value "Edi??o Electr?nica" of key "GenericName[pt]"; /usr/share/applications/scribus.desktop: warning: value "Editora??o eletr?nica" for key "Comment[pt_BR]" in group "Desktop Entry" looks redundant with value "Editora??o eletr?nica" of key "GenericName[pt_BR]"; /usr/share/applications/scribus.desktop: warning: value "Namizno zalo?ni?tvo" for key "Comment[sl]" in group "Desktop Entry" looks redundant with value "Namizno zalo?ni?tvo" of key "GenericName[sl]"; /usr/share/applications/scribus.desktop: warning: value "????? ??????????" for key "Comment[sr]" in group "Desktop Entry" looks redundant with value "????? ??????????" of key "GenericName[sr]"; /usr/share/applications/scribus.desktop: warning: value "Kushicelela ku desktop" for key "Comment[ss]" in group "Desktop Entry" looks redundant with value "Kushicelela ku desktop" of key "GenericName[ss]"; /usr/share/applications/scribus.desktop: warning: value "Desktop Publishing" for key "Comment[sv]" in group "Desktop Entry" looks redundant with value "Desktop Publishing" of key "GenericName[sv]"; /usr/share/applications/scribus.desktop: warning: value "?????????????????" for key "Comment[th]" in group "Desktop Entry" looks redundant with value "?????????????????" of key "GenericName[th]"; /usr/share/applications/scribus.desktop: warning: value "Masa?st? Yay?nc?l?k" for key "Comment[tr]" in group "Desktop Entry" looks redundant with value "Masa?st? Yay?nc?l?k" of key "GenericName[tr]"; /usr/share/applications/scribus.desktop: warning: value "????????? ???????" for key "Comment[uk]" in group "Desktop Entry" looks redundant with value "????????? ???????" of key "GenericName[uk]"; /usr/share/applications/scribus.desktop: warning: value "????? ???????" for key "Comment[uz]" in group "Desktop Entry" looks redundant with value "????? ???????" of key "GenericName[uz]"; /usr/share/applications/scribus.desktop: warning: value "U andadza Desikithopo" for key "Comment[ven]" in group "Desktop Entry" looks redundant with value "U andadza Desikithopo" of key "GenericName[ven]"; /usr/share/applications/scribus.desktop: warning: value "Upapasho lwe Desktop" for key "Comment[xh]" in group "Desktop Entry" looks redundant with value "Upapasho lwe Desktop" of key "GenericName[xh]"; /usr/share/applications/scribus.desktop: warning: value "????" for key "Comment[zh_CN]" in group "Desktop Entry" looks redundant with value "????" of key "GenericName[zh_CN]"; /usr/share/applications/scribus.desktop: warning: value "????" for key "Comment[zh_TW]" in group "Desktop Entry" looks redundant with value "????" of key "GenericName[zh_TW]"; /usr/share/applications/scribus.desktop: warning: value "Ukushicilelwa kwe-Desktop" for key "Comment[zu]" in group "Desktop Entry" looks redundant with value "Ukushicilelwa kwe-Desktop" of key "GenericName[zu]"; 
shogun-0.9.3-alt2.x86_64	big-changelog	info	Package contains big ChangeLog. Gzip it.; 
sifdec-2.0.0-alt1.svn20090528.1.x86_64	rpm-filesystem-conflict-file-file	warn	There are file conflicts with the package libxforms-demos-1.0.93-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.; 
tau-debuginfo-2.19.2-alt12.x86_64	buildroot	fail	found paths to buildroot:  /usr/lib/debug/usr/bin/trace2profile.debug: Двоичный файл /usr/lib/debug/usr/bin/trace2profile.debug совпадает /usr/lib/debug/usr/bin/tau_timecorrect.debug: Двоичный файл /usr/lib/debug/usr/bin/tau_timecorrect.debug совпадает /usr/lib/debug/usr/bin/tau2profile.debug: Двоичный файл /usr/lib/debug/usr/bin/tau2profile.debug совпадает /usr/lib/debug/usr/bin/tau2otf.debug: Двоичный файл /usr/lib/debug/usr/bin/tau2otf.debug совпадает /usr/lib/debug/usr/bin/tau2elg.debug: Двоичный файл /usr/lib/debug/usr/bin/tau2elg.debug совпадает /usr/lib/debug/.build-id/f2/738ae7ad037aec40c782d36eae6d5a46b7e839.debug: Двоичный файл /usr/lib/debug/.build-id/f2/738ae7ad037aec40c782d36eae6d5a46b7e839.debug совпадает /usr/lib/debug/.build-id/e6/c79f221eea1eabe65e4ac19200ed215d252ed3.debug: Двоичный файл /usr/lib/debug/.build-id/e6/c79f221eea1eabe65e4ac19200ed215d252ed3.debug совпадает /usr/lib/debug/.build-id/ba/c4ea35068b0841cae2990076c563cc4f5da7c1.debug: Двоичный файл /usr/lib/debug/.build-id/ba/c4ea35068b0841cae2990076c563cc4f5da7c1.debug совпадает /usr/lib/debug/.build-id/58/7754cb1d3a9ffc0e06a70c993e31f88e34b22d.debug: Двоичный файл /usr/lib/debug/.build-id/58/7754cb1d3a9ffc0e06a70c993e31f88e34b22d.debug совпадает /usr/lib/debug/.build-id/06/dc406dbb337fd66b8575817697c624a878e9fd.debug: Двоичный файл /usr/lib/debug/.build-id/06/dc406dbb337fd66b8575817697c624a878e9fd.debug совпадает;