Bug 276537 - editors/jove: Port (possibly) incorrectly removed as expired, offer to reinstate and take maintainership
Summary: editors/jove: Port (possibly) incorrectly removed as expired, offer to reinst...
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Fernando Apesteguía
URL:
Keywords: needs-patch
Depends on:
Blocks:
 
Reported: 2024-01-22 21:44 UTC by Terry Kennedy
Modified: 2024-02-23 20:43 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Terry Kennedy 2024-01-22 21:44:42 UTC
MOVED had an entry added a few days ago:
editors/jove||2024-01-18|Has expired: No upstream update in last 23 years

https://svnweb.freebsd.org/ports/head/editors/jove/ still shows it, so I can't see which committer removed it.

23 years seemed like a long time, so I checked. The last release on the FTP server in the Makefile is "Jul 11  2010 jove4.16.0.73.tgz", so only 13 years 8-)

Development seems to have moved to GitHub, where there seems to be an active development / user community: https://github.com/jonmacs/jove

The latest release is 4.17.5.3 from March 21, 2023.

There seem to be quite a few Jove PR's that were closed with feedback-timeout: 249148, 248588, 247705, etc.

I have a user that relies on this port. Given that "make maintainer" reports ports@FreeBSD.org, this port seems to be unmaintained.

If no one else is interested, I can look into building the current release and submitting a diff to have the port reinstated using the current release. However, I am not a Jove / Emacs user, so I'm probably not the best choice to be nominated as maintainer.
Comment 1 Fernando Apesteguía freebsd_committer freebsd_triage 2024-01-23 07:46:23 UTC
^Triage: assigning to the committer that removed the port.

@Terry, if you are interested in this port, could you attach a patch with an update?
Comment 2 Terry Kennedy 2024-01-23 07:48:44 UTC
(In reply to Fernando Apesteguía from comment #1)
Sure. I'll take a look at it in the next few days.

If it is too difficult, I'll just tell my user he should switch to a different editor. 8-}
Comment 3 Muhammad Moinur Rahman freebsd_committer freebsd_triage 2024-01-23 12:10:39 UTC
(In reply to Terry Kennedy from comment #0)
Thanks for the report. However the ftp dates are not relevant here as if you remove the files and re add the files the date will change. If you look at the entire git log you will see that this has been with version 4.16 in the tree which was the primary reason of removing.

However as you have mentioned that there are active upstream development going on feel free to submit a patch and take over maintainership as unmaintained ports are more susceptive to removal than maintained ports. While we try to keep as many ports as possible we should also make sure that it does not add overhead to portmgr as they have to do sweeping changes while required.

Before submitting a port make sure to test build with poudriere and use portlint/portclippy.
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2024-01-25 07:14:48 UTC
(In reply to Terry Kennedy from comment #0)
svnweb is deprecated.  It's probably going to show you all kinds of stale stuff :-)
Comment 5 Terry Kennedy 2024-01-25 07:54:49 UTC
(In reply to Mark Linimon from comment #4)
Indeed. My muscle memory hasn't caught up to the repo flavor du jour. Sorry about that...
Comment 6 Terry Kennedy 2024-02-23 20:43:42 UTC
My user indicated that this port is no longer important to them, so I didn't make further progress.

If someone else needs this port, they can open a PR and reference this one.