all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: 18581@debbugs.gnu.org
Cc: request@debbugs.gnu.org
Subject: bug#18581: icecat fails to build on i686
Date: Tue, 30 Sep 2014 13:37:08 -0400	[thread overview]
Message-ID: <87lhp19fi3.fsf@yeeloong.lan> (raw)
In-Reply-To: <877g0narj1.fsf@yeeloong.lan> (Mark H. Weaver's message of "Mon, 29 Sep 2014 02:07:30 -0400")

retitle 18581 IceCat fails to build on i686 and needs security updates
severity 18581 serious
thanks

Mark H Weaver <mhw@netris.org> writes:
> The icecat build on i686 broke with the last core-updates merge.
> See:
>
>   http://hydra.gnu.org/build/96557/log/tail-reload
>   http://hydra.gnu.org/job/gnu/master/icecat-24.0.i686-linux

More importantly, the version of IceCat we are using is almost a year
old, with no security updates applied during that time.

We should update to IceCat 31, which is currently available only from
Trisquel, here:

  http://devel.trisquel.info/icecat/belenos/pool/main/i/icecat/icecat_31.0+gnu3.tar.gz

We also need security updates applied, notably the recent NSS signature
verification flaw: (CVE-2014-1568)

  http://seclists.org/oss-sec/2014/q3/736
  https://www.mozilla.org/security/announce/2014/mfsa2014-73.html

There may be other security patches as well.  I suggest looking on
mozilla.org for patches to version 31.

      Mark

  reply	other threads:[~2014-09-30 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29  6:07 bug#18581: icecat fails to build on i686 Mark H Weaver
2014-09-30 17:37 ` Mark H Weaver [this message]
2014-09-30 18:02   ` Andreas Enge
2014-09-30 19:58     ` bug#18581: IceCat fails to build on i686 and needs security updates Mark H Weaver
2014-09-30 22:03       ` Jason Self
2014-10-12 21:23 ` bug#18581: icecat fails to build on i686 Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lhp19fi3.fsf@yeeloong.lan \
    --to=mhw@netris.org \
    --cc=18581@debbugs.gnu.org \
    --cc=request@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.