Solved pkg can't find packages providing libGL.so.1

[huggablemonad]

Hi,

pkg upgrade keeps wanting to install nvidia-driver-440.100_1. I think it's because of this:

DBG(1)[17376]> cannot find local packages that provide library libGL.so.1 required for cairo
DBG(1)[17376]> cannot find remote packages that provide library libGL.so.1 required for cairo
DBG(1)[17376]> cannot find local packages that provide library libEGL.so.1 required for cairo
DBG(1)[17376]> cannot find remote packages that provide library libEGL.so.1 required for cairo

I have cairo-1.16.0_1,3, mesa-libs-19.0.8_3, and nvidia-driver-390-390.138_1 installed. The nvidia-driver-390-390.138_1 package is locked.

This seems to have happened after the latest October quarterly update. I'm on 12.1-RELEASE-p10 and use only binary packages. Running pkg update -f doesn't make a difference; it still wants to install nvidia-driver-440.100_1.

Nothing seems to be amiss when I look at the output of pkg shlib:

# pkg shlib -P libGL.so.1
libGL.so.1 is provided by the following packages:
nvidia-driver-390-390.138_1
mesa-libs-19.0.8_3

# pkg shlib -R libGL.so.1
libGL.so.1 is linked to by the following packages:
cairo-1.16.0_1,3
[other lines elided]

What should I check next?

 

[SirDice]

The nvidia-driver-390-390.138_1 package is locked.

Unlock it.

 

[huggablemonad]

I have an old video card (GT 620) which isn't supported by the 440.xx series driver, so I have to lock the nvidia-driver-390-390.138_1 package to stop it from being upgraded.

 

[SirDice]

so I have to lock the nvidia-driver-390-390.138_1 package to stop it from being upgraded.

It won't get upgraded to x11/nvidia-driver-440 because it's, from the system's point of view, a different port/package. The -440 is part of the port/package 's name, hence it's a different port/package.

 

[huggablemonad]

It won't get upgraded to x11/nvidia-driver-440 because it's, from the system's point of view, a different port/package. The -440 is part of the port/package 's name, hence it's a different port/package.

Thanks for the explanation. It fixes a wrong assumption that I held about how pkg works. Unlocking the x11/nvidia-driver-390 package as you suggested solved the problem. Thanks!