On Sunday 29 June 2008, b.n. wrote:
By the way: I find the fact emerge -pv just fails in those cases
extremly annoying. Shoudn't it report the error, skip offending
packages but let me see what can be happily merged independently of
that?
Seems a reasonable question, but will be almost
On Mon, Jun 30, 2008 at 5:57 PM, Alan McKinnon [EMAIL PROTECTED] wrote:
On Sunday 29 June 2008, b.n. wrote:
By the way: I find the fact emerge -pv just fails in those cases
extremly annoying. Shoudn't it report the error, skip offending
packages but let me see what can be happily merged
On Monday 30 June 2008, brullo nulla wrote:
Seems a reasonable question, but will be almost impossible to
implement, as how would you define a package that can be happily
merged independently of a blocking package?
portage is software, it isn't intelligent so it doesn't know how to
Alan McKinnon ha scritto:
On Monday 30 June 2008, brullo nulla wrote:
The block will in many cases affect only a branch of the dependency
tree. For example, in this case it is all blocked because glibmm
wants a masked glib. Portage knows that glibmm wants the masked glib,
so it knows that
Hi,
It is probably a dumb blunder of mine, but it seems that there is
something weird with glib on my world file.
emerge -pv world fails with:
---
!!! All ebuilds that could satisfy =dev-libs/glib-2.16 have been masked.
!!! One of the following masked packages is required to complete your
On Sun, 29 Jun 2008 20:39:21 +0200, b.n. wrote:
emerge -pv world fails with:
---
!!! All ebuilds that could satisfy =dev-libs/glib-2.16 have been
masked. !!! One of the following masked packages is required to
complete your request:
- dev-libs/glib-2.16.3 (masked by: package.mask)
Neil Bothwick ha scritto:
!!! All ebuilds that could satisfy =dev-libs/glib-2.16 have been
masked. !!! One of the following masked packages is required to
complete your request:
- dev-libs/glib-2.16.3 (masked by: package.mask)
/usr/portage/local/layman/desktop-effects/profiles/package.mask:
#
#
On Sun, 29 Jun 2008 22:45:20 +0200
b.n. [EMAIL PROTECTED] wrote:
Neil Bothwick ha scritto:
!!! All ebuilds that could satisfy =dev-libs/glib-2.16 have been
masked. !!! One of the following masked packages is required to
complete your request:
- dev-libs/glib-2.16.3 (masked by:
On Sun, 29 Jun 2008 22:45:20 +0200, b.n. wrote:
- dev-libs/glib-2.16.3 (masked by: package.mask)
/usr/portage/local/layman/desktop-effects/profiles/package.mask:
#
# [EMAIL PROTECTED] (9 February 2008)
# glib-2.15 breaks some packages
- dev-libs/glib-2.16.2 (masked by: package.mask,
Neil Bothwick ha scritto:
On Sun, 29 Jun 2008 22:45:20 +0200, b.n. wrote:
- dev-libs/glib-2.16.3 (masked by: package.mask)
/usr/portage/local/layman/desktop-effects/profiles/package.mask:
#
# [EMAIL PROTECTED] (9 February 2008)
# glib-2.15 breaks some packages
- dev-libs/glib-2.16.2 (masked
On Mon, 30 Jun 2008 00:04:20 +0200, b.n. wrote:
This is masked in a profile from the desktop-effects overlay. It's
nothing to do with the official portage tree, but a third-party
overlay breaking things for you.
Now, what should I do? Ask to the desktop-effects guys?
Seems a reasonable
Neil Bothwick ha scritto:
And *why* does
an overlay mask things from the *main* portage tree? Is this normal?
Because masking is global, the sum of all the package.mask files is
applied to the system as a whole.
Yes, I know.
What I wondered, is if this is normal policy. It seems that an
12 matches
Mail list logo
