From owner-freebsd-mono@FreeBSD.ORG Tue Oct 14 09:02:05 2014 Return-Path: Delivered-To: mono@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A30B969C for ; Tue, 14 Oct 2014 09:02:05 +0000 (UTC) Received: from marvin.blogreen.org (marvin.blogreen.org [IPv6:2001:470:1f13:b9c::2]) by mx1.freebsd.org (Postfix) with ESMTP id 36CCFD24 for ; Tue, 14 Oct 2014 09:02:05 +0000 (UTC) Received: by marvin.blogreen.org (Postfix, from userid 1001) id 1BE47197AB3; Tue, 14 Oct 2014 11:01:56 +0200 (CEST) Date: Tue, 14 Oct 2014 11:01:56 +0200 From: Romain =?iso-8859-1?Q?Tarti=E8re?= To: Enrico Maria Crisostomo Subject: Re: xsp bug: fastcgi-mono-server4 fails to start under certain circumstances Message-ID: <20141014090155.GC42254@FreeBSD.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="orO6xySwJI16pVnm" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://romain.blogreen.org/pubkey.asc User-Agent: Mutt/1.5.23 (2014-03-12) Cc: mono@freebsd.org X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2014 09:02:05 -0000 --orO6xySwJI16pVnm Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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: >=20 > https://bugzilla.xamarin.com/show_bug.cgi?id=3D2876#c10 >=20 > It=E2=80=99s 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. >=20 > I think somebody may want to look into this: I don=E2=80=99t know whether= it=E2=80=99s > 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 --=20 Romain Tarti=C3=A8re http://people.FreeBSD.org/~romai= n/ pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) (plain text =3Dnon-HTML=3D PGP/GPG encrypted/signed e-mail much appreciated) --orO6xySwJI16pVnm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGcBAEBAgAGBQJUPOaDAAoJELpNHZVREjNvO7EL/3B7BtCey88uKNVFGToRDgd8 nRKzqjo/pNwSuG7e5UTQtV5aEUDCoOsfIbNhNObe8GlYmXBmC6uyAs9Vn4EtTYVT iY4oJFgyGodGhES4P/upd5/2j2Fy/NTZ+ZjF2p9jVk05FtwbI6s42Oas/S97/CdL vEZcuE/ZddqVTSFxaYwl54378ZpZmE5pphOK13370xr9na92ngh+ZR3BPnum7PKn fScDqqi9IjpjBnyH0zdvKTQ/uBOEq3nm8Iz/5phfi6BCvyYrCqb3xMLPuWmR/BG7 M5AL/kBg082DJussXhFmVByIes9vb8/fV0R8u2ld6/LtjWP+4wn56r1b+amqjZJW cEKnFw3MKsmJsaYd74/3POtzePsiiuzaidMCPi02MksLBgkU3hrvM+Wpxv/bi+SK s/OYNzYFXEwqVSjg7kwFMhkVIkXOiSO59CsrSmsBAL+Qvo6OTqA1ig/FXGgNNuaB xj17BQ6sDQPQ4dCLa4TIMb913MqrXpEjuHwEHsImnA== =YNSa -----END PGP SIGNATURE----- --orO6xySwJI16pVnm--