Summary: | Delete the sysutils/3dm port | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | ports.maintainer |
Component: | Individual Port(s) | Assignee: | Carlo Strub <cs> |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | CC: | cs, mat, takefu |
Priority: | Normal | ||
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
ports.maintainer
2014-05-11 02:30:00 UTC
A commit references this bug: Author: cs Date: Tue Jun 3 18:21:22 UTC 2014 New revision: 356386 URL: http://svnweb.freebsd.org/changeset/ports/356386 Log: Deprecated, does not fetch PR: 189641 Submitted by: ports.maintainer@evilphi.com (maintainer) Changes: head/sysutils/3dm/Makefile Committed. Thank you very much. If you have a look on lsi's site: http://www.lsi.com/support/Pages/download-results.aspx?keyword=3dm You'll see there has been a new release, v2.00.11.022. I understand if you don't want to maintain it any more though. PS: I did not notice it being unfetchable because I already have the distfiles. Yes, "new" as in released in 2012. To give you an idea of just how "no longer supported" this software is, that release contains binaries compiled for FreeBSD 5.x, 6.x and 7.x. Fortunately FreeBSD has really good backward compatibility. To answer the question more directly, no I can't support this port anymore. I don't have the necessary hardware to do it. Takefu@airport.fm sent a patch to take maintainership; I approve the maintainership transfer. Takefu@airport.fm, would you be willing to take over this port and fix fetchability? New maintainer takes over (via private mail). I resurrect the port. A commit references this bug: Author: cs Date: Thu Jun 5 09:41:33 UTC 2014 New revision: 356623 URL: http://svnweb.freebsd.org/changeset/ports/356623 Log: - Resurrect port - Switch maintainer PR: 189641 Submitted by: Darren Pilgrim (maintainer) Changes: head/sysutils/3dm/Makefile The patch I sent rejected? I'm guessing it fell out with the switch to Bugzilla. Might want to resend it by the official attachment mechanism. But, please open a new Problem Report, rather than re-using this one. |