On Mon, Apr 8, 2024 at 7:11 AM Petr Pisar <ppisar@xxxxxxxxxx> wrote: > > V Mon, Apr 08, 2024 at 10:49:42AM +0000, Zbigniew Jędrzejewski-Szmek napsal(a): > > On Mon, Apr 08, 2024 at 12:28:34PM +0200, Petr Pisar wrote: > > > - It breaks upgrade path in downstream distributions (e.g. fixes in RHEL minor > > > releases). > > > > Hmm, can you provide describe the workflow that is broken in more > > detail? > > > RHEL do updates into older minor distribution versions. E.g. you might want to > build for RHEL 9.2 and RHEL 9.3. Users staying on 9.2 should update to that > build for 9.2, users staying on 9.3 to the build for 9.3 and users uprgading > from 9.2 to 9.3 should update to the build for 9.3 regardeless they updated to > the 9.2 build before or not. > > It's bascially the same problem as Fedora has when users upgrade from Fredora > 40 to 41. Fedora "fixed" the rpmautospec problem by stating that upgrade path > between Fedoras is not maintained anymore and users need to do "dnf > distro-sync" to ignore the RPM versioning. > > All that stems from tha fact that a number of commits between parallelly > supported braches is not monotonic. > We did this long before rpmautospec existed. We switched to this behavior in Fedora 23 because we have never fully maintained "upgrade paths" across releases. RHEL is *even worse* in this regard because there is no active testing or handling of distribution upgrades within the distribution itself (hence why no equivalent to fedora-obsolete-packages in CentOS/RHEL), which is why distribution upgrades are the bane of every RHEL admin's existence. The Leapp tooling more or less externally does the same thing now, but that's generally not available to CentOS users. The distro-sync behavior is the right way to handle distribution upgrades, the "upgrade path" is the right way *within* a distribution release. -- 真実はいつも一つ！/ Always, there's only one truth! -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
