[Pkg-bluetooth-maintainers] Bug#565318: Bug#565318: Bug#565318: obexd-server thought as the new implementation of the old obex-data-server

Nobuhiro Iwamatsu iwamatsu at nigauri.org
Fri Jan 22 00:16:52 UTC 2010


Hi , all.

2010/1/15 Andrea Veri <and at debian.org>:
> On Fri, 15 Jan 2010, Filippo Giunchedi wrote:
>
>> 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.
>
> yes, and that's why the conflict will stay where it is.
>
>
>> > 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)
>
> g-bluetooth uses obex-data-server to work and as far as I know no
> GNOME package is currently (and will use) obexd-server to work.
> obexd-server looks broken upstream-side since they started using
> org.openobex without providing a new namespace, and that will take any
> device requesting org.openbox not finding it and therefore failing.
> (like the issues g-bluetooth was having while browsing mobile phones
> with obexd-server)
>
>
>> > 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.
>
> obexd got adopted already, let's hope the new maintainer will have
> this fixed. :)
>

I contacted upstream of obex-data-server.
obex-data-server was made in GoSC/2007 under mentoring of
Marcel Holtmann, bluez and obexd maintainer.

He was ordered  DBUS name to orig.openobex to set it to Marcel.
And Marcel made obexd in this back. However, Marcel seems to have made DBUS name
same value at this time.
Marcel seems to have directed him to change it, but said that he did
not want to change it.

I understood that they did not want to change DBUS-name each other.
I think that we have to take the method how user cannot install
obex-data-serve and obexd in
at the same time in Debian.

How do you think abaout this idea?

Best regards,
  Nobuhiro
-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6





More information about the Pkg-bluetooth-maintainers mailing list