Gentoo Archives: gentoo-user

From: kashani <kashani-list@××××××××.net>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: trying to track down broken dependency
Date: Tue, 22 Sep 2009 18:40:18
Message-Id: 4AB91A0F.1030507@badapple.net
In Reply to: [gentoo-user] Re: trying to track down broken dependency by Torsten Veller
1 Torsten Veller wrote:
2 > * kashani <kashani-list@××××××××.net>:
3 >> 3. Doctored up portage.mask to mask the errant virtuals
4 >>> =virtual/perl-Digest-SHA-5.47
5 >>> =virtual/perl-Test-Harness-3.17
6 >> Thought grumpy thoughts at developers who let packages into ~x86
7 >> with completely broken deps. Hard mask that crap next time.
8 >
9 > There are no broken deps and there is no crap that should be masked.
10 >
11
12 When building bugzilla-3.4.1-r1 which requires ~x86 I have to unmask a
13 number of perl modules. Two of those modules, listed above, attempt to
14 pull in perl-5.10.1 which isn't in portage. Hardmasking packages that
15 require dependencies that don't exist makes sense. If you'd like to
16 explain otherwise a little more data other than "cause I said so" is
17 required.
18
19 kashani
20
21 kashani@www01 /usr/portage/dev-lang/perl $ cat
22 /usr/portage/virtual/perl-Test-Harness/perl-Test-Harness-3.17.ebuild
23 # Copyright 1999-2009 Gentoo Foundation
24 # Distributed under the terms of the GNU General Public License v2
25 # $Header:
26 /var/cvsroot/gentoo-x86/virtual/perl-Test-Harness/perl-Test-Harness-3.17.ebuild,v
27 1.2 2009/08/25 10:56:52 tove Exp $
28
29 DESCRIPTION="Virtual for Test-Harness"
30 HOMEPAGE="http://www.gentoo.org/proj/en/perl/"
31 SRC_URI=""
32
33 LICENSE="GPL-2"
34 SLOT="0"
35 KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390
36 ~sh ~sparc ~sparc-fbsd ~x86 ~x86-fbsd"
37 IUSE=""
38
39 DEPEND=""
40 RDEPEND="|| ( ~dev-lang/perl-5.10.1 ~perl-core/Test-Harness-${PV} )"
41
42 kashani@www01 /usr/portage/dev-lang/perl $ ls
43 ChangeLog Manifest files metadata.xml perl-5.8.8-r5.ebuild
44 perl-5.8.8-r6.ebuild

Replies

Subject Author
[gentoo-user] Re: trying to track down broken dependency Torsten Veller <ml-en@××××××.net>