public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] WARNING latest lvm2 breaks systems with older udev
Date: Wed, 28 Mar 2012 22:26:25 -0400	[thread overview]
Message-ID: <CA+czFiBLSe1mW_2mn04GSPDMmzdq-W0dA88Cdm9nBwp27HW0eg@mail.gmail.com> (raw)
In-Reply-To: <CAA2qdGU5H4o8M4ys3XTqdAV27eB6R5HiYk4NCiTjSsbsE1=vDQ@mail.gmail.com>

On Wed, Mar 28, 2012 at 7:58 PM, Pandu Poluan <pandu@poluan.info> wrote:
>
> On Mar 29, 2012 1:42 AM, "Michael Mol" <mikemol@gmail.com> wrote:
>>
>> On Wed, Mar 28, 2012 at 2:29 PM, Alex Schuster <wonko@wonkology.org>
>> wrote:
>> > Stefan G. Weichinger writes:
>> >
>> >> Am 28.03.2012 12:24, schrieb Stefan G. Weichinger:
>> >> > Am 27.03.2012 22:53, schrieb Allan Gottlieb:
>> >> >> My system wouldn't fully boot this morning after updating lvm
>> >> >> (~amd64).
>> >> >>
>> >> >> Fortunately a mount -a followed by
>> >> >>
>> >> >>    emerge -1 lvm2-previous version
>> >> >>
>> >> >> has be back in business (with the new lvm2 masked).
>> >
>> > Yikes.
>> >
>> >> >> I subsequently found the bug below.
>> >
>> > Thanks for being so kind of doing so!
>>
>> Just to note, it was Pandu who filed that report. Allan *found* the bug
>> report.
>>
>
> Me??
>
> Uh, the bug was filed by Paweł Rumian, not me...
>
>> Just pointing it out because I've seen two people misattribute it now.
>>
>
> And you, too :-D

LOL.

Thanks. :)


-- 
:wq



  reply	other threads:[~2012-03-29  3:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 20:53 [gentoo-user] WARNING latest lvm2 breaks systems with older udev Allan Gottlieb
2012-03-28 10:24 ` Stefan G. Weichinger
2012-03-28 18:09   ` Stefan G. Weichinger
2012-03-28 18:29     ` Alex Schuster
2012-03-28 18:36       ` Michael Mol
2012-03-28 23:58         ` Pandu Poluan
2012-03-29  2:26           ` Michael Mol [this message]
2012-03-29  2:35         ` Allan Gottlieb
2012-03-28 18:41       ` Alex Schuster

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=CA+czFiBLSe1mW_2mn04GSPDMmzdq-W0dA88Cdm9nBwp27HW0eg@mail.gmail.com \
    --to=mikemol@gmail.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