Re @Prabhjot Singh Problem with alsa-plugins-freeworld-lavcrate when upgrading to Fedora 28
"Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers."
The claim here is that removing a third party package counts as "when a typo was fixed". Why is this?
The question can be, and was, answered with a simple reference to the upgrade documentation. It's already pretty helpful. Such a Q&A would be a valid target for potentially quickly signposting future askers. I was kind of surprised that I didn't notice such a target in the auto-search sidebar.
Notice that the doc doesn't treat this as a simple mistake. It's a tradeoff - upgrade to the latest Fedora at this time; lose your third-party packages that haven't updated at the moment.
This is not just a question of reading comprehension either. The reason that third-party repos would show this error is not automatically obvious.
E.g. it's relevant to see that the official Fedora advice is not that you need always to disable all third-party repos first... and then have it be pot-luck to find out whether you can re-install after the upgrade.
The documentation also claims that you will want to take care to pass a specific option, so that you're not downloading the entire upgrade and throwing it away if you cancel and look again at this command several times. I have not been affected by this, but if I was, I would not consider it trivial.
(To anyone who claims they would always be aware of all documentation every time they do an upgrade, I would respectfully quote this from LWN.net regarding Debian: "They are usually pretty simple... but the actual upgrade process is really much more complex. If you run into problems with the above commands, you will quickly learn that you should have followed the release notes, a whopping 20,000-word, ten-section document that outlines all the gory details of the release."
Fedora is better, sure. But the last time I checked, even they didn't manage to link from the GUI upgrade tool through to the "Common F2X bugs" page for the release).