On Thu, Jan 14, 2010 at 08:26:15PM +0100, Andrea Veri wrote: > The old obexd maintainer did a transition between obexd-server and > obex-data-server thinking that they bot ship the same D-Bus API but this is > not right. They are different packages and as far as I know no package is > currently using obexd-server to work at the moment. (e.g no GNOME package > does yet)
As stated in the changelog, the conflict is because obexd and obex-data-server both register as services on org.openobex dbus name, and this still stands AFAICT. > The great problem is that obexd-server conflicts with obex-data-server which > means that quite all the devices that should use obex-data-server (like many > functionalities of gnome-bluetooth and more) are now completely unusable. which interface gnome-bluetooth uses? obexd or ods? it should properly depend on one of those of course. Also note that obexd has been splitted into client and server exactly to not make g-b directly conflict with ods. (IOW, g-b depends on obexd-client but recommends obexd-server which in turn conflicts with ods) > This bug needs to be fixed ASAP, I'm CCing Joss so that we can help out > fixing this issue. If you don't have enough time for this we will try to > think about a working solution and then upload a fixed package. I have no interest (nor time) right now, feel free to adopt/NMU. filippo -- Filippo Giunchedi - http://esaurito.net - 0x6B79D401 If only God would give me some clear sign! Like making a large deposit in my name in a Swiss bank. -- Woody Allen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
