Description of problem: Hello again, can you please provide epel-8 update? I need it for https://bugzilla.redhat.com/show_bug.cgi?id=1815695 Thank you clime
@Adam, if you add the python-sig group to this package I'd be happy to take care of this request.
oh, sorry, I missed this one. I'll do it, but I will add python-sig as comaintainer also.
I do not see a group called python-sig in dist-git? Trying to enter it in the box at https://src.fedoraproject.org/rpms/python-pytest-httpbin/adduser but it's just not there. I see java-sig and perl-sig but no python-sig.
OK, so this isn't going to be easy, there's a whole dep forest here. pytest-httpbin is just a pytest wrapper for httpbin itself, which doesn't have an epel8 build. I own that package, so I could do that one, but...httpbin requires a ton of other stuff: python3-blinker python3-brotli python3-flask python3-markupsafe python3-decorator python3-itsdangerous python3-raven python3-six python3-werkzeug which isn't all in epel8 either. From a quick scratch build attempt: https://koji.fedoraproject.org/koji/taskinfo?taskID=43132980 it seems like brotli and raven are missing. brotli may be a problem. In Fedora, python3-brotli is built out of the 'brotli' source package; it seems like RHEL 8 has its own brotli source package but only ships the 'brotli' binary package from it, it either doesn't build or doesn't ship the python libs. werkzeug could also be an issue: RHEL has python3-werkzeug-0.12.2-4.el8. httpbin 0.7.0 actually requires 0.14.1 or higher, since: https://github.com/postmanlabs/httpbin/commit/75c83178c10c18cd4cf5ebde1a0d0b8b06a79000
Yeah I got here (python-pytest-httpbin) through a dependency of a dependency, so I can relate. I guess pop new bugs for the ones you find, block this one on them, and people (including myself) will get to them as they get to them. There was a recent fedscm-admin fix that allows group commit to request branches, so any of those with the python-sig I can help with as time allows.
out of interest, what's the dependency of the dependency? I packaged this more or less entirely so we could enable the test suite for python-requests during the package build, that was the only thing that used it that I'm aware of.
Sorry, I was confusing this with another epel8 request I was working on. This one is just one level, I need it to build python-vcrpy. I already have bug 1815857 marked as blocked by this one.
(In reply to Adam Williamson from comment #4) > OK, so this isn't going to be easy, there's a whole dep forest here. > pytest-httpbin is just a pytest wrapper for httpbin itself, which doesn't > have an epel8 build. I own that package, so I could do that one, > but...httpbin requires a ton of other stuff: > > python3-blinker python3-brotli python3-flask python3-markupsafe > python3-decorator python3-itsdangerous python3-raven python3-six > python3-werkzeug > > which isn't all in epel8 either. From a quick scratch build attempt: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=43132980 > > it seems like brotli and raven are missing. brotli may be a problem. In > Fedora, python3-brotli is built out of the 'brotli' source package; it seems > like RHEL 8 has its own brotli source package but only ships the 'brotli' > binary package from it, it either doesn't build or doesn't ship the python > libs. > > werkzeug could also be an issue: RHEL has python3-werkzeug-0.12.2-4.el8. > httpbin 0.7.0 actually requires 0.14.1 or higher, since: > > https://github.com/postmanlabs/httpbin/commit/ > 75c83178c10c18cd4cf5ebde1a0d0b8b06a79000 I have hit that problem when trying to build fedmsg: https://copr.fedorainfracloud.org/coprs/clime/python3-fedmsg-epel8/packages/ I think I simply patched python-httpbin to omit that requires. I looked into httpbin code, when the requires was added and I got an impression the >= 0.14.1 condition isn't a functional requirement (or maybe that it would require a little work to make it work with older werkzeug to). It was this commit https://github.com/postmanlabs/httpbin/commit/75c83178c10c18cd4cf5ebde1a0d0b8b06a79000
Yeah, no, I know the change too. It's not functional, but it's a test suite change, and we do want the test suite to run and pass.
I can try to do rebuild in my copr with tests enabled and see if they fail or not with the older werkzeug...
So it builds with tests enabled as well: https://download.copr.fedorainfracloud.org/results/clime/python3-fedmsg-epel8/epel-8-x86_64/01339368-python-httpbin/builder-live.log.gz (i hope it is a correct package).
Hello, could we get this possibly working in epel8? I think just changing the condition by patch to not require wekzeug >= 0.14.1 is enough. Possibly some communication with upstream about this would be good. Adam, can we move this forward? What do you think?
@Adam Williamson should I try to communicate it with upstream to change the condition to 0.12? Thanks
@clime there are several other things missing, not just the werkzeug problem, see my comment earlier. Just resolving the werkzeug issue would be useful but still wouldn't be enough, unless those other ones have been resolved.
(In reply to Adam Williamson from comment #14) > @clime there are several other things missing, not just the werkzeug > problem, see my comment earlier. Just resolving the werkzeug issue would be > useful but still wouldn't be enough, unless those other ones have been > resolved. Sry but what is missing? I.e. what's the blocker? I can take a look at it.
the stuff from comment #4. if all that's been resolved we can try this again.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
moving to EPEL, since that's what this is about. I don't really have time to look at it rn, though.
FEDORA-EPEL-2022-6d7af3cd46 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6d7af3cd46
FEDORA-EPEL-2022-6d7af3cd46 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6d7af3cd46 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-6d7af3cd46 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.