Date: Sun, 3 Apr 2016 21:17:29 -0400 (EDT) From: Louis Epstein <le@main.put.com> To: Jan Beich <jbeich@vfemail.net> Cc: <gecko@freebsd.org> Subject: Re: New Seamonkey Trouble? Message-ID: <20160403211603.O1980-100000@main.put.com> In-Reply-To: <k2kf-o0g8-wny@vfemail.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 3 Apr 2016, Jan Beich wrote: > Louis Epstein <le@main.put.com> writes: > > > On Tue, 29 Dec 2015, Jan Beich wrote: > > > >> Louis Epstein <le@main.put.com> 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. > > 2.40 uses the same browser engine as firefox 43.0 which is vulnerable. > As mail/thunderbird and www/firefox-esr are going to switch to 45.1esr > in a few weeks converting www/seamonkey to use mail/thunderbird distfile > would be more desirable. Upstream appears to be drowning in its own > infra issues. Hmmm...I note that today I am NOT getting the "you are using a vulnerable old version" message from the SeaMonkey homepage. Is 2.41 expected any time soon? > If you still want 2.40 submit patches provided seamonkey-i18n, > linux-seamonkey and Mk/Uses/gecko.mk are kept in sync. > -=-=- The World Trade Center towers MUST rise again, at least as tall as before...or terror has triumphed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160403211603.O1980-100000>