xsp bug: fastcgi-mono-server4 fails to start under certain circumstances

[Romain Tartière]

Hello

On Tue, Oct 14, 2014 at 12:13:11AM +0200, Enrico Maria Crisostomo wrote:
> After upgrading several packages in an existing FreeBSD 10.0
> installation I just experienced what seems to be this bug:
> 
> https://bugzilla.xamarin.com/show_bug.cgi?id=2876#c10
> 
> It’s pretty old, it was fixed in xsp master a couple of years ago, it
> was working before the upgrade, but somehow it has made to the updated
> FreeBSD port. Applying the same workaround described in the bug report
> solves the problem and everything runs fine again.
> 
> I think somebody may want to look into this: I don’t know whether it’s
> an xsp regression upstream or a port problem, but it certainly seems
> to break existing functionality.

You are right, the fix is not in the FreeBSD ports tree because upstream
does not provide tarballs older than xsp-2.10.2 (what we have in the
ports).

I already started to switch the source to Github, I hope to manage this
today, and hopefully you will be able to install xsp-3.0.11 tonight :-)

Regards,
Romain

-- 
Romain Tartière <romain at FreeBSD.org>  http://people.FreeBSD.org/~romain/
pgp: 8234 9A78 E7C0 B807 0B59  80FF BA4D 1D95 5112 336F (ID: 0x5112336F)
(plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 648 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-mono/attachments/20141014/b1ea36d6/attachment.sig>