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