On 6/15/21 7:54 PM, Ed Greshko wrote:
On 16/06/2021 10:49, ToddAndMargo via users wrote:
On 6/15/21 7:00 PM, Ed Greshko wrote:
On 16/06/2021 09:57, ToddAndMargo via users wrote:
2) in their "ultimate wisdom", the rpm maintainers disabled
the service after upgrading it. See the following bug I posted
on 2021-06-14:
Well, that didn't happen all my cases of upgrades. So, I doubt that
was done by
the maintainers.
It happens on all of mine. And this is not the first
time I have complained about it. I doubt I will
be able to prove it to them. I look at my own notes
first anyway.
Another person responding to the BZ also was unable to reproduce.
So, the issue doesn't seem to be very common.
So, best to reproduce in a VM and collect all the information possible.
Those kind of error follow me around like a
storm cloud. I am use to it.
I once fixed a problem where five different things
affect each other.
A --> affected B --> affected C --> affected D--> affected E --> affected A
I had to fix all five. Drove me nuts for a few hours.
I was not the first to have tried either.
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure
