On Sat, Nov 8, 2025 at 6:00 AM Fabio Valentini <[email protected]> wrote: > > On Sat, Nov 8, 2025 at 7:03 AM Carl George <[email protected]> wrote: > > > > It's true that there isn't a config for this included in > > mock-core-configs. My recommendation would be to instead run `fedpkg > > scratch-build` from the epel10.1 branch. > > Yes, I know that I can run scratch builds, but that doesn't help me to > check whether the built packages are *installable*.
There's no perfect answer for this due to the nature of RHEL's development and the non-public RHEL minor version branches. More often than not I hope this has no impact, assuming a package was installable on CentOS 10 at the time of mass branching and that is hasn't changed enough for installability to be adversely affected. Hopefully rebase cases like this are the rare exception. In RHEL, after the minor version branches it gets progressively harder (i.e. more red tape) to make changes to that branch, but we don't have the equivalent on the EPEL side. I would encourage EPEL maintainers to follow that approach whenever possible. > > > While RHEL 10.1 hasn't been released yet, EPEL 10.1 has. Please don't > > treat EPEL minor versions newer than the current RHEL minor version as > > pre-release, because they are already being consumed by CentOS users. > > Are they though? (Or *can* they?) I thought CentOS Stream already > tracks EPEL 10.2 now. CentOS tracked EPEL 10.1 for about six months. It tracks EPEL 10.2 now, but ideally we should still treat EPEL 10.1 with at least as much discretion as we do EPEL 10.2. It doesn't make sense to me to temporarily allow more disruptive updates as a rule during the short gap period where neither CentOS or RHEL is directly consuming an EPEL minor version. My concern is if we start referring to the branched minor version as pre-release, the next logical step is referring to the leading minor version as pre-release. That would be a mistake since people are already relying on it and expecting at least major version stability. > > Fabio > -- > _______________________________________________ > epel-devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected] > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Carl George -- _______________________________________________ epel-devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
