Hi. Thank you for your attention. Try to remove the blocker in blueman, see if files collide or notHow can I remove the blocker in blueman? AFAIK it's not like adding package constraint to the package.unmask or something like that. I have no experience with writing ebuilds though.But I can check
On R, 2017-12-08 at 19:39 +0700, Vadim A. Misbakh-Soloviov wrote:
> >
> > Is it really necessary to block one package when another installed?
>
> Most of the time, the reason to make packages to block each other is
> collisions (if they they contain files (like binaries or libraries)
> with
On 09/12/2017 02:47, Alexey Eschenko wrote:
> Except that fact that I didn't unmasked it.
You must have had a tree checkout slightly newer than mine. I just
synced here and see that the mask has now been removed.
It's quite unusual to unmask an alpha version, maybe raise it on b.g.o ?
For the
Except that fact that I didn't unmasked it.
# fgrep -rni blueman /etc/portage
/etc/portage/package.use/blueman:1:#net-wireless/blueman
But I understand other possible reasons.
On 12/08/2017 07:37 PM, Alan McKinnon wrote:
On 08/12/2017 15:22, Alexey Eschenko wrote:
It can be the issue. But
On 08/12/2017 15:22, Alexey Eschenko wrote:
> It can be the issue. But older version (2.0.4) which is currently
> installed works fine and has no conflicts.
>
> It's quite strange.
>
>
> On 12/08/2017 03:39 PM, Vadim A. Misbakh-Soloviov wrote:
>>> Is it really necessary to block one package
It can be the issue. But older version (2.0.4) which is currently
installed works fine and has no conflicts.
It's quite strange.
On 12/08/2017 03:39 PM, Vadim A. Misbakh-Soloviov wrote:
Is it really necessary to block one package when another installed?
Most of the time, the reason to make
> Is it really necessary to block one package when another installed?
Most of the time, the reason to make packages to block each other is
collisions (if they they contain files (like binaries or libraries) with same
install paths).
Although, I can't guarantee that it was the case here.
I've
After last portage package tree update I've got this conflict:
[ebuild U ] net-wireless/blueman-2.1_alpha2 [2.0.4] USE="nls
policykit pulseaudio -appindicator -network (-thunar%)"
PYTHON_SINGLE_TARGET="python3_4 -python3_5 -python3_6% (-python2_7%)"
PYTHON_TARGETS="python3_4 python3_5
8 matches
Mail list logo
