From owner-freebsd-gecko@freebsd.org Thu Mar 31 22:49:35 2016 Return-Path: Delivered-To: freebsd-gecko@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 2EE3BAE4A69 for ; Thu, 31 Mar 2016 22:49:35 +0000 (UTC) (envelope-from le@main.put.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2099C19BA for ; Thu, 31 Mar 2016 22:49:35 +0000 (UTC) (envelope-from le@main.put.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1FED9AE4A68; Thu, 31 Mar 2016 22:49:35 +0000 (UTC) Delivered-To: gecko@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 1F8F8AE4A67 for ; Thu, 31 Mar 2016 22:49:35 +0000 (UTC) (envelope-from le@main.put.com) Received: from main.put.com (main.put.com [12.144.5.2]) by mx1.freebsd.org (Postfix) with ESMTP id C76A619B9 for ; Thu, 31 Mar 2016 22:49:34 +0000 (UTC) (envelope-from le@main.put.com) Received: from main.put.com (localhost [127.0.0.1]) by main.put.com (8.12.10/8.12.10) with ESMTP id u2VMnd7Z036883; Thu, 31 Mar 2016 17:50:09 -0500 (EST) Received: from localhost (le@localhost) by main.put.com (8.12.10/8.12.10/Submit) with ESMTP id u2VMnc9b036880; Thu, 31 Mar 2016 17:49:38 -0500 (EST) Date: Thu, 31 Mar 2016 17:49:38 -0500 (EST) From: Louis Epstein To: Jan Beich cc: Subject: Re: New Seamonkey Trouble? In-Reply-To: Message-ID: <20160331174853.W36751-100000@main.put.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2016 22:49:35 -0000 On Tue, 29 Dec 2015, Jan Beich wrote: > Louis Epstein writes: > > > We are once again seeing a new revision of the Seamonkey port > > (2.39_3) > > refuse to install via Portmaster because of known vulnerabilities > > (which presumably affect the older version as well). > > > > I suppose I'll have to wait for pkg to catch up to run the > > update? > > SeaMonkey release process lags behind Firefox. It's unrelated to gecko@ > being undermaintained. 2.40 simply has no usable distfile yet. But now?? The SeaMonkey homepage detects my 2.39 and tells me to get 2.40. -=-=- The World Trade Center towers MUST rise again, at least as tall as before...or terror has triumphed.