On Sat, Feb 19, 2022 at 3:21 PM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote: > > Hello, > > I have a Fedora package that I've recently also branched for EPEL 9. > > The (so called) binary package used to be called "python3-tox", but has been > renamed to "tox" in Fedora 34. All supported Fedora versions and EPEL 9 have > the package named as "tox". The package has: > > %py_provides python3-tox > # Remove this once Fedora 36 goes EOL: > Obsoletes: python3-tox < 3.24.4-2 > > However, the EPEL 8 package is still called python3-tox. > > Once I remove the Obsoletes line from Fedora, should I worry about merging that > commit to the epel9 branch or not? Logic dictates that the Obsolete should > remain in EPEL 9 forever, but I wonder if there is a policy/rule of thumb. E.g. > in Fedora, we only support upgrades to Fedora N+2. Do we support upgrades of > EL+EPEL systems as well and how "far"? > Ideally, we support EL X-1 -> EL X. So EPEL9 *should* upgrade EPEL8 packages, but I don't know if we enforce this. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
