Gentoo Archives: gentoo-dev

From: Ben Lutgens <blutgens@×××××××.com>
To: gentoo-dev@××××××××××.org
Subject: Re: [gentoo-dev] Problem with tcl-tk ebuild
Date: Wed, 13 Jun 2001 09:26:47
Message-Id: 20010613102617.A1600@minime.sistina.com
In Reply to: Re: [gentoo-dev] Problem with tcl-tk ebuild by Ben Lutgens
1 On Wed, Jun 13, 2001 at 10:02:04AM -0500, Ben Lutgens wrote:
2 >On Wed, Jun 13, 2001 at 03:42:27PM +0200, Asbjørn Sannes wrote:
3 >>
4 >>I tried to emerge wine getting the error:
5 >
6 >edit /usr/lib/python2.0/portage.py
7
8 I just updated portage-1.5.1-r1 with the fix to the problem you're
9 seeing, please wait about a half hour and then run "emerge rsync" and
10 then emerge the latest portage.
11
12 >
13 >scroll down till you see the categories array and add in "dev-tcltk",
14 >then you should be able to emerge it. Be sure to make a backup copy of
15 >that file incase you fubar it.
16 >
17 >I'll probably add this to portage today.
18 >
19 >>
20 >>!!! Error: couldn't find match for >=dev-tcltk/itcl-3.2
21 >>
22 >>I then tried to emerge dev-tcltk/itcl-3.2 manually and got an error here
23 >>aswell:
24 >>
25 >>!!! ebuild dev-tcltk/itcl-3.2 not found (possibly blocked by package.mask)
26 >>
27 >>Now I checked /usr/portage/profiles/packages.mask, but could not find any
28 >>trace of it in there. So I'm guessing there is an error in the ebuild file
29 >>for itcl-3.2. What Hallski said anyways.. (come to #gentoo on
30 >>irc.openprojects.net).
31 >>
32 >>--
33 >>Asbjorn Sannes
34 >>ace@××××××.org
35 >>
36 >>
37 >>
38 >>_______________________________________________
39 >>gentoo-dev mailing list
40 >>gentoo-dev@××××××××××.org
41 >>http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
42 >
43 >--
44 >Ben Lutgens
45 >Sistina Software Inc.
46 >Kernel panic: I have no root and I want to scream
47
48
49
50 --
51 Ben Lutgens
52 Sistina Software Inc.
53 Kernel panic: I have no root and I want to scream

Replies

Subject Author
[gentoo-dev] portage-1.5.1-r1 doesn't work proberly .. at least on my system Holger Brueckner <lists@××××××××.de>