From owner-freebsd-current@freebsd.org Thu Feb 9 15:40:11 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE109CD7DC8 for ; Thu, 9 Feb 2017 15:40:11 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id DA61A128F for ; Thu, 9 Feb 2017 15:40:11 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id D626ACD7DC2; Thu, 9 Feb 2017 15:40:11 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D599CCD7DC1; Thu, 9 Feb 2017 15:40:11 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9AB45128E; Thu, 9 Feb 2017 15:40:11 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.127] (helo=rmmprod05.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1cbqpL-0000XE-BI; Thu, 09 Feb 2017 16:40:07 +0100 Received: from mail by rmmprod05.runbox with local (Exim 4.86_2) (envelope-from ) id 1cbqpL-0004hT-9P; Thu, 09 Feb 2017 16:40:07 +0100 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Thu, 09 Feb 2017 15:40:07 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "ports" , "timothy.bouquet" CC: "gecko" , "current" Subject: r313305 libevent2 problem and workaround NEED FIXING... Date: Thu, 09 Feb 2017 07:40:07 -0800 (PST) X-Mailer: RMM6 Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 15:40:12 -0000 A huge six-day fix of seamonkey breakage on 11-CURRENT of april 2016, upgra= ded finally last night to pkg 12-CURRENT feb 2017 working and etc by base.txz=20 overwrite etc... ............................................... I've many many hours to restore the desktop to full how-it-was-before, but = as it is working, now, a wholesale 3xxx reinstall of ports by pkg (which had to occur OUT OF Xorg for stall issues... and lack of granularity in the use of "pkg upgrade" (ie thirty-by-thirty) or lack of code in "pkg install" (terse deinstalls necc. where reinstalls were needed) as of this date.... ................................................. Mostly fixed as I write from the fixed system, but the only reason I am usi= ng seamonkey now, and also fixed firefox, just then, is the series of commands... which = I expect to maybe re-break when v12 upgrades _4 seamonkey to _5 which broke (segfaults)= here from ports the port... but in the meantime .......................................... cp -iv /[backup mount}/usr/local/lib/libevent-2.0.so.5.10 /usr/local/lib/co= mpat/libevent-2.0.so.5 cp -iv /usr/local/lib/compat/libevent-2.0.so.5 /usr/ports/www/seamonkey/lib= event-2.0.so.5-NECC-FOR-SEAMONKEY .......................................... backup restored a newly overnight broken seamonkey AND firefox, the former = not as of a day or so from ports being able to run. ......................................... This is quite the showstopper here... almost forced a reinstall of 2004-201= 7 ( this desktop) to a 2016-STABLE v11 new disk.... which I may have to revert to if seamonke= y breaks again or the next iteration of libevent/seamonkey/firefox does not fix up with CLI s= uch as this time. .................................... Out of time for a PR or bug report offically, and hope to gain more pressing urgency to this problem than might be attained, that way... out of= time also. ................................... Thanks for reading, and thanks for putting up with interim list messages in= the last few days which still had a bit of almost PBKAC combined with lack of documentat= ion combined with newbie-ness here which had yet to resolve...=20 and thanks for the forum post(s) which helped resolve the seemingly-lost-ca= use issue of the v11-CURRENT upgrade to v12-CURRENT which appears to have worked today vs s= everal days ago, IF seamonkey continues to be fixable locally. .................................... J. Bouquet=20=