| Summary: | sys-libs/efivar-0.23 dies in install_qa_check | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | dashmz |
| Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | floppym |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
emerge --info |
||
Created attachment 431020 [details]
emerge --info
I'm pretty sure this is an error being produced by some portage QA check, not the efivar ebuild. There isn't enough diagnostic info in the log to track it down further than that. Also, I cannot reproduce the issue. (In reply to dashmz from comment #0) > Created attachment 431018 [details] > build.log > > realpath: ' ./man3/efi_variable_t.3.bz2': No such file or directory > realpath: /var/tmp/portage/sys-libs/efivar-0.23/image//usr/share/info/dir: No such file or directory It looks like you have a script that you have used to wrap the rm command. The script calls realpath, which outputs the above error messages. You need to fix your wrapper script. |
Created attachment 431018 [details] build.log When emerging efivar-0.23 (or efivar-0.21) following error pops up: * ERROR: sys-libs/efivar-0.23::gentoo failed: * rm failed! * * Call stack: * misc-functions.sh, line 603: Called install_qa_check * misc-functions.sh, line 256: Called die * The specific snippet of code: * rm -f "${ED}"/usr/share/info/dir{,.gz,.bz2} || die "rm failed!"