Description of problem: Rebuild of the Fedora 30 src.rpm works well: https://kojipkgs.fedoraproject.org//packages/python-tox/3.5.3/4.fc30/src/python-tox-3.5.3-4.fc30.src.rpm Version-Release number of selected component (if applicable): python3-tox-3.5.3-4 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Why Fedora 30 and not rawhide? Would you co-maintain tox in EPEL for the next decade?
Also, the (rawhide) package builds, but has missing runtime deps: Error: Problem: conflicting requests - nothing provides python3.6dist(importlib-metadata) >= 0.12 needed by python3-tox-3.14.3-1.el8.noarch - nothing provides python3.6dist(importlib-metadata) < 2 needed by python3-tox-3.14.3-1.el8.noarch - nothing provides python3.6dist(pluggy) >= 0.12.0 needed by python3-tox-3.14.3-1.el8.noarch - nothing provides python3.6dist(virtualenv) >= 16.0.0 needed by python3-tox-3.14.3-1.el8.noarch python3.6dist(virtualenv) is part of RHEL 8. So this will be tricky. Packaging an already ancient version of tox to mitigate this is IMHO not a good idea.
And the Fedora 30 build even fails with: Traceback (most recent call last): File "setup.py", line 69, in <module> for x in "2 2.7 3 3.4 3.5 3.6 3.7".split() File "/usr/lib/python3.6/site-packages/setuptools/__init__.py", line 128, in setup _install_setup_requires(attrs) File "/usr/lib/python3.6/site-packages/setuptools/__init__.py", line 123, in _install_setup_requires dist.fetch_build_eggs(dist.setup_requires) File "/usr/lib/python3.6/site-packages/setuptools/dist.py", line 514, in fetch_build_eggs replace_conflicting=True, File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 770, in resolve replace_conflicting=replace_conflicting File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 1053, in best_match return self.obtain(req, installer) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 1065, in obtain return installer(requirement) File "/usr/lib/python3.6/site-packages/setuptools/dist.py", line 581, in fetch_build_egg return cmd.easy_install(req) File "/usr/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 666, in easy_install raise DistutilsError(msg) distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('setuptools-scm<4,>2')
Hi Miro, Those packages are in CentOS PowerTools or RHEL CBR repo.
And yes. I can co-maintain the tox for next decade as long as I am still in Red Hat. I use it daily and also in our CI system. My Fedora account is: cathay4t
Some dependency are in AppStream or CBR which rebase policy is not like Fedora rawhide. The version python3-tox-3.5.3 contains all the features I need right now and works well with existing dependent packages.
> Those packages are in CentOS PowerTools or RHEL CBR repo. How do I enable those in EPEL mock to test this? Also, I don't see python3-importlib-metadata anywhere in RHEL. > The version python3-tox-3.5.3 contains all the features I need right now... This will eventually change. I highly recommend packaging the latest while we still have the chance. > I can co-maintain the tox for next decade... https://pagure.io/releng/fedora-scm-requests/pull-request/22107
(In reply to Miro Hrončok from comment #7) > > Those packages are in CentOS PowerTools or RHEL CBR repo. > > How do I enable those in EPEL mock to test this? According to https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F EPEL-8 already have PowerTools/CBR repo enabled. > Also, I don't see > python3-importlib-metadata anywhere in RHEL. No idea why it is needed for python3-tox-3.5.3. > > > > The version python3-tox-3.5.3 contains all the features I need right now... > > This will eventually change. I highly recommend packaging the latest while > we still have the chance. It's just no possible. Latest tox require many packages which is already shipped in RHEL with older versions. And RHEL never rebase/upgrade a package without good reason. The EPEL policy stop us from changing package shipped by RHEL repos, so we cannot ship the new version. RHEL has never been a place for latest packages. That's Archlinux or Fedora Rawhide. > > > > I can co-maintain the tox for next decade... > > https://pagure.io/releng/fedora-scm-requests/pull-request/22107 Thanks.
> RHEL has never been a place for latest packages. Correct. You seem to have answers to all the questions. That's good. Except: The f30 package does not currently build in epel8, see comment #3. Either way, feel free to request the epel8 branch and submit a PR to it, we can work out the details there.
Requesting epel8 branches at: https://pagure.io/releng/fedora-scm-requests/issue/22224 https://pagure.io/releng/fedora-scm-requests/issue/22223
To create the epel8 branch: * I disabled the PR only option in src.fedoraproject.org * Push a empty commit to epel8 branch. * Re-enabled PR only option in src.fedoraproject.org. Pull request is created at https://src.fedoraproject.org/rpms/python-tox/pull-request/18 for review.
FEDORA-EPEL-2020-7dd88da060 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-7dd88da060
python-tox-3.4.0-1.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-7dd88da060
FEDORA-EPEL-2020-7dd88da060 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.