Problem: unmerged python-exec [SOLVED]

[max_1975]

Hello,

I have made a big mistake because I have unmerged python-exec and now emerge is not working anymore...
I have tried to find some docs for solving this issue but with no luck.

Anyone had the same issue before? Any suggestion in order to solve it?

Thank you very much,
Max

[steveL]

I have made a big mistake because I have unmerged python-exec and now emerge is not working anymore...
Any suggestion in order to solve it?

Follow the steps in the second half of [post=4671467]this post[/post] replacing python with python-exec; for instance there's a 2.0.1-r1 currently in Patrick's tinderbox. (You shouldn't need to symlink anything.)

And [post=7165614]use FEATURES=buildpkg[/post] in future. ;)

[post=7358388]This post[/post] covers similar situations; you'll see the common denominator is binpkgs; having them built as you go, enables rollback at any point.

[max_1975]

I have made a big mistake because I have unmerged python-exec and now emerge is not working anymore...
Any suggestion in order to solve it?

Follow the steps in the second half of [post=4671467]this post[/post] replacing python with python-exec; for instance there's a 2.0.1-r1 currently in Patrick's tinderbox. (You shouldn't need to symlink anything.)

And [post=7165614]use FEATURES=buildpkg[/post] in future.

[post=7358388]This post[/post] covers similar situations; you'll see the common denominator is binpkgs; having them built as you go, enables rollback at any point.

Thank you for the suggesition.

I have downoaded python-exec from Patrick's tinderbox and now I can run emerge,
but when I try to run

Code: Select all

sudo emerge -K dev-lang/python-exec

I obtain the following error

Code: Select all

>>> Emerging binary (1 of 1) dev-lang/python-exec-2.0.1-r1::gentoo
 * python-exec-2.0.1-r1.tbz2 size ;-) ...                                [ ok ]
[dev-lang/python-exec-2.0.1-r1] bash: /usr/lib/portage/python2.7/ebuild.sh: No such file or directory
/bin/bash: /usr/lib/portage/python2.7/misc-functions.sh: No such file or directory
 * 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 to emerge dev-lang/python-exec-2.0.1-r1, Log file:

>>>  '/var/tmp/portage/dev-lang/python-exec-2.0.1-r1/temp/build.log'

 * Messages for package dev-lang/python-exec-2.0.1-r1:

[dol-sen]

It sounds like you are using portage-2.2.14 which now uses python-exec. Older versions of portage did not.

You should be able to run emerge still, you just have to modify your emerge call to call a specific python version of it.

eg:

Code: Select all

/usr/lib/python-exec/python2.7/emerge

Just modify the python2.7 to a known version you have it installed to.

With that you should be able to emerge python-exec normally.
Another advantage of this new install methood is if one version of portage gets trashed. If you have it installed to other versions, you will have an (hopefully) untouched working version still.

[max_1975]

It sounds like you are using portage-2.2.14 which now uses python-exec. Older versions of portage did not.

You should be able to run emerge still, you just have to modify your emerge call to call a specific python version of it.

eg:

Code: Select all

/usr/lib/python-exec/python2.7/emerge

Just modify the python2.7 to a known version you have it installed to.

With that you should be able to emerge python-exec normally.
Another advantage of this new install methood is if one version of portage gets trashed. If you have it installed to other versions, you will have an (hopefully) untouched working version still.

I solved the issue, but I had to manually install the portage-2.2.8-r2 and then re-emerge python-exec.

Thank you very much!

[BlinkEye]

...

Code: Select all

/usr/lib/python-exec/python2.7/emerge

Just modify the python2.7 to a known version you have it installed to.

Thanks, that helped.

[nickel]

It sounds like you are using portage-2.2.14 which now uses python-exec. Older versions of portage did not.

You should be able to run emerge still, you just have to modify your emerge call to call a specific python version of it.

eg:

Code: Select all

/usr/lib/python-exec/python2.7/emerge

Just modify the python2.7 to a known version you have it installed to.

With that you should be able to emerge python-exec normally.
Another advantage of this new install methood is if one version of portage gets trashed. If you have it installed to other versions, you will have an (hopefully) untouched working version still.

i know, it's been 4 years. But i raan in the same problem.
how do you do that?

[szatox]

Never ran into it myself, but I'd start with eselect:
`eselect python list` to check what you have available
`eselect python set <N>` to use one