Summary: | dev-python/setuptools-rust-1.9.0 fails to compile: tar: : Cannot open: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | mgorny, quinn_jones, rust, schatderer |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Agostino Sarubbo
![]() Created attachment 893030 [details]
build.log
build log and emerge --info
Error(s) that match a know pattern in addition to what has been reported in the summary: tar: : Cannot open: No such file or directory tar: Error is not recoverable: exiting now (In reply to Agostino Sarubbo from comment #2) > Error(s) that match a know pattern in addition to what has been reported in > the summary: > > > tar: : Cannot open: No such file or directory > tar: Error is not recoverable: exiting now I came across the same problem here, after performing an update today. I noticed that there was an upgrade to Python (version 3.12 will become the default). I also noticed the imminent installation of a beta version of it (3.13.0_beta1_p1). Whether it was a mere coincidence or not, but after masking the beta version (dev-lang/python:3.13) I managed to install the dev-python/setuptools-rust-1.9.0 package. I'm seeing the same issue, and I think that schatderer's fix was just coincidence. Masking dev-lang/python-3.13.0_beta1_p1 did not affect the build on one of my machines. Interesting to note: in my case it's a rebuild. It's currently installed, but I'm trying to reinstall it as part of an emerge -e world. *** This bug has been marked as a duplicate of bug 931955 *** |