From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 829B4139083 for ; Sat, 9 Dec 2017 14:08:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DD216E1027; Sat, 9 Dec 2017 14:08:18 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 76D33E100F for ; Sat, 9 Dec 2017 14:08:18 +0000 (UTC) Received: from [192.168.2.51] (85.253.86.194.cable.starman.ee [85.253.86.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: leio) by smtp.gentoo.org (Postfix) with ESMTPSA id B17A733C6B6 for ; Sat, 9 Dec 2017 14:08:15 +0000 (UTC) Message-ID: <1512828491.3369.4.camel@gentoo.org> Subject: Re: [gentoo-user] net-wireless/blueman-2.1_alpha2 blocked by net-wireless/gnome-bluetooth - is it necessary? From: Mart Raudsepp To: gentoo-user@lists.gentoo.org Date: Sat, 09 Dec 2017 16:08:11 +0200 In-Reply-To: <2626282.TuXHzJEg2m@note> References: <0951308c-02e4-b5f1-24a4-cc83fd6d90d6@ya.ru> <2626282.TuXHzJEg2m@note> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.3 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archives-Salt: 4d71ea71-2af0-488d-964e-6e4b2d973f87 X-Archives-Hash: a0deccfab686b49abfd79241288d5458 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 same  > install paths). > > Although, I can't guarantee that it was the case here. There was a blocker in blueman against gnome-bluetooth due to a file collision with gnome-bluetooth. This was removed with 2.0-r1, back in Oct 2015, as blueman upstream solved it. To me it looks like the change didn't make it to the live ebuild and then eventually sometime after 2.0.3 a bump was made via copying from 9999, not the latest version, thus reinstating the blocker, possibly by accident. Or maybe on purpose, but I don't see an explanation for it in logs. Try to remove the blocker in blueman, see if files collide or not, and if not file a bug against blueman, possibly with info that it might have been accidental reintroduction due to..., etc. > I've noticed that Gnome Team makes some decisions, that doesn't looks > logical  > for a few times already. Something not looking logical for you doesn't mean there isn't sound logic. In this case, it's not us who have a blocker possibly wrongly reintroduced here. Best, Mart Raudsepp Gentoo GNOME team lead