Fernando Rodriguez schrieb:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 08/13/2016 09:40 AM, hw wrote:
Fernando Rodriguez schrieb:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 08/12/2016 08:44 AM, Jeroen Mathon wrote:
Is it perhaps an idea to mask the gentoolkit package when updating portage?
Since that version of gentoolkit doesn't depend on a specific version of portage
but does depend on portage with the same python_targets use flags, I think the
problem
is that you're trying to emerge portage and gentoolkit with different
python_target_XXX
flags, So just make sure they're the same.
I have removed gentoolkit, and it still fails:
emerge --ask --update --newuse portage
[...]
WARNING: One or more updates/rebuilds have been skipped due to a dependency
conflict:
sys-apps/portage:0
(sys-apps/portage-2.2.28:0/0::gentoo, ebuild scheduled for merge) conflicts
with
sys-apps/portage[python_targets_python2_7(-),python_targets_python3_3(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-)]
required by (app-admin/webapp-config-1.52-r1:0/0::gentoo, installed)
Now it's app-admin/webapp-config it has the same dep on portage
(sys-apps/portage[${PYTHON_USEDEP}]) only when the portage use flag is enabled.
You're trying to build portage with a new python target when everything else is
built for a different
python version. Either change portage's to the same as everythhing else or
remerge all packages that depend
on portage first.
Since someone said I should use the same python target for everything,
I set one globally. Why wouldn´t that target be used?
Even if that would work, I can´t update portage before it´s updated to
a version which can work with EAPI 6 packages, and it can´t be updated
before it can work with EAPI 6 packages.
So the only way to update would be step by step. I´m probably willing
to try that, but I expect other problems when doing that, like with
updating perl. And I can´t do that because it is required that perl
works when the updating is done.
