From: Filippo Giunchedi <filippo@esaurito.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Flavio Stanchina <flavio@stanchina.net>,
385857@bugs.debian.org, bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] Bug#385857: [Pkg-bluetooth-maintainers] Bug#385857: please upgrade to bluez-utils and bluez-libs 3.4
Date: Tue, 5 Sep 2006 12:32:07 +0200 [thread overview]
Message-ID: <20060905103207.GC30274@esaurito.net> (raw)
In-Reply-To: <1157371912.32195.69.camel@aeonflux.holtmann.net>
[-- Attachment #1.1: Type: text/plain, Size: 3392 bytes --]
Hello Marcel,
On Mon, Sep 04, 2006 at 02:11:52PM +0200, Marcel Holtmann wrote:
> > > > bluez-libs compiled out of the box by just unpacking and moving the
> > > > debian directory over, but bluez-utils needs some work:
> > > >
> > > > * remove bluez-bcm203x package (bcm203x firmware loader removed upstream)
> > >
> > > Not needed at all. You don't wanna support a 2.4 kernel and even if you
> > > really want to, you won't find any of these devices anymore. For all 2.6
> > > kernels the bcm203x kernel module takes care of loading the firmware.
> >
> > I'm going to drop it after etch release when we'll discontinue support for 2.4
> > kernels.
>
> You can drop it now actually. A Liunx 2.4 kernel user and owner of this
> device is a really really unlikely combination. I mean it. It would take
> me at least a couple of hours to find my dongle.
good luck with finding your dongle :)
anyway, as rare as it is etch is going to support 2.4 kernels.
>
> > > This package has to die and from an USB and udev perspective it was a
> > > really nasty hack.
> > >
> > > > * remove 000_rfcomm_conf_example.patch: the example is already commented
> > > > * remove 004_rfcomm_usage.patch: applied upstream
> > >
> > > Sometimes it is a good idea to feed patches back to upstream so I don't
> > > have to extract them from the packages.
> >
> > yep, I'm used to do it, I must have overlooked these patches.
>
> Do you have any other patches that are not upstream?
I'm looking at them one by one, bluez debian packages are maintained with svn.
You can browse the patches for bluez-utils at
http://svn.debian.org/wsvn/pkg-bluetooth/bluez-utils/trunk/debian/patches/?rev=0&sc=0
you might be interested in:
http://svn.debian.org/wsvn/pkg-bluetooth/bluez-utils/trunk/debian/patches/007_hcid_typo.patch?op=file&rev=0&sc=0
which fixes a small typo in hcid
http://svn.debian.org/wsvn/pkg-bluetooth/bluez-utils/trunk/debian/patches/008_pand_man.patch?op=file&rev=0&sc=0
addition for pand manpage referring /etc/bluetooth/pan/dev-up execution
http://svn.debian.org/wsvn/pkg-bluetooth/bluez-utils/trunk/debian/patches/006_xsims.patch?op=file&rev=0&sc=0
more compatible usage of test in bluetooth.init and hsplay
[snip]
> And please drop your passkey agent think completely. This will be
> distribution specific and can't be a solution. It is better to put the
> passkey-agent.c example in the docs directory as an example and mention
> it in a README.Debian.
>
> That said. I am missing a package for bluez-gnome which contains the
> graphical passkey agent. New version is coming up also this week. It
> will fix a small glitch with the status icon.
indeed, how about this plan:
- I will add to bluez-utils a default non-interactive passkey agent (more or less
like now but less hackish) which uses /etc/bluetooth/passkeys/<bt_addr> like
now
- bluez-gnome will provide the graphical passkey agent which takes over the
non-interactive one
Marcel: can agents be "stackable", that is, if two agents are registered and
first one doesn't supply an answer, the second will?
comments?
filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:
Age is not a particularly interesting subject. Anyone can get old. All
you have to do is live long enough.
-- Groucho Marx
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 373 bytes --]
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next parent reply other threads:[~2006-09-05 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060903124043.2028.48247.reportbug@forza>
[not found] ` <1157367160.32195.54.camel@aeonflux.holtmann.net>
[not found] ` <20060904100025.GA17058@esaurito.net>
[not found] ` <1157371912.32195.69.camel@aeonflux.holtmann.net>
2006-09-05 10:32 ` Filippo Giunchedi [this message]
2006-09-05 11:07 ` Bug#385857: [Bluez-devel] Bug#385857: [Pkg-bluetooth-maintainers] Bug#385857: please upgrade to bluez-utils and bluez-libs 3.4 Marcel Holtmann
2006-09-05 16:46 ` Stefan Seyfried
2006-09-05 17:13 ` Marcel Holtmann
2006-09-05 18:15 ` Stefan Seyfried
2006-09-05 18:59 ` Marcel Holtmann
2006-09-05 20:38 ` Stefan Seyfried
2006-09-05 21:08 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060905103207.GC30274@esaurito.net \
--to=filippo@esaurito.net \
--cc=385857@bugs.debian.org \
--cc=bluez-devel@lists.sf.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=flavio@stanchina.net \
--cc=marcel@holtmann.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.