Bug 282089 - textproc/jade: Unfetchable and upstream is gone
Summary: textproc/jade: Unfetchable and upstream is gone
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Cy Schubert
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-14 20:31 UTC by Daniel Engberg
Modified: 2024-10-17 17:37 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (cy)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Engberg freebsd_committer freebsd_triage 2024-10-14 20:31:19 UTC 
Consider to sunset port otherwise please fix MASTER_SITES, PATCH_SITES and WWW
Comment 1 Cy Schubert freebsd_committer freebsd_triage 2024-10-14 20:38:36 UTC 
Looks like his site is broken.

slippy$ ftp ftp.jclark.com
Connected to jclark.com.
500 OOPS: failed to open vsftpd log file:/var/log/vsftpd.log
ftp> pwd
Not connected.
ftp> ^D
slippy$
Comment 2 Cy Schubert freebsd_committer freebsd_triage 2024-10-14 20:41:22 UTC 
bsdlab.org is also gone.
Comment 3 Cy Schubert freebsd_committer freebsd_triage 2024-10-14 20:50:17 UTC 
Deprecated and expired. We should probably switch to openjade.
Comment 4 commit-hook freebsd_committer freebsd_triage 2024-10-14 20:50:24 UTC 
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=f9de5757c461e2dc78c9bac1788c44961ab995cb

commit f9de5757c461e2dc78c9bac1788c44961ab995cb
Author:     Cy Schubert <cy@FreeBSD.org>
AuthorDate: 2024-10-14 20:48:51 +0000
Commit:     Cy Schubert <cy@FreeBSD.org>
CommitDate: 2024-10-14 20:49:26 +0000

    textproc/jade: Deprecate and expire

    Upstream has disappeared.

    PR:     282089

 textproc/jade/Makefile | 3 +++
 1 file changed, 3 insertions(+)
Comment 5 Cy Schubert freebsd_committer freebsd_triage 2024-10-14 21:09:49 UTC 
Seems Norm Walsh, who's associated with James Clark, his site is also gone.

I think the path forward is clear. Switch any ports depending on jade to openjade.
Comment 6 Cy Schubert freebsd_committer freebsd_triage 2024-10-15 01:47:09 UTC 
Would it help that I host the distfiles on my website and at people.freebsd.org until we can migrate ports that depend on this port to openjade?

In that case do we want to extend the expiration date?
Comment 7 Daniel Engberg freebsd_committer freebsd_triage 2024-10-16 19:33:29 UTC 
Hi,

It's also available here https://sourceware.org/pub/docbook-tools/new-trials/SOURCES/ although for the sake of maintenance I'd say sunset both and remove support in tree as both upstream projects are dead and it's just a matter of time before they break.

Best regards,
Daniel
Comment 8 Cy Schubert freebsd_committer freebsd_triage 2024-10-16 20:52:08 UTC 
As I'm not maintainer of the other ports, probably not my place to flag them deprecated too. I'm sure Rene will handle the dependency fallout from this and expire the ports that depend on jade.
Comment 9 Daniel Engberg freebsd_committer freebsd_triage 2024-10-17 17:34:55 UTC 
To be honest I would suggest that we're more aggressive about deprecation, neither jade and openjade are "active" and/or likely to see more development. Given it's a handful of ports being affected by this change and it's a documentation related port I'd sunset both and notify downstream consumers in a mail or a PR. We simply don't have the manpower to maintain ~ports@FreeBSD.org status ports until the end of time.