public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: Heads up: Your system might be broken   and/or insecure due to serious patch-2.6 bug
Date: Wed, 02 Dec 2009 18:12:36 +0200	[thread overview]
Message-ID: <hf63la$cec$1@ger.gmane.org> (raw)
In-Reply-To: <20091202144816.GA4798@ca.inter.net>

On 12/02/2009 04:48 PM, Philip Webb wrote:
> 091202 Nikos Chantziaras wrote:
>> On 12/02/2009 12:51 PM, Alan McKinnon wrote:
>>> On Tuesday 01 December 2009 18:02:48 Nikos Chantziaras wrote:
>>>> Everyone should read the following and follow the advice given:
>>>> http://blog.flameeyes.eu/2009/12/01/gentoo-service-announcement-keep-clear-of-gnu-patch-2-6
>>> I emerged patch-2.60 when it hit ~amd64 then downgraded it 10 days later
>>> when a report on b.g.o. showed it was affecting OOo.
>>> Right in the middle of those 10 days, I ran 'emerge -e world'
>>> </sigh>
>> Yep, this bug was a major annoyance for me too.
>> I emerged patch-2.6 on November 15
>> and since then, being on ~amd64, a *lot* of other packages.
>> After downgrading, I needed to rebuild about 300 packages,
>> including all of KDE4, Qt, Firefox and OpenOffice.
>> Quite amazing how much damage a bug in a small package like this can have
>> on a source-based distro...
>
>   2  pieces of advice to avoid such problems:
> (1) never use the 'testing' versions of system pkgs;
> (2) never run 'emerge world' without the '-p' flag.

(3) Never run a mix of arch and ~arch if you can avoid it :D




  parent reply	other threads:[~2009-12-02 16:13 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 16:02 [gentoo-user] Heads up: Your system might be broken and/or insecure due to serious patch-2.6 bug Nikos Chantziaras
2009-12-02 10:51 ` Alan McKinnon
2009-12-02 13:45   ` [gentoo-user] " Nikos Chantziaras
2009-12-02 14:18     ` Neil Bothwick
2009-12-02 16:11       ` Volker Armin Hemmann
2009-12-02 14:33     ` Kevin O'Gorman
2009-12-02 14:48     ` Philip Webb
2009-12-02 15:30       ` Alan McKinnon
2009-12-02 15:49         ` Jesús Guerrero
2009-12-02 17:59         ` Stefan G. Weichinger
2009-12-02 20:04           ` Alan McKinnon
2009-12-02 20:54           ` Stefan G. Weichinger
2009-12-02 16:12       ` Nikos Chantziaras [this message]
2009-12-02 16:21       ` Neil Bothwick
2009-12-02 16:46       ` felix
2009-12-04 23:02       ` daid kahl
2009-12-05  5:14         ` Philip Webb
2009-12-05  6:47           ` Dale
2009-12-05 13:31           ` Volker Armin Hemmann
2009-12-05 14:10             ` Dale
2009-12-05 17:24               ` Neil Bothwick
2009-12-06  1:15                 ` Dale
2009-12-06  2:21                   ` Philip Webb
2009-12-06  2:53                     ` daid kahl
2009-12-06  9:06                       ` Dale
2009-12-07 10:46                       ` Neil Bothwick
2009-12-07 10:48                   ` Neil Bothwick
2009-12-07 11:18                     ` Dale
2009-12-05 15:08             ` Neil Bothwick
2009-12-05 16:10               ` Volker Armin Hemmann
2009-12-05 19:09             ` Philip Webb
2009-12-05 20:14               ` Volker Armin Hemmann
2009-12-06  6:20                 ` Alan McKinnon
2009-12-06  6:19               ` Alan McKinnon
2009-12-06 19:49                 ` Philip Webb
2009-12-07 11:01                   ` Neil Bothwick
2009-12-07 22:46                     ` Philip Webb
2009-12-07 23:04                       ` Alan McKinnon
2009-12-08  0:17                         ` Dale
2009-12-08 11:19                         ` Arttu V.
2009-12-08  1:04                       ` Neil Bothwick
2009-12-05 16:05           ` daid kahl
2009-12-05 16:26           ` [gentoo-user] Re: Heads up: Your system might be broken and/or insecure due to serious patch-2.6 bug, " Peter Humphrey
2009-12-06 10:59             ` Peter Humphrey
2009-12-06 14:11             ` Volker Armin Hemmann

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='hf63la$cec$1@ger.gmane.org' \
    --to=realnc@arcor.de \
    --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