Details here: SECURITY UPDATE (8 Apr 2014): All mod_spdy users should upgrade to mod_spdy 0.9.4.2 immediately to fix the heartbleed bug in mod_spdy's linked version of OpenSSL. See issue 85 for details. https://code.google.com/p/mod-spdy/ Fix: Update mod_spdy port to 0.9.4.2 version.
Responsible Changed From-To: freebsd-ports-bugs->apache apache@ wants this port PRs (via the GNATS Auto Assign Tool)
Maintainer of www/mod_spdy, Please note that PR ports/189109 has just been submitted. If it contains a patch for an upgrade, an enhancement or a bug fix you agree on, reply to this email stating that you approve the patch and a committer will take care of it. The full text of the PR can be found at: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/189109 -- Edwin Groothuis via the GNATS Auto Assign Tool edwin@FreeBSD.org
State Changed From-To: open->feedback Awaiting maintainers feedback (via the GNATS Auto Assign Tool)
Seems the author of the port is not around or reachable. Best solution is to mark the port as forbidden an deprecate in 4 weeks.
This seems like a rather important port. Isn't spdy relatively popular? I'll get a new distfile mirrored. Oddly this thing requires the apache source. Is there some way we can pull the Apache version dynamically instead of having it hardcoded into the port?
Hm, (un)luckily it is at the moment the only implementation. http://lists.w3.org/Archives/Public/ietf-http-wg/2014AprJun/0815.html I also thought about dynamically add apache22 to the mix via `make -V _DISTDIR -C ${PORTSDIR}/www/apache22` but that's a really dirty workaround. A small improvement would be already if the port picks the source from the apache22 DIST_SUBDIR. Some weeks ago there was a discussion on the upstream list to include spdy because of the ugly buildsystem and to keep it more compatible with current apache releases. http://marc.info/?t=139887674700005&r=1&w=2 Haven't done any tests/checkouts from this repo (enotime) https://issues.apache.org/jira/browse/INFRA-7653