Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 700278 Details for
Bug 780810
sys-libs/musl-1.2.2-r2 Failed to emerge in a docker container
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
build.log on emerge musl
build-first.log (text/plain), 4.67 KB, created by
Michel Ganguin
on 2021-04-16 23:57:42 UTC
(
hide
)
Description:
build.log on emerge musl
Filename:
MIME Type:
Creator:
Michel Ganguin
Created:
2021-04-16 23:57:42 UTC
Size:
4.67 KB
patch
obsolete
>File not found: /usr/lib/portage/python3.8/ebuild-ipc > * The ebuild phase 'prerm' has exited unexpectedly. This type of behavior > * is known to be triggered by things such as failed variable assignments > * (bug #190128) or bad substitution errors (bug #200313). Normally, before > * exiting, bash should have displayed an error message above. If bash did > * not produce an error message above, it's possible that the ebuild has > * called `exit` when it should have called `die` instead. This behavior > * may also be triggered by a corrupt bash binary or a hardware problem > * such as memory or cpu malfunction. If the problem is not reproducible or > * it appears to occur randomly, then it is likely to be triggered by a > * hardware problem. If you suspect a hardware problem then you should try > * some basic hardware diagnostics such as memtest. Please do not report > * this as a bug unless it is consistently reproducible and you are sure > * that your bash binary and hardware are functioning properly. >File not found: /usr/lib/portage/python3.8/ebuild-ipc > * The ebuild phase 'die_hooks' has exited unexpectedly. This type of > * behavior is known to be triggered by things such as failed variable > * assignments (bug #190128) or bad substitution errors (bug #200313). > * Normally, before exiting, bash should have displayed an error message > * above. If bash did not produce an error message above, it's possible > * that the ebuild has called `exit` when it should have called `die` > * instead. This behavior may also be triggered by a corrupt bash binary or > * a hardware problem such as memory or cpu malfunction. If the problem is > * not reproducible or it appears to occur randomly, then it is likely to > * be triggered by a hardware problem. If you suspect a hardware problem > * then you should try some basic hardware diagnostics such as memtest. > * Please do not report this as a bug unless it is consistently > * reproducible and you are sure that your bash binary and hardware are > * functioning properly. >!!! FAILED prerm: 1 >File not found: /usr/lib/portage/python3.8/ebuild-ipc > * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior > * is known to be triggered by things such as failed variable assignments > * (bug #190128) or bad substitution errors (bug #200313). Normally, before > * exiting, bash should have displayed an error message above. If bash did > * not produce an error message above, it's possible that the ebuild has > * called `exit` when it should have called `die` instead. This behavior > * may also be triggered by a corrupt bash binary or a hardware problem > * such as memory or cpu malfunction. If the problem is not reproducible or > * it appears to occur randomly, then it is likely to be triggered by a > * hardware problem. If you suspect a hardware problem then you should try > * some basic hardware diagnostics such as memtest. Please do not report > * this as a bug unless it is consistently reproducible and you are sure > * that your bash binary and hardware are functioning properly. >File not found: /usr/lib/portage/python3.8/ebuild-ipc > * The ebuild phase 'die_hooks' has exited unexpectedly. This type of > * behavior is known to be triggered by things such as failed variable > * assignments (bug #190128) or bad substitution errors (bug #200313). > * Normally, before exiting, bash should have displayed an error message > * above. If bash did not produce an error message above, it's possible > * that the ebuild has called `exit` when it should have called `die` > * instead. This behavior may also be triggered by a corrupt bash binary or > * a hardware problem such as memory or cpu malfunction. If the problem is > * not reproducible or it appears to occur randomly, then it is likely to > * be triggered by a hardware problem. If you suspect a hardware problem > * then you should try some basic hardware diagnostics such as memtest. > * Please do not report this as a bug unless it is consistently > * reproducible and you are sure that your bash binary and hardware are > * functioning properly. >!!! FAILED postrm: 1 > * The 'postrm' phase of the 'sys-libs/musl-1.2.1-r2' package has failed > * with exit value 1. > * > * The problem occurred while executing the ebuild file named > * 'musl-1.2.1-r2.ebuild' located in the '/var/db/pkg/sys- > * libs/musl-1.2.1-r2' directory. If necessary, manually remove the > * environment.bz2 file and/or the ebuild file located in that directory. > * > * Removal of the environment.bz2 file is preferred since it may allow the > * removal phases to execute successfully. The ebuild will be sourced and > * the eclasses from the current ebuild repository will be used when > * necessary. Removal of the ebuild file will cause the pkg_prerm() and > * pkg_postrm() removal phases to be skipped entirely.
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 780810
:
700275
| 700278 |
700281