| 1 |
Hi, |
| 2 |
|
| 3 |
It is probably a dumb blunder of mine, but it seems that there is |
| 4 |
something weird with glib on my world file. |
| 5 |
|
| 6 |
emerge -pv world fails with: |
| 7 |
|
| 8 |
--- |
| 9 |
|
| 10 |
!!! All ebuilds that could satisfy ">=dev-libs/glib-2.16" have been masked. |
| 11 |
!!! One of the following masked packages is required to complete your |
| 12 |
request: |
| 13 |
- dev-libs/glib-2.16.3 (masked by: package.mask) |
| 14 |
/usr/portage/local/layman/desktop-effects/profiles/package.mask: |
| 15 |
# |
| 16 |
# <jmbsviceto@g.o> (9 February 2008) |
| 17 |
# glib-2.15 breaks some packages |
| 18 |
|
| 19 |
- dev-libs/glib-2.16.2 (masked by: package.mask, ~x86 keyword) |
| 20 |
- dev-libs/glib-2.16.1 (masked by: package.mask, ~x86 keyword) |
| 21 |
|
| 22 |
For more information, see MASKED PACKAGES section in the emerge man page or |
| 23 |
refer to the Gentoo Handbook. |
| 24 |
(dependency required by "dev-cpp/glibmm-2.16.1" [ebuild]) |
| 25 |
|
| 26 |
--- |
| 27 |
|
| 28 |
Now, I have a bunch of unmasked stuff in package.keywords, but I've |
| 29 |
*not* unmasked glibmm ~x86 or other glib related stuff. So why is a x86 |
| 30 |
glibmm pulling down ~x86 stuff/why is an unstable glibmm being pulled |
| 31 |
down? By what? |
| 32 |
|
| 33 |
By the way: I find the fact "emerge -pv" just fails in those cases |
| 34 |
extremly annoying. Shoudn't it report the error, skip offending packages |
| 35 |
but let me see what can be happily merged independently of that? |
| 36 |
|
| 37 |
m. |
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-user@l.g.o mailing list |
Archives