On 08/28/2017 08:55 PM, Patrick O'Callaghan wrote: > On Mon, 2017-08-28 at 08:46 -0400, Tom Horsley wrote: >> On Mon, 28 Aug 2017 07:11:59 -0500 >> Richard Shaw wrote: >> >>> Was RPM being updated in the same transaction? This bug[1] seems to >>> indicate that the database being updated can cause this problem... >> Yep, looks like rpm shows up in the log as being updated, though >> I have never actually figured out what the heck akmod does and if >> it is part of the same transaction or not. If I poke around on >> the system during the dnf update, I see akmod build the new >> nvidia driver while dnf update is still running, so I'm not >> sure how an rpm that didn't exist at the start of the dnf update >> could be part of the same transaction :-). >> >> Thanks for the info. Looks like it won't be a problem I see >> very often. > This or similar problems do show up quite often. I think it's because > the akmod update builds a new rpm and tries to install it while dnf > itself is still running, so there's race condition on the rpm database. > If you run the rpm install after dnf finishes it will work. > I've not seen that behavior in a long time. I will watch, from time to time, the output in /var/cache/akmods/akmods.log while doing a "dnf update". These lines 2017/08/28 14:30:20 akmods: Checking kmods exist for 4.12.9-300.fc26.x86_64 2017/08/28 14:30:21 akmods: Building and installing nvidia-kmod don't appear until the last "clean up" line appears in the update process. Then I would see... 2017/08/28 14:31:12 akmods: Installing newly built rpms 2017/08/28 14:31:12 akmods: DNF detected And not until the last "verify" is finished will I see.... 2017/08/28 14:32:03 akmods: Successful. And you'll notice the time difference. -- Fedora Users List - The place to go to speculate endlessly
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
