* Messages for package net-wireless/blueman-1.23_p20140717-r1: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). See * http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to * solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /usr/share/icons/hicolor/48x48/status/bluetooth-disabled.png * /usr/share/icons/hicolor/48x48/status/bluetooth-active.png * /usr/share/icons/hicolor/32x32/status/bluetooth-disabled.png * /usr/share/icons/hicolor/32x32/status/bluetooth-active.png * /usr/share/icons/hicolor/24x24/status/bluetooth-disabled.png * /usr/share/icons/hicolor/24x24/status/bluetooth-active.png * /usr/share/icons/hicolor/22x22/status/bluetooth-disabled.png * /usr/share/icons/hicolor/22x22/status/bluetooth-active.png * /usr/share/icons/hicolor/16x16/status/bluetooth-disabled.png * /usr/share/icons/hicolor/16x16/status/bluetooth-active.png * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * net-wireless/gnome-bluetooth-3.12.0:2::gentoo * /usr/share/icons/hicolor/16x16/status/bluetooth-active.png * /usr/share/icons/hicolor/16x16/status/bluetooth-disabled.png * /usr/share/icons/hicolor/22x22/status/bluetooth-active.png * /usr/share/icons/hicolor/22x22/status/bluetooth-disabled.png * /usr/share/icons/hicolor/24x24/status/bluetooth-active.png * /usr/share/icons/hicolor/24x24/status/bluetooth-disabled.png * /usr/share/icons/hicolor/32x32/status/bluetooth-active.png * /usr/share/icons/hicolor/32x32/status/bluetooth-disabled.png * /usr/share/icons/hicolor/48x48/status/bluetooth-active.png * /usr/share/icons/hicolor/48x48/status/bluetooth-disabled.png * * Package 'net-wireless/blueman-1.23_p20140717-r1' NOT merged due to * file collisions. If necessary, refer to your elog messages for the * whole content of the above message. * * The following package has failed to build or install: * * (net-wireless/blueman-1.23_p20140717-r1:0/0::gentoo, ebuild scheduled for merge), Log file: * '/var/tmp/portage/net-wireless/blueman-1.23_p20140717-r1/temp/build.log' Reproducible: Always Steps to Reproduce: 1. emerge -av1 \=net-wireless/gnome-bluetooth-3.12.0 (or any program that needs this package) 2. emerge -av1 \=net-wireless/blueman-1.23_p20140717-r1 Actual Results: Package failed to install Expected Results: Get the package installed
Created attachment 382196 [details] emerge --info
Created attachment 382198 [details] build.log
I don't want this to sit around for too long, anyone see a reason why a bi-directional blocker would be an issue? If gnome team wants to add the blockers they have my blessing, if no one complains I'll go ahead in a few hours. I can't see a major need to have two widgets fighting over my bluetooth.
Seeing the only blockers are icons I would at also try to report to blueman upstream to see if they can rename the icons or something :/
(In reply to Rick Farina (Zero_Chaos) from comment #3) > I don't want this to sit around for too long, anyone see a reason why a > bi-directional blocker would be an issue? > > If gnome team wants to add the blockers they have my blessing, if no one > complains I'll go ahead in a few hours. I can't see a major need to have > two widgets fighting over my bluetooth. The situation is complicated by the fact that gnome-bluetooth is just have a partial sendto funtctionality (via this applet we can send files to devices), while blueman is full-featured bluetooth applet. Because of this making mutual blocking is the wrong way (IMHO). In its turn gnome-bluetooth is needed by widly-used nm-applet (NetworkManager) for "sendto" funtctionality. So situation with both package installed is quite common.
adding a temp blocker to blueman to prevent this for now. hopefully upstream will rename and I'll just make a new snapshot.
@Zero_Chaos, You can now remove the blocker, because the icons issue was just fixed in GIT, and the live ebuild works ok. You may look at my report and the resolution here: https://github.com/blueman-project/blueman/pull/77#event-150846742 (and of course your original issue https://github.com/blueman-project/blueman/issues/82) The =net-wireless/blueman-9999 version also needs removal of the blocker towards gnome-bluetooth BTW I can confirm the GIT version works ok with bluez5, and the upstream work hard on fixing things, so I do not see a reason this to be removed from portage as proposed in bug #501718 And just one note about the versioning of the ebuild... the GIT code is actually a Blueman2 code, so the =net-wireless/blueman-1.23_p20140717-r1 is not quite exact....
(In reply to PhobosK from comment #7) > And just one note about the versioning of the ebuild... the GIT code is > actually a Blueman2 code, so the =net-wireless/blueman-1.23_p20140717-r1 is > not quite exact.... The version tag in git is still 1.23 in the about box. I'll update it when upstream does.
(In reply to Rick Farina (Zero_Chaos) from comment #8) > (In reply to PhobosK from comment #7) > > > And just one note about the versioning of the ebuild... the GIT code is > > actually a Blueman2 code, so the =net-wireless/blueman-1.23_p20140717-r1 is > > not quite exact.... > > The version tag in git is still 1.23 in the about box. I'll update it when > upstream does. Hey all, not sure who is tracking this bug, but we fixed this upstream a few commits ago.
