[gentoo-user] Big problem: Seamonkey

[gentoo-user] Big problem: Seamonkey

[Alan Grimes]

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.

-- 
IQ is a measure of how stupid you feel.

Powers are not rights.

Re: [gentoo-user] Big problem: Seamonkey

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 632 bytes --]

On Wednesday 18 Nov 2015 16:54:23 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.

http://gpo.zugaina.org/www-client/seamonkey

There was also the CVS archive, but the link is dead.  Probably all moved to 
git now?  Someone else should be more knowledgeable on current portage 
architecture.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[gentoo-user] Re: Big problem: Seamonkey

[»Q«]

On Wed, 18 Nov 2015 11:54:23 -0500
Alan Grimes <ALONZOTG@verizon.net> 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.

<https://gitweb.gentoo.org/repo/gentoo.git/tree/www-client/seamonkey/seamonkey-2.35.ebuild?id=e45cfc56ca7f5ae52ae873c30da1c86b898dc5d0>

In case it helps anyone else find old stuff, I got there by looking at
the log on the web -- when/where a file is removed or added, it has a
link to that file.

Re: [gentoo-user] Big problem: Seamonkey

[Raffaele BELARDI]

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

Re: [gentoo-user] Re: Big problem: Seamonkey

[Alan Grimes]

Okay, since just dumping the legacy e-build into the portage tree would
be too easy, it was prevented. How do I build an ebuild out-of-tree? =(

I've kinda wanted to know how to do this for years but was too lazy to
track down the information but these later versions of Seamonkey are so
crashtastic that I need to get rid of it... I got a million irrelevant
results when I tried to google it. =(

-- 
IQ is a measure of how stupid you feel.

Powers are not rights.

Re: [gentoo-user] Re: Big problem: Seamonkey

[Raffaele BELARDI]

Alan Grimes wrote:
> Okay, since just dumping the legacy e-build into the portage tree would
> be too easy, it was prevented. How do I build an ebuild out-of-tree? =(
>

create a portage overlay and put your ebuild in there, then mask 
seamonkey > 2.38 in package.mask:


$ ll /usr/portage/local/mygentoo/www-plugins/adobe-flash/
total 8
-rw-r--r-- 1 portage portage 3561 Jul 22  2013 
adobe-flash-10.3.183.90.ebuild
-rw-r--r-- 1 portage portage  786 Jul 22  2013 Manifest

$ grep OVERLAY /etc/portage/make.conf
# PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
#PORTDIR_OVERLAY=/usr/portage/local/mygentoo

I don't remember the details since I did it a long time ago and no 
longer need it.

raffaele

Re: [gentoo-user] Re: Big problem: Seamonkey

[Todd Goodman]

* Raffaele BELARDI <raffaele.belardi@st.com> [151119 10:24]:
> Alan Grimes wrote:
> > Okay, since just dumping the legacy e-build into the portage tree would
> > be too easy, it was prevented. How do I build an ebuild out-of-tree? =(
> >
> 
> create a portage overlay and put your ebuild in there, then mask 
> seamonkey > 2.38 in package.mask:
> 
> 
> $ ll /usr/portage/local/mygentoo/www-plugins/adobe-flash/
> total 8
> -rw-r--r-- 1 portage portage 3561 Jul 22  2013 
> adobe-flash-10.3.183.90.ebuild
> -rw-r--r-- 1 portage portage  786 Jul 22  2013 Manifest
> 
> $ grep OVERLAY /etc/portage/make.conf
> # PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
> #PORTDIR_OVERLAY=/usr/portage/local/mygentoo
> 
> I don't remember the details since I did it a long time ago and no 
> longer need it.
> 
> raffaele

I believe using PORTDIR_OVERLAY is now deprecated and overlays are
configured in /etc/portage/repos.conf/*

Check out:

https://wiki.gentoo.org/wiki/Overlay/Local_overlay

Todd

Re: [gentoo-user] Re: Big problem: Seamonkey

[Raffaele BELARDI]

Todd Goodman wrote:
> I believe using PORTDIR_OVERLAY is now deprecated and overlays are
> configured in /etc/portage/repos.conf/*
>
> Check out:
>
> https://wiki.gentoo.org/wiki/Overlay/Local_overlay

Good to know, I suppose the bit:

   root # repoman manifest

is equivalent to:

   root # ebuild <blah blah> manifest

right?

Re: [gentoo-user] Re: Big problem: Seamonkey

[Todd Goodman]

* Raffaele BELARDI <raffaele.belardi@st.com> [151119 10:45]:
> Todd Goodman wrote:
> > I believe using PORTDIR_OVERLAY is now deprecated and overlays are
> > configured in /etc/portage/repos.conf/*
> >
> > Check out:
> >
> > https://wiki.gentoo.org/wiki/Overlay/Local_overlay
> 
> Good to know, I suppose the bit:
> 
>    root # repoman manifest
> 
> is equivalent to:
> 
>    root # ebuild <blah blah> manifest
> 
> right?

I assume so but I always still do the above (ebuild <blah blah>
manifest) and it still works for me.

Todd