FS#70462 - nvidia packages not updated at the same time

Attached to Project: Arch Linux
Opened by Matthew Krafczyk (krafczyk) - Thursday, 15 April 2021, 17:14 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 15 April 2021, 18:14 GMT
Task Type General Gripe
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I updated my system software this morning at about 9:00 central time. (sudo pacman -Syu) and discovered upon reboot that steam wouldn't start. After an hour of my time debugging, I found an X org BadValue error, I discovered that my lib32-nvidia* packages had all been updated to 465.24.02-1, and yet the nvidia* kernel driver related packages were still on version 460.

This happened because at the time of my system update, only the lib32-nvidia* packages had been updated in the official repositories to 465, while it wasn't until almost 2hrs later that official nvidia driver packages were updated. this is corroborated by the current 'last-updated' times reported here: https://archlinux.org/packages/multilib/x86_64/lib32-nvidia-utils/ and here: https://archlinux.org/packages/extra/x86_64/nvidia/

lib32-nvidia-utils was updated at 2021-04-15 13:36 UTC (8:36 local time)
nvidia was updated at 2021-04-15 15:11 UTC (10:11 local time)

Of course, I probably could've seen this if I'd inspected the package versions carefully on the pacman update, but I don't always have time for such a thorough review (such as this morning) and I generally trusted that package groups would be updated together.

It's possible this was just a fluke and it always takes this long to update all of these nvidia packages, but this is meant to gently ask maintainers try to reduce the time groups of packages like this have mis-matched versions. It was a nasty surprise debugging session this morning.

Thanks for your great work on this package otherwise! This is really the first time I've had such an issue.

Steps to reproduce:
This was hopefully a fluke situation. It's related to the timing of package updates and when users refresh their pacman db for a system update.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Thursday, 15 April 2021, 18:14 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#70459 

Loading...