fvwm is no more supported. http://fvwm.sourceforge.net/download/ --> Obsolete packages: Older 2.x.x versions: here (Note! Versions prior to 2.4.0 are no longer supported.) Last 1.xx Version: 1.24r (Note! This version is no longer supported.) Very old 1.x releases: here
Do you have a patch for this to set as stated in bug?
Created attachment 206309 [details] svn-diff-fvwm Ups... forgot the patch.
A commit references this bug: Author: jgh Date: Tue Aug 6 17:25:34 UTC 2019 New revision: 508263 URL: https://svnweb.freebsd.org/changeset/ports/508263 Log: - set deprecation - set expiration to 2019-10-05 PR: 239661 Submitted by: w.schwarzenfeld@utanet.at (based on) Changes: head/x11-wm/fvwm/Makefile
Thanks for your contribution! I adjusted expiration date, as this seemed too generous for an unsupported upstream version that is unfetchable. Thanks, again! -jgh
Okay!
The source code is now online again on https://github.com/fvwmorg/fvwm1 Can the port please not be deprecated?
Can you provide a patch with new MASTER_SITE?
Created attachment 206938 [details] svn-diff-fvwm-new Please test the patch, I cannot test it I have fvwm-crystal installed (this conflicts).
Comment on attachment 206938 [details] svn-diff-fvwm-new No, was wrong.
Created attachment 206939 [details] svn-diff-fvwm-new_v2 This should work.
Created attachment 206940 [details] svn-diff-fvwm-new_v3 Forgot I have commented out conflicts.
Created attachment 206943 [details] svn-diff-fvwm-new_v3 Forgot I have commented out conflicts.
Please use USE_GITHUB.
Syntax?
Comment on attachment 206940 [details] svn-diff-fvwm-new_v3 Patch needs updating to USE_GITHUB [1] and not use a moving branch target (master) [1] https://www.freebsd.org/doc/en/books/porters-handbook/book.html#makefile-master_sites-github-description
Created attachment 206950 [details] svn-diff-fvwm-new_v4 Found it.
Comment on attachment 206950 [details] svn-diff-fvwm-new_v4 I can confirm that the port builds, installs, and default fvwm starts. I can do more sophisticated tests if needed once the rest of the notebook is all a bit more working as well :-)
The updated patch to bring the software back will not be committed to the tree. This is a unmaintained project.
(In reply to Jason Helfman from comment #18) What needs to be done to keep it alive? Just because development has stopped (and by that argument a loooong time ago) doesn't mean people are not using it anymore. I can keep a private copy of the port, but if two people do that we are already wasting resources.
(In reply to Bjoern A. Zeeb from comment #19) Please reach out to portmgr@ regarding this issue. I am fine in working through whatever the solution is to have it resolved, but at this point portmgr@ has agreed that adding this to the tree is not an option in this state.
^Triage: Correct resolution (FIXED, per original report) @Bjoern If you'd like to make a case for the ports resurrection, please: - Open a new issue: Assignee: portmgr - With the patch attached here included - With this issue ID in See Also: