From: "Andrey Vul" <andrey.vul@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2
Date: Wed, 29 Oct 2008 13:14:34 -0400 [thread overview]
Message-ID: <e38d12ff0810291014u13f7d8cbr928b143130e2d048@mail.gmail.com> (raw)
In-Reply-To: <a964044f0810291003l7d179a58rc6e9cd38f96f8bba@mail.gmail.com>
On Wed, Oct 29, 2008 at 1:03 PM, Rafael Barrera Oro <borafael@gmail.com> wrote:
> Thank you both for your responses, i will try dealing with QT first and then
> emerge udev separately, without any mercilless barbaric
> running-around-barely-dressed-waving-an-axe-around unmerging.
It'll be faster do do udev first. Get it done and over with.
Qt will take 2+ hours to compile.
> I'm gonna miss the sledgehammer though...
I sledgehammer my way through blocks and no problems here :D
> Seroiusly, thanks very much for your help
>
> PD: As soon as i get it done i will tell how the outcome was
>
> 2008/10/29 Alan McKinnon <alan.mckinnon@gmail.com>
>>
>> On Wednesday 29 October 2008 18:41:47 Andrey Vul wrote:
>> > > [blocks B ] <sys-fs/udev-114 ("<sys-fs/udev-114" is blocking
>> > > media-gfx/sane-backends-1.0.19-r2, media-libs/libgphoto2-2.4.2)
>> > >
>> > > My usual solution for problems of this kind is to mercilessly unmerge
>> > > any
>> > > packages that stand in my way, but, considering we are talking about
>> > > packages like qt and udev, i must admit i do not dare to follow my
>> > > usual
>> > > strategy.
>>
>> Instead of unmerging stuff without mercy, taking a sledgehammer to the
>> problem
>> and generally acting like a Windows user, I recommend you read the output
>> and
>> understand what is going on.
>>
>> It clearly says that your *current* version of udev which is less than 114
>> is
>> blocking sane-backends and libgphoto. So, merge udev separately:
>>
>> emerge -av1 udev
I prefer emerge -1pv udev
<look at output>
emerge -1 udev
>> there's no need for udev to go in world, it's already in system. Then
>> emerge
>> world and it will probably work (after you deal with qt that is, but
>> another
>> poster told you how to do that)
--
Andrey Vul
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
next prev parent reply other threads:[~2008-10-29 17:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 16:33 [gentoo-user] Trying to solve blockage when trying to install kde-meta-4.1.2 Rafael Barrera Oro
2008-10-29 16:41 ` Andrey Vul
2008-10-29 16:56 ` Alan McKinnon
2008-10-29 17:03 ` Rafael Barrera Oro
2008-10-29 17:14 ` Andrey Vul [this message]
2008-10-29 20:46 ` Neil Bothwick
2008-10-29 21:52 ` Alan McKinnon
2008-10-29 22:13 ` Neil Bothwick
2008-10-29 23:26 ` Andrey Vul
2008-10-30 1:44 ` Joshua Murphy
2008-10-30 2:23 ` Andrey Vul
2008-10-30 22:55 ` Joshua Murphy
2008-10-29 19:59 ` Alan McKinnon
2008-10-30 10:39 ` Peter Humphrey
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=e38d12ff0810291014u13f7d8cbr928b143130e2d048@mail.gmail.com \
--to=andrey.vul@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