public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Randolph <mattr@erols.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] backups and world updates
Date: Thu, 28 Jul 2005 11:47:08 -0400	[thread overview]
Message-ID: <42E8FDFC.6000509@erols.com> (raw)
In-Reply-To: <42E8EA25.2030302@cisco.com>

Roy Wright wrote:

> Most of the time, I just open an konsole and do the
> update.  Occasionally I'll postpone if the update looks
> really large or time consuming.  For major gui components
> like KDE or xorg, I'll exit KDE and emerge from the
> command line over the weekend (ok, probably overly
> cautious, but I was burned once).


I have emerged kde and xorg-x11 from within kde without any problems.  I 
was even emerging firefox while surfing the web.  I probably played some 
Doom III too.

> Occasionally I'll get a blocking condition.  I really think
> twice now before just unblocking via package.keywords.
> I've found that waiting a day or two might result in
> portage handling the unblocking.

Firefox is a good example.  When mozilla-firefox-1.0.5 came out in ~arch 
in response to a GLSA, it hit +arch within the next 24-36 hours, if I 
recall.  I would just "ACCEPT_KEYWORDS='~amd64' emerge -a 
mozilla-firefox" in these situations rather than messing with 
package.keywords.  Then, I'd just keep an eye out for new stable 
packages and emerge them as appropriate.  If you unblock via 
package.keywords you will be resigning yourself to always using a 
testing version, thus exposing yourself to more new bugs than if you 
stayed in stable. 

However, if you simply wait a day or two, you are leaving yourself 
susceptible to exploits for that entire time.  Think about how many 
spams arrive in thunderbird in that amount of time.  It would only take 
one hastily written spam exploiting the right vulnerability and then 
POW!  As unlikely as that may be, I'd rather install security updates 
the very instant I find out about them instead.

-- 
"Pluralitas non est ponenda sine necessitate" - W. of O.

-- 
gentoo-amd64@gentoo.org mailing list



  parent reply	other threads:[~2005-07-28 15:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 13:53 [gentoo-amd64] backups and world updates Mark
2005-07-28 14:11 ` Brett Johnson
2005-07-31  3:48   ` [gentoo-amd64] emerge of neverwinter nights fails Mark Creamer
2005-07-31  3:57     ` shimi
2005-07-31  9:24       ` Michal Žeravík
2005-07-31  9:51         ` Peter Humphrey
2005-07-31 17:05           ` phil
2005-07-31 21:39             ` Michal Žeravík
2005-07-31 23:05               ` Mark Creamer
2005-08-01 15:59                 ` Chuck Milam
2005-08-01 16:11                   ` Peter Humphrey
2005-08-01 17:10                     ` Chuck Milam
2005-08-01 20:10                       ` phil
2005-08-01 18:49                     ` phil
2005-07-31  9:25     ` [gentoo-amd64] " Duncan
2005-07-28 14:22 ` [gentoo-amd64] backups and world updates Roy Wright
2005-07-28 15:13   ` Mark
2005-07-28 18:32     ` Roy Wright
2005-07-28 15:47   ` Matt Randolph [this message]
2005-07-28 15:15 ` Matt Randolph
2005-07-29 14:25 ` [gentoo-amd64] " Duncan

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=42E8FDFC.6000509@erols.com \
    --to=mattr@erols.com \
    --cc=gentoo-amd64@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