Need to stable a newer version for LLVM 18 and figure may as well do 1.79.0 unless a good reason no to? Please let me know, or add CC-ARCHES if it's fine as-is.
+1
virtual/rust-1.79.0 doesn't work for me. It fails in the clean phase - it seems to want to go through clean/prepare/setup/configure as if it were a classic package and not a dependency wrapper. 🙄 Here is my result: " embedded null byte: /bin/bash -c /usr/lib/portage/python3.12/ebuild.sh clean Process Process-6: Traceback (most recent call last): File "/usr/lib/python3.12/multiprocessing/process.py", line 314, in _bootstrap self.run() File "/usr/lib/python3.12/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "/usr/lib/python3.12/site-packages/portage/util/_async/ForkProcess.py", line 326, in _bootstrap sys.exit(target(*(args or []), **(kwargs or {}))) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/portage/process.py", line 1473, in __call__ return self._target(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/portage/process.py", line 849, in _exec_wrapper _exec( File "/usr/lib/python3.12/site-packages/portage/process.py", line 1102, in _exec _exec2( File "/usr/lib/python3.12/site-packages/portage/process.py", line 1202, in _exec2 os.execve(binary, myargs, env) ValueError: embedded null byte * The ebuild phase 'die_hooks' has been aborted since PORTAGE_BUILDDIR * does not exist: '/var/tmp/portage/virtual/rust-1.79.0' >>> Failed to emerge virtual/rust-1.79.0"
(In reply to brankob from comment #2) > virtual/rust-1.79.0 doesn't work for me. > > It fails in the clean phase - it seems to want to go through > clean/prepare/setup/configure as if it were a classic package and not a > dependency wrapper. 🙄 > > Here is my result: > > " embedded null byte: > /bin/bash -c /usr/lib/portage/python3.12/ebuild.sh clean > Process Process-6: > Traceback (most recent call last): > File "/usr/lib/python3.12/multiprocessing/process.py", line 314, in > _bootstrap > self.run() > File "/usr/lib/python3.12/multiprocessing/process.py", line 108, in run > self._target(*self._args, **self._kwargs) > File > "/usr/lib/python3.12/site-packages/portage/util/_async/ForkProcess.py", line > 326, in _bootstrap > sys.exit(target(*(args or []), **(kwargs or {}))) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/site-packages/portage/process.py", line 1473, in > __call__ > return self._target(*args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/site-packages/portage/process.py", line 849, in > _exec_wrapper > _exec( > File "/usr/lib/python3.12/site-packages/portage/process.py", line 1102, in > _exec > _exec2( > File "/usr/lib/python3.12/site-packages/portage/process.py", line 1202, in > _exec2 > os.execve(binary, myargs, env) > ValueError: embedded null byte > * The ebuild phase 'die_hooks' has been aborted since PORTAGE_BUILDDIR > * does not exist: '/var/tmp/portage/virtual/rust-1.79.0' > > >>> Failed to emerge virtual/rust-1.79.0" This looks like a completely messed up portage. 1. Is this reproducible on demand? 2. Does this occur with any other package? 3. Does it reproduce in a clean stage3 chroot? 4. Does it also reproduce with virtual/rust-1.78.0?
(In reply to brankob from comment #2) > virtual/rust-1.79.0 doesn't work for me. > > It fails in the clean phase - it seems to want to go through > clean/prepare/setup/configure as if it were a classic package and not a > dependency wrapper. 🙄 > It *is* a classic package which happens to install no files. > Here is my result: > > " embedded null byte: Eh? Anyway, please file a new bug.
amd64 done
x86 done
arm done
arm64 done
sparc done
ppc done
ppc64 done all arches done