1 |
On Mon, 8 Mar 2021 at 00:32, Steven Lembark <lembark@×××××××.com> wrote: |
2 |
> * emerge: there are no ebuilds to satisfy ">=dev-python/chardet-3.0.2[python_targets_python3_6(-),python_targets_python3_7(-),python_targets_python3_8(-),-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]". |
3 |
> <snip> |
4 |
|
5 |
If you can unsnip here and show more of the output, we could see what |
6 |
package is causing this error. This error is telling you that |
7 |
something in the snipped output is requiring dev-python/chardet to be |
8 |
built with python targets matching that other package, and that |
9 |
package seems to be using other targets than the default 3.8. |
10 |
|
11 |
Since you've already mentioned that depclean doesn't remove anything, |
12 |
do you have any package-specific python targets set that you've |
13 |
forgotten about? |
14 |
# grep python_targets /etc/portage/package.use/* |
15 |
|
16 |
It seems to me very similar to other threads on this list where people |
17 |
have older packages hanging back that creates problems because portage |
18 |
can't remove them. |
19 |
|
20 |
Regards, |
21 |
Arve |