Bug 244948 - www/py-webargs: Downgrade to 5.5.3
Summary: www/py-webargs: Downgrade to 5.5.3
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs mailing list
URL:
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2020-03-21 12:31 UTC by Goran Mekić
Modified: 2020-03-25 06:58 UTC (History)
2 users (show)

See Also:
meka: maintainer-feedback+


Attachments
py-webargs.diff (1.07 KB, patch)
2020-03-21 12:31 UTC, Goran Mekić
meka: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Goran Mekić 2020-03-21 12:31:08 UTC
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.
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2020-03-22 07:12:21 UTC
Its preferable to create a separate port (webargs5), than downgrade versions. Is there any way to make/get flask-smorest to support 6.x ?
Comment 2 Goran Mekić 2020-03-22 08:17:28 UTC
(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.