Hello, I would like to propose to take maintainership of the port. Given the stability of the top of the repository on github. My aim is to replace the vm-bhyve port with the contents of the vm-bhyve-devel port. It has been about 2 years of development without an upstream tag.
Oops, the reporter has a ports commit bit. I have no part to play here. The last time current maintainer contributed to the port is 2022-07-19. However, there is no consecutive timeouts so far. Let's wait a feedback from the current maintainer for weeks. BTW, I think you can take sysutils/vm-bhyve-devel already. You created the port and you're almost the only contributor to the port. So you're practically the maintainer of the port. Anyway, thank you very much for working on this. I'm also a big fan of vm-bhyve and using it everyday.
(In reply to Dries Michiels from comment #1) Today Mateusz Kwiatkowski released vm-bhyve 1.6.0[1], please see bug 282782. All the credits go to Mateusz and his Serveraptor company since he handled these pull requests and spent a lot of time improving vm-bhyve. Please see also bug 278121, where the problem of stalled sysutils/vm-bhyve port was initially brought up. 1. https://github.com/churchers/vm-bhyve/releases/tag/v1.6.0
Ok Marek, I'm still waiting on maintainer timeout. If you can look for previous timeouts of this maintainer it will help. Normally I have to wait 3 months, but 3 consecutive timeouts is also sufficient. https://people.freebsd.org/~olivierd/porters-handbook/makefile-maintainer.html#:~:text=If%20the%20maintainer%20does%20not,made%20without%20explicit%20maintainer%20approval.
(In reply to Dries Michiels from comment #4) Perhaps the maintainer timeout mentioned could be shortened due to the port maintainer's excessive disregard for problem reports. Let me note only several such reports: - bug 237479, bug 237646 and bug 241699 were reported in 2019, - bug 248238 and bug 243576 - were reported in 2020, not even mentioning here newer PRs regarding sysutils/vm-bhyve.
(In reply to Dries Michiels from comment #4) I dare to say that the maintainer has been absent already for more than three months since nothing happened upstream. I'd rather go out portmgr@FreeBSD.org to address this by end of year.
(In reply to Marek Zarychta from comment #5) I dare here also to say that none of the are valid since they aren't port releated, but upstream problems mostly. No need to duplicate reports.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=f4320431e4c233c6f930340a1664f7d8ffdcbb01 commit f4320431e4c233c6f930340a1664f7d8ffdcbb01 Author: Dries Michiels <driesm@FreeBSD.org> AuthorDate: 2024-11-29 16:03:01 +0000 Commit: Dries Michiels <driesm@FreeBSD.org> CommitDate: 2024-11-29 16:03:58 +0000 sysutils/vm-bhyve: take maintainership PR: 282450 Approved by: maintainer timeout (consecutive and > 3months) sysutils/vm-bhyve/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)