From: Raffaele BELARDI <raffaele.belardi@st.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Big problem: Seamonkey
Date: Thu, 19 Nov 2015 13:26:15 +0100 [thread overview]
Message-ID: <564DBFE7.4090507@st.com> (raw)
In-Reply-To: <564CAD3F.1020208@verizon.net>
Alan Grimes wrote:
> Hey, both Seamonkey 2.38 and 2.39 are unstable to the point of being
> utterly unusable, I need to re-install 2.35 but it has already been
> removed from Portage, HELP!!
>
> There are some mutterings on the upstream bugtracker about it being
> related to how Cairo is being compiled/poorly coded, but urgently, I
> need 2.35 back.
Maybe I've been lucky, but I've had and have no problems with 2.38 nor
2.39 on ~x86 and I do use Seamonkey a lot. This does not help you but I
wonder why.
raffaele
prev parent reply other threads:[~2015-11-19 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 16:54 [gentoo-user] Big problem: Seamonkey Alan Grimes
2015-11-18 17:10 ` Mick
2015-11-18 18:25 ` [gentoo-user] " »Q«
2015-11-19 15:08 ` Alan Grimes
2015-11-19 15:24 ` Raffaele BELARDI
2015-11-19 15:32 ` Todd Goodman
2015-11-19 15:45 ` Raffaele BELARDI
2015-11-19 15:51 ` Todd Goodman
2015-11-19 12:26 ` Raffaele BELARDI [this message]
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=564DBFE7.4090507@st.com \
--to=raffaele.belardi@st.com \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox