Closed au-phiware closed 9 years ago
Thanks for the depressing cornucopia of low-level minutia. You're awesome!
Unfortunately, I can't reproduce this locally. And I tried. Damn my squinty eyes, I tried. I even enabled your reported set of Portage ${FEATURES}
and manually moved /usr/portage/eclass/git-r3.eclass
away to try and coerce emerge
into failing with a similar code path. No such luck. Grepping /var/tmp/portage/app-misc/powerline-2.1.4/temp/environment
for git-r3
yields nothing but tears on my end, and the ebuild successfully builds.
That said, hsoft reported a similar issue nearly a month ago. We patched that up for him, but then mercilessly refactored our Powerline ebuilds to unify live and release logic into a single "universal" ebuild. To truncate this tiresome story, powerline-2.1.4.ebuild
now symlinks to powerline-9999-r20.ebuild
.
It's conceivable that this refactoring has caused a regression, distasteful as that is to admit. If you wouldn't mind wading into the dimly lit deep end with us:
/usr/portage/eclass/git-r3.eclass
exist for you?/var/lib/layman/raiagent/app-misc/powerline/powerline-2.1.4.ebuild
a relative symlink to powerline-9999-r20.ebuild
for you?/var/tmp/portage/app-misc/powerline-2.1.4/temp/environment
somewhere for me (e.g., as a Gist)?powerline-9999
install for you? Specifically, does emerge powerline
succeed after adding the following lines to /etc/portage/package.accept_keywords
?:>=app-misc/powerline-1.0 **
>=app-vim/powerline-vim-1.0 **
@ZyX-I If you're not too busy, would you mind verifying that powerline-2.1.4
still builds for you? It'd be great to determine if this is a widespread issue. Without being able to reproduce this locally, there's not much I can do on my end. :disappointed:
Thank you for your prompt response and my apologies for my failure to reciprocate the gesture; allow me to remedy that forthwith:
I hope this helps, because I'm still without a clue... Don't hesitate if there's something else you need to ask of me. I shall endeavor to reply, eventually. On the sunny side I've just now completed a fresh install of Gentoo on another laptop and decided to install powerline early in the process: with no problems. Puzzle me that. I haven't installed X yet; fbterm is as complicated as it gets for now, but we shall see.
Thank you for your prompt response and my apologies for my failure to reciprocate the gesture; allow me to remedy that forthwith:
You appear to be literate. Allow me to shake your gentlemanly hand in a jocular manner. :tophat:
I hope this helps
That totally helped. Specifically, your bpasted environment
file contains since-deleted code from an obsolete commit suggesting this to be a repository synchronization issue. A simple sudo layman -s raiagent
on your problem machine should amend this up and permit you to install powerline-2.1.4
without further hardship, tears, woe, or gnashing of scum-fuzzed teeth.
If that is not the case, we will all promptly eat our top hats. All of us.
HAZAR!
I doff my hat to you, good sir! I have at last achieved success!
Hello,
I encounter
git-r3_src_unpack: command not found
when attempting to emerge powerline, which is odd because it shouldn't need the git-r3 eclass, right?Here's more detail than I know what to do with: