-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Thu, Jul 26, 2018 at 09:34:20AM -0400, Steve Coleman wrote:
> After a normal dnf update this error was displayed, because the old package
> is not erasing correctly. building the u2mfn from source did not help.
>
> $ sudo dnf update qubes-kernel-vm-support
> Last metadata expiration check: 0:39:14 ago on Thu Jul 26 08:27:57 2018.
> Dependencies resolved.
>
> Problem: cannot install both qubes-kernel-vm-support-4.0.20-1.fc28.x86_64
> and qubes-kernel-vm-support-4.0.20-1.fc28.x86_64
> - cannot install the best update candidate for package
> qubes-kernel-vm-support-4.0.20-1.fc28.x86_64
> - cannot install the best update candidate for package
> qubes-kernel-vm-support-4.0.19-1.fc28.x86_64
> ======================================================================================================================================
> Package Arch Version
> Repository Size
> ======================================================================================================================================
> Reinstalling:
> qubes-kernel-vm-support x86_64 4.0.20-1.fc28
> qubes-vm-r4.0-current 14 k
> replacing qubes-kernel-vm-support.x86_64 4.0.19-1.fc28
Looks like some previous update failed to remove 4.0.19-1.fc28 version
and now you have both.
(...)
> Running scriptlet: qubes-kernel-vm-support-4.0.19-1.fc28.x86_64
> 2/3
> Error! There are no instances of module: u2mfn
> 4.0.19 located in the DKMS tree.
> error: %preun(qubes-kernel-vm-support-4.0.19-1.fc28.x86_64) scriptlet
> failed, exit status 3
> Error in PREUN scriptlet in rpm package qubes-kernel-vm-support
> Error in PREUN scriptlet in rpm package qubes-kernel-vm-support
Probably qubes-kernel-vm-support-4.0.19-1.fc28.x86_64 was half-removed
already. Cleanup it with bypassing scripts:
sudo rpm -e --noscripts qubes-kernel-vm-support-4.0.19-1.fc28.x86_64
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAltaWX8ACgkQ24/THMrX
1yyw0AgAgVK5ZcFZIY8uTEZXshGypGIyBtZnzS6NoG7H3q4ZE/iOv1Ve1IFsIwt9
/Mn2tl1Wubq3G25KBGZeR17+qih6EtK+8lRKSfh5ZaDUINtWYgZJuY46wLMR54wM
cWb1Bsk1LB1mf98pVoHM3GrzohFs3KATtl4umOJEAIcSYGWFVt3WEQ7LzpYeCOTi
GLHT0gPtR9zoZ2y7/g/4EiUTTHYUoVgiakrdf7MRJ6KsH/BUJjdXYcaD9/PVGZl4
4n+/TBwQaBeyHCGvXoopb2vEshIyF2XmInOp/41DwxitXwFww/4dsXjX62Ttaa7t
YsSJ1MLgnuf/TsVVPdeTyq4J/Xn4Fw==
=R8Yb
-----END PGP SIGNATURE-----