public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexey Eschenko <skobkin-ru@ya.ru>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] net-wireless/blueman-2.1_alpha2 blocked by net-wireless/gnome-bluetooth - is it necessary?
Date: Sat, 9 Dec 2017 03:47:51 +0300	[thread overview]
Message-ID: <7e962a44-83d8-8e64-9bc8-f848dbf84e28@ya.ru> (raw)
In-Reply-To: <9ca93a20-ef3d-e9d3-b805-8f8ca9343ac0@gmail.com>

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 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 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 noticed that Gnome Team makes some decisions, that doesn't looks
>>> logical
>>> for a few times already.
>>>
>
> It's not at all strange; it's quite ordinary actually.
>
> Keeping in mind that I do not use these packages, or gnome, look at the
> available blueman packages:
>
> # eix net-wireless/blueman
> * net-wireless/blueman
>       Available versions:  (~)2.0.3 (~)2.0.4 [M](~)2.1_alpha1 **9999
> {appindicator network nls policykit pulseaudio thunar
> PYTHON_SINGLE_TARGET="python2_7 python3_4 python3_5 python3_6"
> PYTHON_TARGETS="python2_7 python3_4 python3_5 python3_6"}
>
> 2.1 is still in an alpha state, and it is p.masked:
>
> /var/portage/profiles/package.mask:
> # Michał Górny <mgorny@gentoo.org> (26 Jan 2017)
> # Pre-release, masked for testing. Major changes since 2.0.4,
> # including dropped support for BlueZ 4.
>
> It is not unreasonable to conclude that blueman-2.1 intends to add
> features that conflict with gnome-bluetooth and they can't co-exist. As
> Vadim said, file collisions are often the underlying cause.
>
> You unmasked an alpha package, clearly tagged as "for testing". Nothing
> add abut the result you got at all.
>
>
>

-- 
Kind regards,
Alexey Eschenko
https://skobk.in/



  reply	other threads:[~2017-12-09  0:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08 12:27 [gentoo-user] net-wireless/blueman-2.1_alpha2 blocked by net-wireless/gnome-bluetooth - is it necessary? Alexey Eschenko
2017-12-08 12:39 ` Vadim A. Misbakh-Soloviov
2017-12-08 13:22   ` Alexey Eschenko
2017-12-08 16:37     ` Alan McKinnon
2017-12-09  0:47       ` Alexey Eschenko [this message]
2017-12-09  8:44         ` Alan McKinnon
2017-12-09 14:08   ` Mart Raudsepp
2017-12-10 23:14     ` Alexey Eschenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7e962a44-83d8-8e64-9bc8-f848dbf84e28@ya.ru \
    --to=skobkin-ru@ya.ru \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox