1 |
Hi List! |
2 |
|
3 |
I'm having a little problem with package masking that I just can't seem |
4 |
to wrap my head around. See, I emerged the Gaim 2 beta by unmasking it |
5 |
through /etc/portage/package.keywords, and all went fine, until |
6 |
gaim-2.0.0_beta5-r3 came along, which requires a ~x86 dbus, which I |
7 |
don't want (for a variety of obvious reasons). So I thought to continue |
8 |
running with gaim-2.0.0_beta5-r2, which is still in portage. |
9 |
|
10 |
In order to keep `emerge -Duva world' working, I wanted to mask |
11 |
gaim-2.0.0_beta5-r3, though, but there's where my problem is. I've added |
12 |
`>net-im/gaim-2.0.0_beta5-r3' to /etc/portage/package.mask, but nothing |
13 |
changes. `emerge gaim' still wishes to emerge gaim-2.0.0_beta5-r3, and |
14 |
`emerge -Duva world' fails since it cannot build a depgraph including |
15 |
gaim-2.0.0_beta5-r3. I've never had any problems |
16 |
with /etc/portage/package.mask in the past -- even now, it's working to |
17 |
mask >=net-fs/nfs-utils-1.0.8. |
18 |
|
19 |
Does anyone have any idea why it has no effect on gaim? I thought it |
20 |
might be confused by gaim's version numbers or something, but still it |
21 |
seems to be able to see that gaim-2.0.0_beta5-r3 is newer than |
22 |
gaim-2.0.0_beta5-r2, so that can't be it, right? |
23 |
|
24 |
Fredrik Tolf |
25 |
|
26 |
|
27 |
-- |
28 |
gentoo-user@g.o mailing list |