This is a bit problematic as, with that block, a user having Gnome and MATE installed will need to choose between having bluetooth support in one or the other (as latest MATE relies on blueman). I remember the file collision was fixed long time ago (I think for 2.0 versions), then, I am unsure about why the block is still there. I have taken a look to Fedora, for example, and it seems that both can collide Thanks
The original file collision was fixed a long time ago. Let me know what is the reason for the blocker and I'll see what we (blueman project) can do about resolving it.
I have no clue either but since it's a weak block, I suppose it was just the file collision.
I see that I dropped it 5 years ago https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=932447c160072a0e793425751255b57488edd8af But it was introduced again on a version bump: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=95b2396a74ab07c164b0f3a4fb35498923c84a62 But I don't see why, maybe it was because of me fixing it on 2.0, but maybe forgetting in 9999 and later 2.1.x getting based on 9999... I don't remember, but it would possible :/
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=37999af984f9b8ca1b74e5b1e007c30a997d2e97 commit 37999af984f9b8ca1b74e5b1e007c30a997d2e97 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-05-03 07:19:14 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-05-03 10:24:15 +0000 net-wireless/blueman: Remove gnome-bluetooth blocker Closes: https://bugs.gentoo.org/720718 Signed-off-by: Michał Górny <mgorny@gentoo.org> net-wireless/blueman/blueman-2.1.2.ebuild | 1 - net-wireless/blueman/blueman-9999.ebuild | 1 - 2 files changed, 2 deletions(-)
Thanks Michał
