dev-python/coronavirus-1.1.1 needs immutables BDEPEND #124

New Issue

onkelbeh · 2020-09-08T20:17:34+02:00

onkelbeh commented

2020-09-08 20:17:34 +02:00

 * Package:    dev-python/coronavirus-1.1.1
 * Repository: HomeAssistantRepository
 * Maintainer: b@edevau.net
 * Upstream:   opensource@nabucasa.com
 * 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 coronavirus-1.1.1.tar.gz to /var/tmp/portage/dev-python/coronavirus-1.1.1/work
>>> Source unpacked in /var/tmp/portage/dev-python/coronavirus-1.1.1/work
>>> Preparing source in /var/tmp/portage/dev-python/coronavirus-1.1.1/work/coronavirus-1.1.1 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-python/coronavirus-1.1.1/work/coronavirus-1.1.1 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-python/coronavirus-1.1.1/work/coronavirus-1.1.1 ...
 * python3_8: running distutils-r1_run_phase distutils-r1_python_compile
python3.8 setup.py build -j 10
running build
running build_py
creating /var/tmp/portage/dev-python/coronavirus-1.1.1/work/coronavirus-1.1.1-python3_8/lib/coronavirus
copying coronavirus/__init__.py -> /var/tmp/portage/dev-python/coronavirus-1.1.1/work/coronavirus-1.1.1-python3_8/lib/coronavirus
running egg_info
writing coronavirus.egg-info/PKG-INFO
writing dependency_links to coronavirus.egg-info/dependency_links.txt
writing requirements to coronavirus.egg-info/requires.txt
writing top-level names to coronavirus.egg-info/top_level.txt
reading manifest file 'coronavirus.egg-info/SOURCES.txt'
writing manifest file 'coronavirus.egg-info/SOURCES.txt'
warning: build_py: byte-compiling is disabled, skipping.

>>> Source compiled.
>>> Test phase [not enabled]: dev-python/coronavirus-1.1.1
Traceback (most recent call last):
  File "/usr/lib/portage/python3.8/ebuild-ipc.py", line 48, in <module>
    from portage.util._eventloop.global_event_loop import global_event_loop
  File "/usr/lib/python3.8/site-packages/portage/util/_eventloop/global_event_loop.py", line 5, in <module>
    from .EventLoop import EventLoop
  File "/usr/lib/python3.8/site-packages/portage/util/_eventloop/EventLoop.py", line 4, in <module>
    import asyncio as _real_asyncio
  File "/usr/lib/python3.8/asyncio/__init__.py", line 8, in <module>
    from .base_events import *
  File "/usr/lib/python3.8/asyncio/base_events.py", line 40, in <module>
    from . import events
  File "/usr/lib/python3.8/asyncio/events.py", line 14, in <module>
    import contextvars
  File "/usr/lib/python3.8/site-packages/contextvars/__init__.py", line 4, in <module>
    import immutables
ModuleNotFoundError: No module named 'immutables'
 * The ebuild phase 'test' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
Traceback (most recent call last):
  File "/usr/lib/portage/python3.8/ebuild-ipc.py", line 48, in <module>
    from portage.util._eventloop.global_event_loop import global_event_loop
  File "/usr/lib/python3.8/site-packages/portage/util/_eventloop/global_event_loop.py", line 5, in <module>
    from .EventLoop import EventLoop
  File "/usr/lib/python3.8/site-packages/portage/util/_eventloop/EventLoop.py", line 4, in <module>
    import asyncio as _real_asyncio
  File "/usr/lib/python3.8/asyncio/__init__.py", line 8, in <module>
    from .base_events import *
  File "/usr/lib/python3.8/asyncio/base_events.py", line 40, in <module>
    from . import events
  File "/usr/lib/python3.8/asyncio/events.py", line 14, in <module>
    import contextvars
  File "/usr/lib/python3.8/site-packages/contextvars/__init__.py", line 4, in <module>
    import immutables
ModuleNotFoundError: No module named 'immutables'
 * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.

