dev-python/poetry-1.0.10 collides with dev-python/poetry-core-1.0.0_alpha9 #119

New Issue

onkelbeh · 2020-09-08T20:08:35+02:00

onkelbeh commented

2020-09-08 20:08:35 +02:00

 * Package:    dev-python/poetry-1.0.10
 * Repository: HomeAssistantRepository
 * Maintainer: b@edevau.net
 * Upstream:   sebastien@eustace.io
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_python3_8 test userland_GNU
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking poetry-1.0.10.tar.gz to /var/tmp/portage/dev-python/poetry-1.0.10/work
>>> Source unpacked in /var/tmp/portage/dev-python/poetry-1.0.10/work
>>> Preparing source in /var/tmp/portage/dev-python/poetry-1.0.10/work/poetry-1.0.10 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-python/poetry-1.0.10/work/poetry-1.0.10 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-python/poetry-1.0.10/work/poetry-1.0.10 ...
 * python3_8: running distutils-r1_run_phase distutils-r1_python_compile
 * DISTUTILS_USE_SETUPTOOLS value is probably incorrect
 *   value:    DISTUTILS_USE_SETUPTOOLS=bdepend (default?)
 *   expected: DISTUTILS_USE_SETUPTOOLS=rdepend
>>> Done.
 * checking 723 files for package collisions
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 *
 * Detected file collision(s):
 *
 *      /usr/lib/python3.8/site-packages/poetry/__init__.py
 *      /usr/lib/python3.8/site-packages/poetry/__pycache__/__init__.cpython-38.opt-2.pyc
 *      /usr/lib/python3.8/site-packages/poetry/__pycache__/__init__.cpython-38.opt-1.pyc
 *      /usr/lib/python3.8/site-packages/poetry/__pycache__/__init__.cpython-38.pyc
 *
 * Searching all installed packages for file collisions...
 *
 * Press Ctrl-C to Stop
 *
 * dev-python/poetry-core-1.0.0_alpha9:0::HomeAssistantRepository
 *      /usr/lib/python3.8/site-packages/poetry/__init__.py
 *      /usr/lib/python3.8/site-packages/poetry/__pycache__/__init__.cpython-38.opt-1.pyc
 *      /usr/lib/python3.8/site-packages/poetry/__pycache__/__init__.cpython-38.opt-2.pyc
 *      /usr/lib/python3.8/site-packages/poetry/__pycache__/__init__.cpython-38.pyc
 *
 * Package 'dev-python/poetry-1.0.10' NOT merged due to file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.

``` * Package: dev-python/poetry-1.0.10 * Repository: HomeAssistantRepository * Maintainer: b@edevau.net * Upstream: sebastien@eustace.io * USE: abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_python3_8 test userland_GNU * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox >>> Unpacking source... >>> Unpacking poetry-1.0.10.tar.gz to /var/tmp/portage/dev-python/poetry-1.0.10/work >>> Source unpacked in /var/tmp/portage/dev-python/poetry-1.0.10/work >>> Preparing source in /var/tmp/portage/dev-python/poetry-1.0.10/work/poetry-1.0.10 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-python/poetry-1.0.10/work/poetry-1.0.10 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-python/poetry-1.0.10/work/poetry-1.0.10 ... * python3_8: running distutils-r1_run_phase distutils-r1_python_compile * DISTUTILS_USE_SETUPTOOLS value is probably incorrect * value: DISTUTILS_USE_SETUPTOOLS=bdepend (default?) * expected: DISTUTILS_USE_SETUPTOOLS=rdepend >>> Done. * checking 723 files for package collisions * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at https://bugs.gentoo.org/ unless you report exactly * which two packages install the same file(s). See * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how * to solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /usr/lib/python3.8/site-packages/poetry/__init__.py * /usr/lib/python3.8/site-packages/poetry/__pycache__/__init__.cpython-38.opt-2.pyc * /usr/lib/python3.8/site-packages/poetry/__pycache__/__init__.cpython-38.opt-1.pyc * /usr/lib/python3.8/site-packages/poetry/__pycache__/__init__.cpython-38.pyc * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * dev-python/poetry-core-1.0.0_alpha9:0::HomeAssistantRepository * /usr/lib/python3.8/site-packages/poetry/__init__.py * /usr/lib/python3.8/site-packages/poetry/__pycache__/__init__.cpython-38.opt-1.pyc * /usr/lib/python3.8/site-packages/poetry/__pycache__/__init__.cpython-38.opt-2.pyc * /usr/lib/python3.8/site-packages/poetry/__pycache__/__init__.cpython-38.pyc * * Package 'dev-python/poetry-1.0.10' NOT merged due to file collisions. * If necessary, refer to your elog messages for the whole content of the * above message. ```

onkelbeh added this to the Compile all components without USEFLAGS (2020/09) milestone 2020-09-08 20:08:35 +02:00

onkelbeh added the

Bug

label 2020-09-08 20:08:35 +02:00

onkelbeh added the

File Collision

label 2020-09-08 22:57:41 +02:00

onkelbeh commented

2020-09-09 22:24:25 +02:00

TEST: remove core dependency: 0202fd4e67

TEST: remove core dependency: https://git.edevau.net/onkelbeh/HomeAssistantRepository/commit/0202fd4e678add28e24aecd3c4400fcea12bb6e4

onkelbeh closed this issue