| Summary: | media-sound/beets-1.4.9-r4 fails to compile with dev-lang/python-exec[-native-symlinks] | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
| Component: | Current packages | Assignee: | Guillaume Seren <guillaumeseren> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | asturm, ionen, kangie, proxy-maint |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 762406 | ||
| Attachments: | build.log | ||
|
Description
Agostino Sarubbo
2021-01-24 11:52:13 UTC
Created attachment 684375 [details]
build.log
build log and emerge --info
Hello, I have tested on a stage3 chroot and I can not reproduce this issue. Maybe I am missing something, but the error look like an installation problem, can you provide more details ? Is the error reproducible ? This is caused by USE=native-symlinks and ago does not feel like it is necessary to mention that in $summary or $description. Yeah, I can't reproduce this on a clean stage3 either with similar emerge history. (In reply to Andreas Sturmlechner from comment #3) > This is caused by USE=native-symlinks and ago does not feel like it is > necessary to mention that in $summary or $description. This is not about what I feel. It is just hard to implement for how it works right now. This isn't [-native-symlinks], the flag is enabled in the emerge --info and there's no errors about commands not found. It's failing to find beets import while inside the image, can get the same error by, outside the ebuild, running image/usr/bin/beet while beets doesn't exist on the system. That aside, I haven't been able to reproduce from the ebuild where the python environment should be set right. Hey,
I have tested this issue again on a clean stage3 chroot,
and I can not reproduce it (even with dev-lang/python-exec[-native-symlinks]).
In the build log, it look like the build crashed when calling the following line:
${PYTHON} "${ED}/usr/bin/beet" completion > "${T}/beet.bash"
As it us ED it should be portable, maybe there is something else changed in python module loading in the tinderbox.
Also Ago, is that possible to try to run the test suite in the tinderbox to see if that works ? Closing as obsolete - this hasn't been repro'd on any in-tree versions of the package, or really anywhere looking at the comments. |