[gentoo-dev] firefox-1.5.x still in ~arch

[gentoo-dev] firefox-1.5.x still in ~arch

[Matthias Langer]

I'm just curious: What is the reason that firefox-1.5.x is still in
~arch ?

-- 
gentoo-dev@gentoo.org mailing list

[gentoo-dev] Re: firefox-1.5.x still in ~arch

[Duncan]

Matthias Langer posted <1142778259.17324.16.camel@sputnik886.ruz-net>,
excerpted below,  on Sun, 19 Mar 2006 15:24:19 +0100:

> I'm just curious: What is the reason that firefox-1.5.x is still in
> ~arch ?

General policy is that an ebuild should be bug-free in ~arch for 30 days
before it is stabilized.  Individual herds and maintainers may have their
own policies, but the above 30 day guideline is the general Gentoo rule of
thumb.

Looking at the changelog, mozilla-firefox-1.5.0.1-r2 was only added to the
tree on February 24.  The -r2 indicates updates serious enough to bump the
release number were released at least twice, and the 1.5 ebuilds are at
-r9, indicating 10 versions (the first being -r0, not marked with an
release number, of course).

That's a /lot/ of versions!  I'd guess there have simply been enough
issues that no version of 1.5 has yet made it 30 days bug-free in ~arch,
altho the .0.1-r2 version above is getting close to 30 days in ~arch now,
tho I don't know its bug status.

I often check the portage tree changelogs and Gentoo bugzilla site status
of particular packages that I'm interested in.  I'm glad the info is
available, as it has proven useful quite often.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Re: firefox-1.5.x still in ~arch

[Matthias Langer]

On Sun, 2006-03-19 at 07:56 -0700, Duncan wrote:
> Matthias Langer posted <1142778259.17324.16.camel@sputnik886.ruz-net>,
> excerpted below,  on Sun, 19 Mar 2006 15:24:19 +0100:
> 
> > I'm just curious: What is the reason that firefox-1.5.x is still in
> > ~arch ?
> 
> General policy is that an ebuild should be bug-free in ~arch for 30 days
> before it is stabilized.  Individual herds and maintainers may have their
> own policies, but the above 30 day guideline is the general Gentoo rule of
> thumb.
> 
> Looking at the changelog, mozilla-firefox-1.5.0.1-r2 was only added to the
> tree on February 24.  The -r2 indicates updates serious enough to bump the
> release number were released at least twice, and the 1.5 ebuilds are at
> -r9, indicating 10 versions (the first being -r0, not marked with an
> release number, of course).
> 
> That's a /lot/ of versions!  I'd guess there have simply been enough
> issues that no version of 1.5 has yet made it 30 days bug-free in ~arch,
> altho the .0.1-r2 version above is getting close to 30 days in ~arch now,
> tho I don't know its bug status.
> 
> I often check the portage tree changelogs and Gentoo bugzilla site status
> of particular packages that I'm interested in.  I'm glad the info is
> available, as it has proven useful quite often.
> 
> -- 
Thanks for your answer; however, i've seen new versions of firefox
getting from ~arch to stable much faster than 30 days, but i guess that
was because of security issues; by the way, i was happy to read

"
*mozilla-firefox-1.5.0.1-r1 (09 Feb 2006)

  09 Feb 2006; <anarchy@gentoo.org> +mozilla-firefox-1.5.0.1-r1.ebuild:
  official branding support, ewarn about regchrome
"

that gentoo now has official branding support ...

Matthias


-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] firefox-1.5.x still in ~arch

[Patrick Lauer]

[-- Attachment #1: Type: text/plain, Size: 550 bytes --]

On Sun, 2006-03-19 at 15:24 +0100, Matthias Langer wrote:
> I'm just curious: What is the reason that firefox-1.5.x is still in
> ~arch ?
Looking at bugreports it seems that firefox 1.5 has - at least on some systems - quite serious issues.

Some users report excessive memory usage, I've masked it on my system
because it was unbearably slow (multiple seconds to open a new empty
tab). As long as these issues are not reliably fixed I think firefox
should stay in ~arch


Patrick
-- 
Stand still, and let the rest of the universe move

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