From: Uwe Thiem <uwix@iway.na>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] No ebuild for kdeartwork-colorschemes ??
Date: Sun, 20 Jan 2008 14:18:15 +0200 [thread overview]
Message-ID: <200801201418.15378.uwix@iway.na> (raw)
In-Reply-To: <200801201359.16703.alan.mckinnon@gmail.com>
On 20 January 2008, Alan McKinnon wrote:
> Hi all,
>
> My portage-fu is apparently up the creek. Again.
>
> Trying to emerge kde-4.0.0, I get this:
>
> ==================
> nazgul ~ # emerge -av kde-meta
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies | *
> * ERROR: kde-base/kdeartwork-colorschemes-4.0.0 failed.
> * Call stack:
> * ebuild.sh, line 1666: Called
> source
> '/var/portage/kde-base/kdeartwork-colorschemes/kdeartwork-colorschemes-4.0.
>0.ebuild' * kdeartwork-colorschemes-4.0.0.ebuild, line 9: Called
> inherit 'kde4-meta'
> * ebuild.sh, line 1192: Called
> qa_source '/var/portage/local/layman/kde/eclass/kde4-meta.eclass'
> * ebuild.sh, line 36: Called
> source '/var/portage/local/layman/kde/eclass/kde4-meta.eclass'
> * kde4-meta.eclass, line 39: Called
> get-parent-package 'kde-base/kdeartwork-colorschemes'
> * kde4-functions.eclass, line 330: Called die
> * The specific snippet of code:
> * die "Package $target not found in KDE_DERIVATION_MAP, please
> report bug"
> * The die message:
> * Package not found in KDE_DERIVATION_MAP, please report bug
> *
> * If you need support, post the topmost build error, and the call stack
> if relevant.
> *
>
> emerge: there are no ebuilds to
> satisfy ">=kde-base/kdeartwork-colorschemes-4.0.0:kde-4".
> (dependency required by "kde-base/kdeartwork-meta-4.0.0" [ebuild])
> =================
>
> But the ebuild is there:
>
> =================
> nazgul portage # eix kdeartwork-colorschemes
> * kde-base/kdeartwork-colorschemes
> Available versions: (kde-4) {M}(~)4.0.0
> Homepage: http://www.kde.org/
> Description: KDE extra colorschemes
> =================
>
> And it's also keyworded and unmasked:
>
> =================
> nazgul portage # grep -r kdeartwork-colorschemes /etc/portage/*
> /etc/portage/package.keywords/kde4:kde-base/kdeartwork-colorschemes
> **
> /etc/portage/package.unmask/kde4:>=kde-base/kdeartwork-colorschemes-4.0.0
> =================
>
> I don't want to submit a bug as per the error just yet as I'm sure I'm
> doing something wrong on my end (as usual).
I just finished emerging KDE4 and are running revdep-rebuild now. I didn't get
that error. That's no consolation, I know, but I guess something must be
wrong on your side. Is the kdeartwork tarball actually in distfiles?
Uwe
--
If a man speaks in a forest, and no woman listens to him,
is he still lying?
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-20 12:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 11:59 [gentoo-user] No ebuild for kdeartwork-colorschemes ?? Alan McKinnon
2008-01-20 12:18 ` Uwe Thiem [this message]
2008-01-20 15:39 ` Alan McKinnon
2008-01-20 16:16 ` [gentoo-user] SOLVED " Alan McKinnon
2008-01-20 19:40 ` Uwe Thiem
2008-01-20 20:33 ` Alan McKinnon
2008-01-21 14:56 ` Eddie Mihalow Jr
2008-01-20 21:05 ` Neil Bothwick
2008-01-24 21:07 ` ionut cucu
2008-01-25 9:44 ` Neil Bothwick
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=200801201418.15378.uwix@iway.na \
--to=uwix@iway.na \
--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