public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] autounmask not doing to well
Date: Thu, 16 Sep 2010 21:58:26 -0500	[thread overview]
Message-ID: <4C92D952.2070807@gmail.com> (raw)

Hi folks,

The latest KDE 4.5.1 has hit the tree.  It made it there a few days 
ago.  Yeppie!!  It is masked but I wanted to try to install it again.  
The last time was a mess to say it lightly.  I use autounmask to unmask 
it.  I use this command:

autounmask kde-base/kde-meta-4.5.1

I don't use the -n option but it doesn't seem to matter even if I do.  
I'm on portage-2.2_rc67 and autounmask-0.27 which is the only version I 
see in the tree.  After I run autounmask and then do a emerge -uvDNa 
world, I get this:

root@smoker / # emerge -uvDNa world

These are the packages that would be merged, in order:

Calculating dependencies... done!

emerge: there are no ebuilds to satisfy 
">=kde-base/kdelibs-9999[-kdeprefix,-aqua]".
(dependency required by "kde-base/liboxygenstyle-9999" [installed])
(dependency required by "kde-base/kdebase-meta-4.5.1" [ebuild])
(dependency required by "kde-base/kde-meta-4.5.1" [ebuild])
(dependency required by "@world" [argument])

root@smoker / #

If I add that kdelibs package to the unmask file, it just goes to the 
nest blocker and this continues until I get the idea something is not 
working right.  So, is autounmask not working right?  Am I not doing 
something right?  Am I missing something?

Oh, I don't currently have any overlays on here.  I waited until it hit 
the tree and had a couple days to settle down.

Thanks for any insight on this.

Dale

:-)  :-)



             reply	other threads:[~2010-09-17  2:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-17  2:58 Dale [this message]
2010-09-17  5:38 ` [gentoo-user] autounmask not doing to well Alan McKinnon
2010-09-17 14:28 ` Paul Hartman
2010-09-17 18:11   ` Dale

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=4C92D952.2070807@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