On Tue, Sep 5, 2023 at 5:22 PM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote:
updates-testing is not enabled by default for the upgrade.
The upgrade process uses whatever repos are enabled *in the current
configuration*. So in the "typical" case, you are upgrading from a
stable Fedora release with default repo configuration, in which
updates-testing is not enabled. Thus updates-testing is not used for
the upgrade.
This didn't occur to me, you're right. We could update our instructions to tell people to use "--enablerepo=updates-testing" when upgrading to a development release, or at least add it if they see broken dependencies and the upgrade fails to start, but only limited people would find those instructions. It's definitely better in general to fix those packages in the main repo.
I'd like to propose an alternative change: we should make clean FTI
cases "automatic freeze exceptions". By "clean" I mean cases where the
package was, practically speaking, useless before the fix. Cases where
it's just one subpackage of a larger package that was FTI should still
be manually checked, especially if the changes are larger than just a
straight targeted fix to that subpackage (e.g. a version bump).
That sounds reasonable. But would we trust packagers to include this important information ("this is not a simple case...") in their FE proposal, or would we still manually check case-by-case?
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-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/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
