On 7/9/23 15:18, Sam Varshavchik wrote:
ToddAndMargo via users writes:
On 7/9/23 04:21, Sam Varshavchik wrote:
ToddAndMargo via users writes:
Okay, after erasing all the 9005's, redoing the following
https://www.libvirt.org/daemons.html#switching-to-modular-daemons
and rebooting, all my VM stuff is running perfectly again.
Thank you all for the help!
Upstream documentation, like that, isn't really meant for use with
packaged distributions, like Fedora. Unless something over there
explicitly states: "do this on Fedora X", then you're on your own.
If memory serves me, I had switched to upstream
as a bug had been fixed in it that I need.
But has long since been fixed. I am happy
to be back on the Fedora repos.
I have not read that external documentation, but in this situation the
best course of action is:
1) grab the most recent Fedora .src.rpm
2) grab the newer upstream source
3) figure out whether any Fedora patches are still needed or need to be
adjusted for the new upstream source
4) build new Fedora binary rpms, and use DNF to upgrade them
The situation becomes more complicated if the package provides
libraries, and now one needs to figure out if there are any binary ABI
changes that any downstream packages depend on. Usually, but not always,
this gets picked up by an soname mismatch.
In any case, there is no cookie-cutter recipe for this situation, and
one needs a fair amount of understanding of the target package and
development background, to be able to avoid pitfalls, like that.
It is working fine now. :-)
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
