From: Daniel Gryniewicz <dang@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Masking / qt upgrade
Date: Fri, 10 Nov 2006 10:15:27 -0500 [thread overview]
Message-ID: <1163171727.9141.25.camel@athena.fprintf.net> (raw)
In-Reply-To: <29c147bd0611100316g5d11fe93uecb7063591a6bbd3@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
On Fri, 2006-11-10 at 12:16 +0100, Lorenzo Milesi wrote:
> Hi
>
> I know it must be a simple thing, but I couldn't get out of this.
> Yesterday I did a --sync to upgrade the system.
> When launching emerge I get the following error:
>
> !!! All ebuilds that could satisfy ">=sys-apps/dbus-0.93" have been masked.
> !!! One of the following masked packages is required to complete your request:
> - sys-apps/dbus-0.95 (masked by: package.mask)
> # Steev Klimaszewski <steev@gentoo.org> (18 Aug 2006)
> # waiting for new mono bindings and some testing
>
> - sys-apps/dbus-0.94 (masked by: package.mask)
>
> For more information, see MASKED PACKAGES section in the emerge man page or
> refer to the Gentoo Handbook.
> (dependency required by "x11-libs/qt-4.2.1-r1" [ebuild])
>
> And that's ok. So, in order to upgrade anyway I'm going to mask
> qt-4.2.1-r1 by adding
> =x11-libs/qt-4.2.1-r1
> in my package.mask. Right? Sadly emerge is still blocking because of
> the same exact error.
> What did I do wrong?
>
Typically, that means you have qt unmasked. The unmask trump the mask,
always. You need to modify your unmask to have >=11-libs/qt-4.2.1 or
something similar, or unmask dbus.
Daniel
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2006-11-10 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 11:16 [gentoo-amd64] Masking / qt upgrade Lorenzo Milesi
2006-11-10 11:48 ` Neil Bothwick
2006-11-10 12:31 ` Lorenzo Milesi
2006-11-10 12:45 ` Bo Ørsted Andresen
2006-11-10 15:25 ` Lorenzo Milesi
2006-11-10 15:15 ` Daniel Gryniewicz [this message]
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=1163171727.9141.25.camel@athena.fprintf.net \
--to=dang@gentoo.org \
--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