Am Samstag 20 Juni 2009 12:48:40 schrieb Filippo Giunchedi: > On Sat, Jun 20, 2009 at 12:04:39PM +0200, Hendrik Sattler wrote: > > > > I'm not sure what you mean, libbluetooth-dev right now is 4.40 which > > > > has headers for libbluetooth3 so I don't see what needs to be > > > > changed. > > > > > > is there any update on this bug? > > > > Same as with obexfs, this is in the queue. Didn't get around asking > > someone for upload, yet. > > It is available at > > http://www.hendrik-sattler.de/debian/pool/main/ussp-push/ussp-push_0.11-1 > >.dsc > > the call to hci_remote_name instead of hci_read_remote_name is still there: > > /tmp/buildd/ussp-push-0.11/src/obex_socket.c: In function > 'bt_sock_name2bth': /tmp/buildd/ussp-push-0.11/src/obex_socket.c:200: > warning: implicit declaration of function 'hci_remote_name'
Hm, no. You cannot change the API without change the name of the -dev package. This is an absolute no-go! And not having hci_remote_name() in bluetooth/hci_lib.h anymore _IS_ an API change. You cannot have both: either provide a compatible API or change the name of the -dev package. HS -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
