From: Torsten Veller <ml-en@veller.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: trying to track down broken dependency
Date: Tue, 22 Sep 2009 22:20:57 +0200 [thread overview]
Message-ID: <20090922202057.GA24449@veller.net> (raw)
In-Reply-To: <4AB91A0F.1030507@badapple.net>
* kashani <kashani-list@badapple.net>:
> When building bugzilla-3.4.1-r1 which requires ~x86 I have to
> unmask a number of perl modules. Two of those modules, listed above,
> attempt to pull in perl-5.10.1 which isn't in portage. Hardmasking
> packages that require dependencies that don't exist makes sense. If
> you'd like to explain otherwise a little more data other than "cause
> I said so" is required.
Let's have a look at the ebuild:
> kashani@www01 /usr/portage/dev-lang/perl $ cat
> /usr/portage/virtual/perl-Test-Harness/perl-Test-Harness-3.17.ebuild
> # Copyright 1999-2009 Gentoo Foundation
> # Distributed under the terms of the GNU General Public License v2
> # $Header: /var/cvsroot/gentoo-x86/virtual/perl-Test-Harness/perl-Test-Harness-3.17.ebuild,v
> 1.2 2009/08/25 10:56:52 tove Exp $
>
> DESCRIPTION="Virtual for Test-Harness"
> HOMEPAGE="http://www.gentoo.org/proj/en/perl/"
> SRC_URI=""
>
> LICENSE="GPL-2"
> SLOT="0"
> KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64
> ~s390 ~sh ~sparc ~sparc-fbsd ~x86 ~x86-fbsd"
> IUSE=""
>
> DEPEND=""
> RDEPEND="|| ( ~dev-lang/perl-5.10.1 ~perl-core/Test-Harness-${PV} )"
The ebuild depends on dev-lang/perl-5.10.1 or perl-core/Test-Harness-3.17.
The second one is in the tree so there is no need for hardmasking.
So if you add virtual/perl-Test-Harness to package.keywords you should
also add perl-core/Test-Harness.
If you wonder why portage doesn't report both possibilities, visit the
bugs in my other mail in this thread.
Thanks
prev parent reply other threads:[~2009-09-22 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 22:40 [gentoo-user] trying to track down broken dependency kashani
2009-09-18 22:49 ` Paul Hartman
2009-09-18 22:51 ` Paul Hartman
2009-09-19 1:49 ` kashani
2009-09-19 16:38 ` Michael Higgins
2009-09-19 17:45 ` Volker Armin Hemmann
2009-09-19 18:24 ` [gentoo-user] " Torsten Veller
2009-09-19 18:58 ` [gentoo-user] " kashani
2009-09-19 23:18 ` [gentoo-user] " Torsten Veller
2009-09-22 18:40 ` kashani
2009-09-22 20:20 ` Torsten Veller [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=20090922202057.GA24449@veller.net \
--to=ml-en@veller.net \
--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