Bug 238535
| Summary: | devel/py-hgsubversion: unbreak with mercurial 5.0 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Charlie Li <vishwin> | ||||
| Component: | Individual Port(s) | Assignee: | freebsd-python (Nobody) <python> | ||||
| Status: | Closed Feedback Timeout | ||||||
| Severity: | Affects Many People | CC: | rene | ||||
| Priority: | --- | Keywords: | easy, patch-ready, regression | ||||
| Version: | Latest | Flags: | bugzilla:
maintainer-feedback?
(python) |
||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| URL: | https://bitbucket.org/durin42/hgsubversion/commits/all | ||||||
| Attachments: |
|
||||||
It seems 6a6ce9d is the only thing required for mercurial 5.0 fix. The commit before, 5d8603f, is also needed for future-proofing when mercurial 5.1 comes around. The other commits are bug fixes and removal of compat code for old mercurial that we don't even carry in quarterly anymore. Ping? Notice that this port expired today because it is Python-2.7-only, but has been retained for now. (In reply to Rene Ladan from comment #3) All of its dependencies are python 2.7 only. That means this port is still python 2.7 only whether it's patched or not. (In reply to Sunpoet Po-Chuan Hsieh from comment #4) Hmm, indeed... No feedback from maintainer (python@) in over a month, and the patch does not address upgrading the port to Python 3. Closing this PR. |
Created attachment 205025 [details] py-hgsubversion-hg5.0.patch Mercurial 5.0 introduced some breaking API changes that this extension depends on. This patch pulls in all revisions between the 1.9.3 release and tip as of this writing (6a6ce9d), since there were, again, multiple API breakages. Been dogfooding this since devel/mercurial updated to 5.0; passes testport, portlint and runtime.