[MIR] obexd

[Tony Espy]

1. Availability:

http://archive.ubuntu.com/ubuntu/pool/universe/o/obexd

This package is available for all supported architectures.

2. Rationale:

gnome-bluetooth includes obexd-client in it's 'Depends:' list.

NOTE - obexd-server is not needed and can be excluded from main.

3. Security:

 * There are no current CVE entries for obexd
 * There are no search results retunred by Secunia for obexd
 * Any binaries running as root or suid/sgid ? NO
 * Any daemons ?

   obex-client is a user-daemon DBUS-activated as a session service.

 * Network activity: does it open any port?

   obex-client opens the Bluetooth device and send/receives data to/from
   a connected device's obex-server.

 * Does it handle incoming network data?

   obex-client only handles incoming data in response to requests it
   sends to a connected obex-server.

 * Does it directly (not through a library) process
   binary (video, audio, etc) or structured (PDF, etc) data ?

   obex-client does no direct processing of binary data. It's used
   only for data transfer.

 * Any source code review performed? NO

4. Quality assurance:

 * In what situations does the package not work out of the box without configuration? NONE
 * Does the package ask any debconf questions higher than priority 'medium' ? NO
 * Debian bugs: (mention any that are particularly relevant, and any showstoppers) NONE
 * Maintenance in Debian is frenetic/vigorous/calm/dead ?

   The Ubuntu Desktop and Foundations will maintain the package in Debian.

 * Upstream is frenetic/vigorous/calm/dead ?

   Upstream activity is currently calm.

 * Upstream bug tracker: (mention any particularly relevant or critical) NONE
 * Hardware: Does this package deal with hardware and if so how exotic is it ?

   Yes, this package deals with consumer Bluetooth devices, which by definition
   it not exotic.

 * Is there a test suite in the upstream source or packaging ? NO

5. UI standards:

obex-client is a daemon process and has no user-visible strings or UI.

6. Standards compliance:

 * FHS, Debian Policy compliance? YES
 * Packaging system (debhelper/cdbs/dbs)? debhelper
 * Patch system? simple-patchsys
 * Any packaging oddities? NO
7. Dependencies:

 * Build-Depends: cdbs, debhelper (>= 7), libglib2.0-dev, libdbus-1-dev,
   libopenobex1-dev, libbluetooth-dev (>= 4)
 * Runtime: none
 * Are these all in main? YES

8. Maintenance:

  * How much maintenance is this package likely to need ?

    In theory, very little. This is pretty simple daemon used for
    BT file transfer.

  * Who is responsible for monitoring the quality of this package and
    fixing its bugs ?

    The Ubuntu Desktop and Foundations teams.

  * Are they Ubuntu or Debian developers ? YES, both.

9. Background information:

 * The general purpose and context of the package should be clear from the package's
   debian/control file. If it isn't then please explain.

   The explanation in the debian/control file is sufficient.

 * What do upstream call this software ?

   obexd-client

 * Has it had different names in the past ? NO

10. Internationalization:

 N/A, see Section 5. UI standards

[Alexander Sack (asac)]

we pre-promote this for alpha4 ... setting milestone to alpha 5 so it doesnt get lost.

[Loïc Minier (lool)]

(FYI upstream is at 0.17 while we have 0.14)

Please subscribe to bugmail

Approved; thanks

[Martin Pitt (pitti)]

Not promoting yet, component-mismatches does not want to pull it in yet. Presumably because current gnome-bluetooth does not build because of the gpsd mess.

[Martin Pitt (pitti)]

Please note that this will not be promoted unless something in main or the seeds require it. Please make this a (build)-dependency of something, otherwise we will just "time out" and close this MIR.

Thank you!

[Tony Espy (awe)]

Martin, not sure I understand your last comment...

According to asac, this was pre-promoted for alpha4 and Loic approved subsequently.

gnome-bluetooth does builds and currently lives in main, and as stated in the original MIR, has a -dependency on obexd-client.

[Steve Langasek (vorlon)]

yes, this package is already in main; closing the bug, thanks.