| 1 |
On 14/03/2017 19:00, allan gottlieb wrote: |
| 2 |
> On Tue, Mar 14 2017, Alan McKinnon wrote: |
| 3 |
> |
| 4 |
>> On 14/03/2017 16:43, allan gottlieb wrote: |
| 5 |
>>> I update roughly twice a week. On one machine (full output below) I was |
| 6 |
>>> told that libinput and evdev are blocking xorg-drivers |
| 7 |
>>> |
| 8 |
>>> [blocks B ] <x11-drivers/xf86-input-libinput-0.20.0 |
| 9 |
>>> ("<x11-drivers/xf86-input-libinput-0.20.0" is blocking |
| 10 |
>>> x11-base/xorg-drivers-1.19) |
| 11 |
>>> [blocks B ] <x11-drivers/xf86-input-evdev-2.10.4 |
| 12 |
>>> ("<x11-drivers/xf86-input-evdev-2.10.4" is blocking |
| 13 |
>>> x11-base/xorg-drivers-1.19) |
| 14 |
>>> |
| 15 |
>>> However the merge does propose to update xorg-drivers |
| 16 |
>>> [ebuild U ] x11-base/xorg-drivers-1.19 [1.18-r1] VIDEO_CARDS="-ark% |
| 17 |
>>> -i915% -i965% (-newport) -sis%" |
| 18 |
>>> |
| 19 |
>>> It also proposes to update libinput and evdev |
| 20 |
>>> [ebuild U ] x11-drivers/xf86-input-libinput-0.24.0 [0.19.0] |
| 21 |
>>> [ebuild U ] x11-drivers/xf86-input-evdev-2.10.5 [2.10.3] |
| 22 |
>>> |
| 23 |
>>> I do see that the versions of libinput and evdev to be used are higher |
| 24 |
>>> than the versions that would block xorg-drivers. I am wondering why in |
| 25 |
>>> this case emerge is telling me about the block (in red with a capital B) |
| 26 |
>>> and more importantly would appreciate confirmation that I should let the |
| 27 |
>>> emerge proceed. |
| 28 |
>> |
| 29 |
>> |
| 30 |
>> Portage found a solution that satisfies all constraints, so you should |
| 31 |
>> let it proceed. |
| 32 |
>> |
| 33 |
>> Did you run emerge with -v to get the above? |
| 34 |
>> That looks like portage is doing it's usual -v thing which is to core |
| 35 |
>> dump to your console in the hope that maybe you can figure it out and |
| 36 |
>> you are willing to play the game called "let's find out what portage |
| 37 |
>> thinks it means today!" |
| 38 |
>> |
| 39 |
>> I don't understand why those blockers are marked hard, as portage found |
| 40 |
>> a solution. The blocker lines are really telling you why portage wants |
| 41 |
>> to upgrade your libinput and evdev drivers - the current ones won't work |
| 42 |
>> with your current drivers. |
| 43 |
>> |
| 44 |
>> Which is all totally pointless, as newer versions of everything are |
| 45 |
>> available and you want a full update. There's very little point in |
| 46 |
>> software going to great lengths to tell you why it won't keep old |
| 47 |
>> versions when you explicitly told it to not keep old versions :-) |
| 48 |
> |
| 49 |
> Thank you for the confirmation! I also doubt the use of B when b would |
| 50 |
> be appropriated. No this was not a --verbose run. I would guess that |
| 51 |
> output would be even less illuminating. |
| 52 |
|
| 53 |
:-) |
| 54 |
|
| 55 |
Portage is a lot like Sheldon from The Big Bang Theory. Everything it |
| 56 |
says is completely correct, and most of us have no clue what it is |
| 57 |
talking abut! |
| 58 |
|
| 59 |
-- |
| 60 |
Alan McKinnon |
| 61 |
alan.mckinnon@×××××.com |
Archives