From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem with update world
Date: Tue, 10 Nov 2009 09:30:32 -0600 [thread overview]
Message-ID: <4AF98718.3040104@gmail.com> (raw)
In-Reply-To: <200911101611.48772.wonko@wonkology.org>
Alex Schuster wrote:
> Dale writes:
>
>
>> I am running into the same thing. I'm updating everything else then
>> going to tackle this. In theory, you have to unmerge device-mapper
>> then let it update. Something like:
>>
>> emerge -C device-mapper && emerge -uvDN world
>>
>> That's my plan at least. Unless someone else posts a better one.
>>
>
> I just unmerged device-mapper and updated lvm2 right after that. So in
> case of a crash or something during a longer world update I still have an
> intact system. I'm not sure if it would boot with the old lvm2 and without
> device-mapper, probably yes, but I did not want to take any risk.
>
> Um, shouldn't the new portage have dealt auto-magically with this blocker?
>
> Wonko
>
Here's something more interesting, I don't need or use lvm. I was
trying to track it down with equery but I was getting drunk going in
circles.
I also assume that is why portage can't figure out a way to handle
this. It got drunk too. After a while a drunk just falls down. lol
Thought about using the -et options with emerge to figure this out.
Dale
:-) :-)
next prev parent reply other threads:[~2009-11-10 15:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 14:31 [gentoo-user] Problem with update world Massimiliano Ziccardi
2009-11-10 14:34 ` Alan McKinnon
2009-11-10 14:44 ` Massimiliano Ziccardi
2009-11-10 14:34 ` [gentoo-user] " Massimiliano Ziccardi
2009-11-10 14:37 ` [gentoo-user] " Dale
2009-11-10 15:11 ` Alex Schuster
2009-11-10 15:30 ` Dale [this message]
2009-11-10 16:06 ` Alex Schuster
2009-11-10 18:14 ` Dale
2009-11-10 20:39 ` Alan McKinnon
2009-11-10 20:49 ` Neil Bothwick
2009-11-10 21:08 ` Dale
2009-11-10 22:09 ` Joshua Murphy
2009-11-10 23:04 ` Dale
2009-11-10 22:13 ` John H. Moe
2009-11-10 16:55 ` Alan McKinnon
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=4AF98718.3040104@gmail.com \
--to=rdalek1967@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