| 1 |
On Mon, 20 Sep 2021 16:31:59 +0200 |
| 2 |
Gerrit Kuehn <gerrit.kuehn@×××××××.de> wrote: |
| 3 |
|
| 4 |
> This looks like portage is blocked by itself... so how to solve this |
| 5 |
> one? |
| 6 |
|
| 7 |
Well, I simply installed the new virtual packages manually and used |
| 8 |
"--nodeps" on portage itself afterwards... and here we are. Looks like |
| 9 |
new portage will update the rest of my system without any issue now (at |
| 10 |
least it says so when checking with -p), so here we go. Still no idea |
| 11 |
why this was blocking so hard, though. |
| 12 |
|
| 13 |
|
| 14 |
cu |
| 15 |
Gerrit |
Archives