Bug 244948
| Summary: | www/py-webargs: Downgrade to 5.5.3 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Goran Mekić <meka> | ||||
| Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||
| Status: | Closed Overcome By Events | ||||||
| Severity: | Affects Only Me | CC: | meka, python, tcberner | ||||
| Priority: | --- | Keywords: | needs-qa | ||||
| Version: | Latest | Flags: | meka:
maintainer-feedback+
|
||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| See Also: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244950 | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 244950, 244957 | ||||||
| Attachments: |
|
||||||
Its preferable to create a separate port (webargs5), than downgrade versions. Is there any way to make/get flask-smorest to support 6.x ? (In reply to Kubilay Kocak from comment #1) The support for webargs 6.0 is being worked on, but it will take some time. I asked on #freebsd-ports for advise, and as only flask-smorest depends on webargs, I've been told I should downgrade unless support for 6.0 would be added soon(ish). Once flask-smorest supports webargs 6.0, there would be nothing requiring webargs 5.x, so I thought there's no point in creating webargs5. Sorry, got the order a bit wrong :) Committed. A commit references this bug: Author: tcberner Date: Sat Apr 4 18:47:34 UTC 2020 New revision: 530706 URL: https://svnweb.freebsd.org/changeset/ports/530706 Log: www/py-webargs: Downgrade to 5.5.3 PR: 244948 Submitted by: Goran Meki? <meka@tilda.center> (maintainer) Changes: head/www/py-webargs/Makefile head/www/py-webargs/distinfo This has been reverted. |
Created attachment 212577 [details] py-webargs.diff QA: * portlint: OK (looks fine.) * testport: OK (poudriere: 12.1, amd64 tested) * maketest: OK (292 passed, 6 skipped, 3 warnings) As www/py-flask-smorest is the only port that depends on webargs and webargs version 6.0 contains breaking changes, reverting webargs to 5.5.3 seams logical.