You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Traceback (most recent call last):
File "/usr/local/bin/superflore-gen-ebuilds", line 33, in <module>
sys.exit(load_entry_point('superflore==0.3.3+2.gd475c34.dirty', 'console_scripts', 'superflore-gen-ebuilds')())
File "/usr/local/lib/python3.10/dist-packages/superflore-0.3.3+2.gd475c34.dirty-py3.10.egg/superflore/generators/ebuild/run.py", line 202, in main
File "/usr/local/lib/python3.10/dist-packages/superflore-0.3.3+2.gd475c34.dirty-py3.10.egg/superflore/generators/ebuild/overlay_instance.py", line 103, in regenerate_manifests
File "/usr/local/lib/python3.10/dist-packages/superflore-0.3.3+2.gd475c34.dirty-py3.10.egg/superflore/docker.py", line 110, in run
File "/usr/local/lib/python3.10/dist-packages/docker-6.0.0-py3.10.egg/docker/models/containers.py", line 875, in run
raise ContainerError(
docker.errors.ContainerError: Command 'bash -c ' cd /tmp/ros-overlay/ros-humble/zstd_vendor &>> /tmp/tmp23b1vxa4/log.txt && repoman manifest & ...'
This error occurs on the manifest creation step however the error not clear.
The text was updated successfully, but these errors were encountered:
I haven't ever looked deeply into how superflore's gentoo support works but the fact that it relies on Docker images which have not been updated for a number of years suggests that it may need to be reworked entirely.
As I've said I'm not intimately familiar with the details but if there's a way to generate the required data without using Docker (possibly by using ports of the Gentoo tools to other systems like Debian, or independently implementing a subset of their behavior) that would make this a lot more maintainable.
I am fairly new to gentoo so I don't have a good grasp on every concept. I don't really know how manifest are generated.
Is there a link to the dockerfile used somewhere ?
Running the following command generates ebuild for humble while ignoring packages running the error mentioned in #289
This error occurs on the manifest creation step however the error not clear.
The text was updated successfully, but these errors were encountered: