Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 449926 Details for
Bug 596912
git-r3.eclass: _git-r3_env_setup(): Bad substitution for packages with PN starting with digit
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
build.log of 389-ds-base
net-nds:389-ds-base-9999:20161011-214922.log (text/x-log), 1.38 KB, created by
Vadim A. Misbakh-Soloviov (mva)
on 2016-10-11 22:00:15 UTC
(
hide
)
Description:
build.log of 389-ds-base
Filename:
MIME Type:
Creator:
Vadim A. Misbakh-Soloviov (mva)
Created:
2016-10-11 22:00:15 UTC
Size:
1.38 KB
patch
obsolete
> * Package: net-nds/389-ds-base-9999 > * Repository: gentoo > * Maintainer: wibrown@redhat.com wes@sol1.com.au,proxy-maint@gentoo.org > * USE: abi_x86_64 amd64 bitwise dna elibc_glibc kernel_linux ldapi pam-passthru presence userland_GNU > * FEATURES: ccache fakeroot preserve-libs sandbox splitdebug userpriv usersandbox >>>> Unpacking source... >/var/tmp/portage/net-nds/389-ds-base-9999/temp/environment: line 656: 389_ds_base_LIVE_REPO: bad substitution > * The ebuild phase 'unpack' 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.
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 596912
: 449926