| 1 |
On Sun, 14 Jun 2020 22:07:20 +0200, n952162 wrote: |
| 2 |
|
| 3 |
> I see that there are new lines in the dependencies table that I've never |
| 4 |
> encountered before: |
| 5 |
> |
| 6 |
> [blocks B ] <x11-proto/randrproto-1.5.0-r1 |
| 7 |
> ("<x11-proto/randrproto-1.5.0-r1" is blocking |
| 8 |
> x11-base/xorg-proto-2019.2) |
| 9 |
> |
| 10 |
> I get these (using the emerge from the git repository) for all of |
| 11 |
> @world, @system, and portage. |
| 12 |
> |
| 13 |
> Is there a way to handle that? |
| 14 |
|
| 15 |
As you're now SSHing into the machine and don't need X to do the upgrade, |
| 16 |
I'd just unmerge randrproto. Once you have portage updage, the next world |
| 17 |
update will pull in the correct version if it's still needed. |
| 18 |
|
| 19 |
|
| 20 |
-- |
| 21 |
Neil Bothwick |
| 22 |
|
| 23 |
Deja Foobar: A feeling of having made the same mistake before. |
Archives