``` * Package: dev-python/coronavirus-1.1.1 * Repository: HomeAssistantRepository * Maintainer: b@edevau.net * Upstream: opensource@nabucasa.com * 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 coronavirus-1.1.1.tar.gz to /var/tmp/portage/dev-python/coronavirus-1.1.1/work >>> Source unpacked in /var/tmp/portage/dev-python/coronavirus-1.1.1/work >>> Preparing source in /var/tmp/portage/dev-python/coronavirus-1.1.1/work/coronavirus-1.1.1 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-python/coronavirus-1.1.1/work/coronavirus-1.1.1 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-python/coronavirus-1.1.1/work/coronavirus-1.1.1 ... * python3_8: running distutils-r1_run_phase distutils-r1_python_compile python3.8 setup.py build -j 10 running build running build_py creating /var/tmp/portage/dev-python/coronavirus-1.1.1/work/coronavirus-1.1.1-python3_8/lib/coronavirus copying coronavirus/__init__.py -> /var/tmp/portage/dev-python/coronavirus-1.1.1/work/coronavirus-1.1.1-python3_8/lib/coronavirus running egg_info writing coronavirus.egg-info/PKG-INFO writing dependency_links to coronavirus.egg-info/dependency_links.txt writing requirements to coronavirus.egg-info/requires.txt writing top-level names to coronavirus.egg-info/top_level.txt reading manifest file 'coronavirus.egg-info/SOURCES.txt' writing manifest file 'coronavirus.egg-info/SOURCES.txt' warning: build_py: byte-compiling is disabled, skipping. >>> Source compiled. >>> Test phase [not enabled]: dev-python/coronavirus-1.1.1 Traceback (most recent call last): File "/usr/lib/portage/python3.8/ebuild-ipc.py", line 48, in <module> from portage.util._eventloop.global_event_loop import global_event_loop File "/usr/lib/python3.8/site-packages/portage/util/_eventloop/global_event_loop.py", line 5, in <module> from .EventLoop import EventLoop File "/usr/lib/python3.8/site-packages/portage/util/_eventloop/EventLoop.py", line 4, in <module> import asyncio as _real_asyncio File "/usr/lib/python3.8/asyncio/__init__.py", line 8, in <module> from .base_events import * File "/usr/lib/python3.8/asyncio/base_events.py", line 40, in <module> from . import events File "/usr/lib/python3.8/asyncio/events.py", line 14, in <module> import contextvars File "/usr/lib/python3.8/site-packages/contextvars/__init__.py", line 4, in <module> import immutables ModuleNotFoundError: No module named 'immutables' * The ebuild phase 'test' has exited unexpectedly. This type of behavior * is known to be triggered by things such as failed variable assignments * (bug #190128) or bad substitution errors (bug #200313). Normally, before * exiting, bash should have displayed an error message above. If bash did * not produce an error message above, it's possible that the ebuild has * called `exit` when it should have called `die` instead. This behavior * may also be triggered by a corrupt bash binary or a hardware problem * such as memory or cpu malfunction. If the problem is not reproducible or * it appears to occur randomly, then it is likely to be triggered by a * hardware problem. If you suspect a hardware problem then you should try * some basic hardware diagnostics such as memtest. Please do not report * this as a bug unless it is consistently reproducible and you are sure * that your bash binary and hardware are functioning properly. Traceback (most recent call last): File "/usr/lib/portage/python3.8/ebuild-ipc.py", line 48, in <module> from portage.util._eventloop.global_event_loop import global_event_loop File "/usr/lib/python3.8/site-packages/portage/util/_eventloop/global_event_loop.py", line 5, in <module> from .EventLoop import EventLoop File "/usr/lib/python3.8/site-packages/portage/util/_eventloop/EventLoop.py", line 4, in <module> import asyncio as _real_asyncio File "/usr/lib/python3.8/asyncio/__init__.py", line 8, in <module> from .base_events import * File "/usr/lib/python3.8/asyncio/base_events.py", line 40, in <module> from . import events File "/usr/lib/python3.8/asyncio/events.py", line 14, in <module> import contextvars File "/usr/lib/python3.8/site-packages/contextvars/__init__.py", line 4, in <module> import immutables ModuleNotFoundError: No module named 'immutables' * The ebuild phase 'die_hooks' has exited unexpectedly. This type of * behavior is known to be triggered by things such as failed variable * assignments (bug #190128) or bad substitution errors (bug #200313). * Normally, before exiting, bash should have displayed an error message * above. If bash did not produce an error message above, it's possible * that the ebuild has called `exit` when it should have called `die` * instead. This behavior may also be triggered by a corrupt bash binary or * a hardware problem such as memory or cpu malfunction. If the problem is * not reproducible or it appears to occur randomly, then it is likely to * be triggered by a hardware problem. If you suspect a hardware problem * then you should try some basic hardware diagnostics such as memtest. * Please do not report this as a bug unless it is consistently * reproducible and you are sure that your bash binary and hardware are * functioning properly. ```

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

onkelbeh added the requirement label 2020-09-08 20:17:34 +02:00

onkelbeh commented

2020-09-08 20:29:27 +02:00

nope, just installed dev-python/contextvars by accident

onkelbeh closed this issue

2020-09-08 20:29:27 +02:00

onkelbeh referenced this issue from a commit

2022-09-14 20:53:51 +02:00

Merge pull request #124 from onkelbeh/2022.9.3

Sign in to join this conversation.