| 1 |
Except that fact that I didn't unmasked it. |
| 2 |
> # fgrep -rni blueman /etc/portage |
| 3 |
> /etc/portage/package.use/blueman:1:#net-wireless/blueman |
| 4 |
But I understand other possible reasons. |
| 5 |
|
| 6 |
On 12/08/2017 07:37 PM, Alan McKinnon wrote: |
| 7 |
> On 08/12/2017 15:22, Alexey Eschenko wrote: |
| 8 |
>> It can be the issue. But older version (2.0.4) which is currently |
| 9 |
>> installed works fine and has no conflicts. |
| 10 |
>> |
| 11 |
>> It's quite strange. |
| 12 |
>> |
| 13 |
>> |
| 14 |
>> On 12/08/2017 03:39 PM, Vadim A. Misbakh-Soloviov wrote: |
| 15 |
>>>> Is it really necessary to block one package when another installed? |
| 16 |
>>> Most of the time, the reason to make packages to block each other is |
| 17 |
>>> collisions (if they they contain files (like binaries or libraries) |
| 18 |
>>> with same |
| 19 |
>>> install paths). |
| 20 |
>>> |
| 21 |
>>> Although, I can't guarantee that it was the case here. |
| 22 |
>>> |
| 23 |
>>> I've noticed that Gnome Team makes some decisions, that doesn't looks |
| 24 |
>>> logical |
| 25 |
>>> for a few times already. |
| 26 |
>>> |
| 27 |
> |
| 28 |
> It's not at all strange; it's quite ordinary actually. |
| 29 |
> |
| 30 |
> Keeping in mind that I do not use these packages, or gnome, look at the |
| 31 |
> available blueman packages: |
| 32 |
> |
| 33 |
> # eix net-wireless/blueman |
| 34 |
> * net-wireless/blueman |
| 35 |
> Available versions: (~)2.0.3 (~)2.0.4 [M](~)2.1_alpha1 **9999 |
| 36 |
> {appindicator network nls policykit pulseaudio thunar |
| 37 |
> PYTHON_SINGLE_TARGET="python2_7 python3_4 python3_5 python3_6" |
| 38 |
> PYTHON_TARGETS="python2_7 python3_4 python3_5 python3_6"} |
| 39 |
> |
| 40 |
> 2.1 is still in an alpha state, and it is p.masked: |
| 41 |
> |
| 42 |
> /var/portage/profiles/package.mask: |
| 43 |
> # Michał Górny <mgorny@g.o> (26 Jan 2017) |
| 44 |
> # Pre-release, masked for testing. Major changes since 2.0.4, |
| 45 |
> # including dropped support for BlueZ 4. |
| 46 |
> |
| 47 |
> It is not unreasonable to conclude that blueman-2.1 intends to add |
| 48 |
> features that conflict with gnome-bluetooth and they can't co-exist. As |
| 49 |
> Vadim said, file collisions are often the underlying cause. |
| 50 |
> |
| 51 |
> You unmasked an alpha package, clearly tagged as "for testing". Nothing |
| 52 |
> add abut the result you got at all. |
| 53 |
> |
| 54 |
> |
| 55 |
> |
| 56 |
|
| 57 |
-- |
| 58 |
Kind regards, |
| 59 |
Alexey Eschenko |
| 60 |
https://skobk.in/ |
Archives