Bug 509360 – dev-qt/qt-mobility still PDEPENDs on app-mobilephone/obexd

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Pacho Ramos 2014-05-02 08:27:14 UTC]

Would be nice to confirm if it still works with plain bluez5 (that incorporated obexd that is no developed for a long long time)

Thanks a lot

[Comment 1 Davide Pesavento (RETIRED) 2014-05-02 11:06:31 UTC]

The QtConnectivity component uses the org.openobex.{Agent,Client,Manager,Transfer} dbus interfaces. Does that mean that it works with bluez-5? Did they keep the same interfaces?

[Comment 2 Pacho Ramos 2014-05-02 11:08:32 UTC]

Uh, then it will only work with old obexd-0.46 (and bluez4) then :/, not sure if upstream could be contacted to clarify if they plan to support bluez5 in some way, if they were deprecated by other thing... :|

[Comment 3 Davide Pesavento (RETIRED) 2014-05-02 11:16:54 UTC]

qt-mobility development has practically stopped a couple of years ago, bugfixes for mobile platforms are still committed from time to time, but that's it. Bluez 5 support won't happen.

Should I change the bluez dep to =bluez-4* ?

[Comment 4 Pacho Ramos 2014-05-02 11:30:07 UTC]

Not sure as looks like Fedora (that is bluez-5 only for a long time) is still having it without obexd and bluez-5 but using a newer snapshot. The same for Mandriva :/

[Comment 5 Davide Pesavento (RETIRED) 2014-05-02 12:06:05 UTC]

(In reply to Pacho Ramos from comment #4)
> but using a newer snapshot.

No, only fedora rawhide has a newer snapshot than ours. And anyway there haven't been bluetooth-related commits lately.

Since it's a runtime-only dep, we can switch to

  || ( =bluez-5*
       ( =bluez-4* obexd )
     )

what do you think?

[Comment 6 Pacho Ramos 2014-05-02 12:41:04 UTC]

Looks interesting, but if it relies on org.openobex dbus interfaces I don't think it will work with bluez-5 only (and I am unsure how will work when both, bluez-5 and obexd are present) :|

Maybe we could mail to fedora maintainers of this package

[Comment 7 Davide Pesavento (RETIRED) 2014-05-02 15:35:59 UTC]

(In reply to Pacho Ramos from comment #6)
> Looks interesting, but if it relies on org.openobex dbus interfaces I don't
> think it will work with bluez-5 only (and I am unsure how will work when
> both, bluez-5 and obexd are present) :|

I think that's acceptable. qt-mobility's target is mainly application developers who can deal with this (the bt file transfer functionality will simply not work with bluez-5). Moreover, the bluetooth module of qt-mobility has zero in-tree users.

[Comment 8 Davide Pesavento (RETIRED) 2014-05-23 13:58:42 UTC]

*qt-mobility-1.2.2_p20130703-r1 (23 May 2014)

  23 May 2014; Davide Pesavento <[e-mail]>
  +qt-mobility-1.2.2_p20130703-r1.ebuild:
  Remove USE=bearer, superseded by dev-qt/qtbearer. Switch to virtual/libudev.
  Drop obexd dependency wrt bug 509360.